IP addresses in NS records seem to be breaking hostname resolution

[David Botham]

As a follow up, I forwarded this thread to both the soa responsible
email and whois responsible email.  And as an extra bonus, I called the
whois admin contact on the phone.  He was happy to here from me and said
he would call his ISP and light a fire under...

Dave...
> -----Original Message-----
> From: Chris Davis [mailto:chris.davis at computerjobs.com]
> Sent: Wednesday, July 17, 2002 10:00 AM
> To: 'David Botham'; bind-users at isc.org
> Subject: RE: IP addresses in NS records seem to be breaking hostname
> resolution
> 
> David,
> 
> Your nameserver 216.154.198.178 responded to your single dig query
with
> correct nameserver entries provided by the GTLD servers.  This first
bit
> of
> resolution works for me as well if I don't have any NS records for
> pacetech-inc.com in my resolver's cache.
> 
> The problem I'm experiencing is that once I make contact with the
> nameservers at hj.dpliv.com or pcweb.dpliv.com to resolve an MX or A
> record,
> they pass additional records to me containing broken NS records.
After
> that, resolution fails.
> 
> When you did "dig mx pacetech-inc.com", you got back the same bad NS
> records
> I got back:  IP addresses.  Look closely at the NS records in the
> AUTHORITY
> section of what you sent me under "dig mx pacetech-inc.com".
> 
> Your first dig got NS records from GTLD servers.  Your second dig
shows
> the
> bad NS records from pacetech-inc.com's servers.
> 
> Your subsequent resolutions of pacetech-inc.com hostnames should now
fail
> if
> you're using a caching resolver.
> 
> Chris Davis
> 
> -----Original Message-----
> From: David Botham [mailto:dns at botham.net]
> Sent: Wednesday, July 17, 2002 9:31 AM
> To: bind-users at isc.org
> Subject: RE: IP addresses in NS records seem to be breaking hostname
> resolution
> 
> 
>