How to force root servers to update cached host record (Long post)
James Griffin
agriffin at cpcug.org
Fri May 31 13:54:44 UTC 2002
Ralf Naegele wrote:
>
> Lee M Dobson <ldobson at alabanza.com> shaped the electrons to say:
>
> well, it seems, that I have the same problem. Hosting the zone dis.ag,
> the root nameservers are always caching the old host record for www.dis.ag
> 195.20.74.131 instead the real and up-to-date host record 212.21.186.57
> which is in the zone if you check the authoritive nameservers for dis.ag.
>
> By now I've checked several whois servers including whois.nic.ag for
> some hints who has this stupid host record for www.dis.ag with the IP
> 195.20.74.131 but with no success. Where can I additionally look for
> it?
Try the following:
$ dig +trace www.dis.ag.
; <<>> DiG 9.2.0 <<>> +trace www.dis.ag.
;; global options: printcmd
.. 243998 IN NS B.ROOT-SERVERS.NET.
.. 243998 IN NS C.ROOT-SERVERS.NET.
.. 243998 IN NS D.ROOT-SERVERS.NET.
.. 243998 IN NS E.ROOT-SERVERS.NET.
.. 243998 IN NS F.ROOT-SERVERS.NET.
.. 243998 IN NS G.ROOT-SERVERS.NET.
.. 243998 IN NS H.ROOT-SERVERS.NET.
.. 243998 IN NS I.ROOT-SERVERS.NET.
.. 243998 IN NS J.ROOT-SERVERS.NET.
.. 243998 IN NS K.ROOT-SERVERS.NET.
.. 243998 IN NS L.ROOT-SERVERS.NET.
.. 243998 IN NS M.ROOT-SERVERS.NET.
.. 243998 IN NS A.ROOT-SERVERS.NET.
;; Received 292 bytes from 127.0.0.1#53(127.0.0.1) in 6 ms
ag. 172800 IN NS ACT2.ACT2000.NET.
ag. 172800 IN NS ACT1.ACT2000.NET.
ag. 172800 IN NS NS2.NETNAMES.NET.
ag. 172800 IN NS NS1.NETNAMES.NET.
ag. 172800 IN NS UPR1.UPR.CLU.EDU.
;; Received 232 bytes from 128.9.0.107#53(B.ROOT-SERVERS.NET) in 10300
ms
www.dis.ag. 7088 IN A 195.20.74.131
dis.ag. 7088 IN NS ns7.dns-net.de.
dis.ag. 7088 IN NS ns2.she.de.
dis.ag. 7088 IN NS ns.she.de.
;; Received 165 bytes from 208.255.124.46#53(ACT2.ACT2000.NET) in 715 ms
Note that the "incorrect" address was provided from act2.act2000.net.
It is also worth looking at a current 'doc' run. Note that
act2.act2000.net appears again, this time as non-authoritative. The
serial numbers imply current zones.
Doc-2.2.3: doc -v dis.ag.
Doc-2.2.3: Starting test of dis.ag. parent is ag.
Doc-2.2.3: Test date - Fri May 31 09:50:06 EDT 2002
soa @act1.act2000.net. for ag. has serial: 2002053100
WARNING: non-authoritative answer for ag. from act1.act2000.net.
soa @act2.act2000.net. for ag. has serial: 2002053100
WARNING: non-authoritative answer for ag. from act2.act2000.net.
soa @ns1.netnames.net. for ag. has serial: 2002053100
soa @ns2.netnames.net. for ag. has serial: 2002053100
soa @upr1.upr.clu.edu. for ag. has serial: 2002053100
WARNING: non-authoritative answer for ag. from upr1.upr.clu.edu.
SOA serial #'s agree for ag. domain
Found 3 NS and 0 glue records for dis.ag. @ns1.netnames.net. (non-AUTH)
Found 3 NS and 0 glue records for dis.ag. @ns2.netnames.net. (non-AUTH)
DNServers for ag.
=== 0 were also authoritatve for dis.ag.
=== 2 were non-authoritative for dis.ag.
Servers for ag. (not also authoritative for dis.ag.)
=== agree on NS records for dis.ag.
NS list summary for dis.ag. from parent (ag.) servers
== ns2.she.de. ns7.dns-net.de. ns.she.de.
soa @ns2.she.de. for dis.ag. serial: 2002052902
soa @ns7.dns-net.de. for dis.ag. serial: 2002052902
soa @ns.she.de. for dis.ag. serial: 2002052902
SOA serial #'s agree for dis.ag.
WARN: SOA records differ for dis.ag. from authoritative servers
Authoritative domain (dis.ag.) servers agree on NS for dis.ag.
NS list from dis.ag. authoritative servers matches list from
=== parent (ag.) servers not authoritative for dis.ag.
Checking 0 potential addresses for hosts at dis.ag.
==
Summary:
WARNINGS issued for dis.ag. (count: 4)
Done testing dis.ag. Fri May 31 09:50:53 EDT 2002
HTH
Jim
>
> Regards,
> Ralf
>
> > Eric,
>
[snip stuff from Eric]
More information about the bind-users
mailing list