Help with screwy behavior...
Mark.Andrews at nominum.com
Mark.Andrews at nominum.com
Thu Jun 15 22:35:30 UTC 2000
Boatmotors.com has its delegation completely screwed up as the NS
list in zone does not match that in the parent zone.
I've Bcc the relevent contacts.
Mark
bsdi:resolv {1778} % dig boatmotors.com @NS.IBOATS.COM
; <<>> DiG 8.2 <<>> boatmotors.com @NS.IBOATS.COM
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;; boatmotors.com, type = A, class = IN
;; ANSWER SECTION:
boatmotors.com. 1D IN A 209.90.113.162
;; AUTHORITY SECTION:
boatmotors.com. 1D IN NS boatmotors.com.
boatmotors.com. 1D IN NS local.iboats.com.
;; ADDITIONAL SECTION:
boatmotors.com. 1D IN A 209.90.113.162
local.iboats.com. 1D IN A 209.90.117.130
;; Total query time: 460 msec
;; FROM: bsdi.dv.isc.org to SERVER: NS.IBOATS.COM 209.90.113.162
;; WHEN: Fri Jun 16 08:31:44 2000
;; MSG SIZE sent: 32 rcvd: 124
bsdi:resolv {1779} % dig ns boatmotors.com @a.root-servers.net
; <<>> DiG 8.2 <<>> ns boatmotors.com @a.root-servers.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUERY SECTION:
;; boatmotors.com, type = NS, class = IN
;; ANSWER SECTION:
boatmotors.com. 2D IN NS NS.IBOATS.COM.
boatmotors.com. 2D IN NS NS.LOCAL.IBOATS.COM.
;; ADDITIONAL SECTION:
NS.IBOATS.COM. 2D IN A 209.90.113.162
NS.LOCAL.IBOATS.COM. 2D IN A 209.90.117.130
;; Total query time: 464 msec
;; FROM: bsdi.dv.isc.org to SERVER: a.root-servers.net 198.41.0.4
;; WHEN: Fri Jun 16 08:32:14 2000
;; MSG SIZE sent: 32 rcvd: 114
bsdi:resolv {1780} %
>
> The last week I've seen some odd behaviour. A few other name servers
> can't resolve our domains, and I'm not sure why... It happened first with
> one of USWest's name servers, and the problem went away in a day. Now,
> another ISP's name servers are doing the same thing:
>
> [steve at helix steve]$ nslookup
> Default Server: slkcpop1.slkc.uswest.net
> Address: 206.81.128.1
>
> > server ns.inconnect.com
> Default Server: ns.inconnect.com
> Address: 209.140.64.4
>
> > boatmotors.com.
> Server: ns.inconnect.com
> Address: 209.140.64.4
>
> *** ns.inconnect.com can't find boatmotors.com.: Server failed
> > server a.root-servers.net
> Default Server: a.root-servers.net
> Address: 198.41.0.4
>
> > boatmotors.com.
> Server: a.root-servers.net
> Address: 198.41.0.4
>
> Name: boatmotors.com
> Served by:
> - NS.IBOATS.COM
> 209.90.113.162
> boatmotors.com
> - NS.LOCAL.IBOATS.COM
> 209.90.117.130
> boatmotors.com
> > server ns.iboats.com
> Default Server: ns.iboats.com
> Address: 209.90.113.162
>
> > boatmotors.com.
> Server: ns.iboats.com
> Address: 209.90.113.162
>
> Name: boatmotors.com
> Address: 209.90.113.162
>
> ---------------------------------------------
>
> So, for me it appears that the normal "chain of command" is working. The
> offending name server *should* talk to the root servers, they point it to
> ns.iboats.com, and that responds. I'm baffled as to why it doesn't work.
>
> Any suggestions?
>
> steve
> --
> --------------------------------------------------
> Domain for replies is "codon".
> --------------------------------------------------
>
>
>
>
>
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at nominum.com
More information about the bind-users
mailing list