com nameserver caching

rh rhashemian at
Wed Jun 18 21:22:15 UTC 2008

hi all,
if you lookup, most queries come back with:
but i started noticing that a couple of my dns servers were returning
a wrong ip:

after some digging, i noticed that the com namesavers actually have
this RR cached like so:
[~]$ dig +norec @h.GTLD-SERVERS.NET

; <<>> DiG 9.2.4 <<>> +norec @h.GTLD-SERVERS.NET
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29492
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;                 IN      A

;; ANSWER SECTION:          172800  IN      A

;; AUTHORITY SECTION:              172800  IN      NS              172800  IN      NS

;; ADDITIONAL SECTION:         172800  IN      A         172800  IN      A


is this normal? i don't see any other RR's for major companies in
these nameservers. i assume because of this the iterative query stops
at this point and returns this bad ip without going further to the
authoritative nameservers for



More information about the bind-users mailing list