ns.paulbunyan.net looks like a glue record that doesn't belong.
Hopefully, it will go away, eventually.
Never try to redefine the name used previously for a second-level
nameserver until you are sure the 'glue has dried'.
--Dean
On Thu, 2 Nov 2006, The Almighty Pegasus Epsilon wrote:
> i need to look up ns.paulbunyan.net. so i do:
>
> # dnsq a ns.paulbunyan.net 192.5.6.30 (a.gtld-servers.net)
> 1 ns.paulbunyan.net:
> 119 bytes, 1+1+2+2 records, response, noerror
> query: 1 ns.paulbunyan.net
> answer: ns.paulbunyan.net 172800 A 206.8.120.20
> authority: paulbunyan.net 172800 NS ns2.paulbunyan.net
> authority: paulbunyan.net 172800 NS ns3.paulbunyan.net
> additional: ns2.paulbunyan.net 172800 A 209.191.199.72
> additional: ns3.paulbunyan.net 172800 A 209.191.199.73
>
> the SOA is correct. the answer is NOT. the answer is also not authoritative.
> so we ask the authoritative server, and get:
>
> # dnsq a ns.paulbunyan.net 209.191.199.72 (ns2.paulbunyan.net)
> 1 ns.paulbunyan.net:
> 135 bytes, 1+1+2+3 records, response, authoritative, noerror
> query: 1 ns.paulbunyan.net
> answer: ns.paulbunyan.net 1800 A 209.191.199.71
> authority: paulbunyan.net 1800 NS ns3.paulbunyan.net
> authority: paulbunyan.net 1800 NS ns2.paulbunyan.net
> additional: ns2.paulbunyan.net 1800 A 209.191.199.121
> additional: ns2.paulbunyan.net 1800 A 209.191.199.72
> additional: ns3.paulbunyan.net 1800 A 209.191.199.73
>
> aha! that answer is correct, AND authoritative.
>
> so what i need, apparently, is a way to make dnscache discard any answer
> that isn't authoritative. any hints? any preexisting patches? do i need to
> request a bugfix or something?
>
--
Av8 Internet Prepared to pay a premium for better service?
www.av8.net faster, more reliable, better service
617 344 9000
|