DNS entry updated but external DNS servers show old IP address

[CAS_2]

Hi

I updated an entry in my DNS server database:
IP adress of "xxx.my.com" was X.X.X.10 and now is X.X.X.20.

Now, any nslookup from my intranet solves fine the new IP, but nslookup from outer (any other node in Internet) shows OLD IP dir.

The update was done 4 days ago.
New IP address is not propagate to other DNS servers.

How can I check if my DNS server is propagating properly my changes ?

Thank you

[Bejoy C Alias]

Hi CAS,

Can you specify the exact domain name and ip addresses .
You can use dnsstuff.com or dnsreport.com to check whether any one from outside is getting the correct dns answers.

Rgds
Bejoy

[jpcast_real]

When you update your DNS server you have to increase the serial number which represents the zone . This will make that the transfer of zone will be performed.

An example:


Dartanan:/etc/named.data> more db.sate2.com
$TTL 10d
sate2.com. IN SOA dartanan.sate2.com. root.dartanan.sate2.com. (
2005041301 ; Serial
10800 ; Refresh every 3 hours
3600 ; Retry every hour
604800 ; Expire after a week
86400 ) ; Negative Caching TTL


It is very tipical to use the date of the day in inverse way to build this number

2005050601.... Year,month,day,release

Restarting your slave DNS server you can force the refresh...

[Andrew Cowan]

Zone transfers will also fail if the serial number is too-large, ie out of range, because the daemon actually sees a negative number, and ignores it.

[Florian Heigl (new acc)]

Some more reasons murphy came up with:
TTL/Refresh of zone is very high
Connectivity to authoritative NS
authoritative NS doesn't consider himself authoritative
Serial number not increased (this shouldn't be the issue, as You see the right data)
But external servers might still have cached data on You from earlier queries for the duration of Your TTL.