Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

DNS propagation question

Posted on 2010-09-10
12
Medium Priority
?
526 Views
Last Modified: 2012-08-14
Hello, 48 hours ago DNS was modified to point website to one host (BlueHost) and
email to another host (Liquidweb)

Today when I ping from my Comcast connection it shows the correct IP for the
website (74.220.207.179) and the correct IP for mail (69.167.173.234) but when
I send a test email through Comcast it's still going to BlueHost.

Domain is luxuryvillaslanzarote.com

Mail sent from within the email host server (Liquidweb) routes correctly to his email address, but all other mail goes to BlueHost.

any ideas?
0
Comment
Question by:SimpleJoe
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 3
  • +2
12 Comments
 
LVL 32

Expert Comment

by:Rodney Barnhardt
ID: 33649954
I tried checking using mxtoolbox.com and the domain for mail on the Internet is still showing 74.220.207.179. Maybe you need to contact your ISP and see if there is a propagation issue on their part. I remember making a change several years ago with MCI, and when I called back, told me they were having DNS issues.
0
 
LVL 3

Expert Comment

by:kf4zmt
ID: 33649990
Is this a bind dns server?  If so, did you restart the bind service after making the changes?
0
 
LVL 24

Expert Comment

by:rfc1180
ID: 33650040
;; ANSWER SECTION:
luxuryvillaslanzarote.com. 503      IN      A      74.220.207.179


atomant@neteng01 ~ $ dig mail.luxuryvillaslanzarote.com +short
69.167.173.234



You need to update the MX record to point to mail.luxuryvillaslanzarote.com

Billy
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
LVL 24

Expert Comment

by:rfc1180
ID: 33650045
meaning the MX record is pointing to the parent domain:

atomant@neteng01 ~ $ dig mx luxuryvillaslanzarote.com +short
0 luxuryvillaslanzarote.com.
0
 
LVL 8

Expert Comment

by:dmarinenko
ID: 33650059
You may have changed the A records but not the MX records. An "A" record change would ping the correct spot.  E-mail can still go somewhere else though as it depends upon the MX records.  Go to mxtoolbox.com and put in your domain to see what your MX records are pointed too.  I checked it and it is pointed to 74.220.207.179.  Ask whoever holds your dns records to erase that enry and put the correct one in.
0
 

Author Comment

by:SimpleJoe
ID: 33650134
it's a cpanel server, here's a screenshot of the DNS as we have it setup, and he is using our nameservers:
dns.jpg
0
 
LVL 32

Expert Comment

by:Rodney Barnhardt
ID: 33650155
Not on the server. Your MX record with your ISP. That is where you need to make the MX record change.
0
 
LVL 24

Accepted Solution

by:
rfc1180 earned 2000 total points
ID: 33650158
change the line:

luxuryvillaslanzarote.com 600 IN MX 0  luxuryvillaslanzarote.com.

to

luxuryvillaslanzarote.com 600 IN MX 0  mail.luxuryvillaslanzarote.com.
0
 
LVL 32

Expert Comment

by:Rodney Barnhardt
ID: 33650166
Sorry, mis read you last post. on the MX record, you need the IP on the right side instead of the domain name.
0
 
LVL 24

Expert Comment

by:rfc1180
ID: 33650185
bad practice to use the IP; besides, there is an A record already defined for the IP (mail):
0
 

Author Comment

by:SimpleJoe
ID: 33650971
rfc1180: thank you very much, you were absolutely correct.

48 hours and multiple techs and it took experts exchange to correct it within minutes

thanks again
0
 

Author Closing Comment

by:SimpleJoe
ID: 33650975
awesome
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is intended as an extension of a blog on Aging and Scavenging by the MS Enterprise Networking Team. In brief, Scavenging is used as follows: Each record in a zone which has been dynamically registered with an MS DNS Server will have…
I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums. I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question