I've been trying to find out why a small number of nameservers seem to
cache incorrect A records for {ns1,ns2,ns3}.ispc.org and I think I've
tracked it down to some bad "additional results" returned by the .org
roots when looking up domains served by those nameservers. Likely some
old nameservers that are subject to cache poisoning are getting polluted
by that info, which would explain why only a small fraction of people
have problems.
What I can't find out is where that glue is coming from, or more to
the point, where to go to fix it.
As an example: ask any .org root server for info about "geezer.org" .
The "additional" section contains addresses for the geezer.org
nameservers, with incorrect IP addresses for the ns?.ispc.org names.
Example below.
Does anybody know where I might go to repair this? i.e., to have
the bad glue removed or at least corrected?
Yours,
-mm-
% dig @tld2.ultradns.net geezer.org
; <<>> DiG 8.3 <<>> @tld2.ultradns.net geezer.org
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7500
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 3
;; QUERY SECTION:
;; geezer.org, type = A, class = IN
;; AUTHORITY SECTION:
GEEZER.ORG. 2D IN NS NS3.ISPC.ORG.
GEEZER.ORG. 2D IN NS NS2.ISPC.ORG.
GEEZER.ORG. 2D IN NS NS1.MV.NET.
GEEZER.ORG. 2D IN NS NS1.ISPC.ORG.
;; ADDITIONAL SECTION:
ns3.ispc.org. 1D IN A 212.96.128.162
ns2.ispc.org. 1D IN A 212.96.128.161
ns1.ispc.org. 1D IN A 212.96.128.160
;; Total query time: 371 msec
;; FROM: osmium.mv.net to SERVER: 204.74.113.1
;; WHEN: Thu Mar 24 20:52:35 2005
;; MSG SIZE sent: 28 rcvd: 186
