Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am having an issue where I ping my domain and it replies back the old IP/A record of that domain. I have checked my Dns records for both NS servers and all records are correct. If I have posted this in the wrong thread please let me know.

share|improve this question
How old is the record? Your client may have cached the DNS entry. Also, new records may not have propagated fully yet. – David Houde Jan 8 '13 at 20:50
We changed the records to the new IP address 5 days ago. – n_starnes Jan 8 '13 at 20:51
Is this a linux or windows client? I would like to check using the actual name server. Windows->Run->CMD: nslookup [enter] server (replace with either ns IP) [enter] [enter] and it should return a result. Is this the new IP or old IP? – David Houde Jan 8 '13 at 20:53
It is a windows server. I'll try that real quick. – n_starnes Jan 8 '13 at 21:09
What's the domain? – gparent Jan 9 '13 at 21:03
up vote 1 down vote accepted

There are many possible reasons and you gave very little details. We do not even have the domain name to test.

Among the possible reasons:

  • You forgot to increment the serial number so the slaves still have the old zone ('dig @slaveserver SOA domainname' to test)
  • you have glue records at the registry with the old address ('dig @registryserver A name' to test)

Without more details, we can only guess. For instance, what does "I have checked my Dns records for both NS servers and all records are correct" mean? Did you just read the zone files or tested the actual live DNS server with dig or drill?

share|improve this answer
I have simply checked the zone files. This is what I meant. The domain is – n_starnes Jan 10 '13 at 17:32

After using dig we found that the DNS of our internal server which we all connect to through a local domain was not updated and using the old IP/A record.

share|improve this answer
Edit the question, do not add details as answers. – bortzmeyer Jan 10 '13 at 19:14
This in itself is an answer due to it solved the problem. – n_starnes Jan 11 '13 at 20:28

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.