reverse DNS - FIXED!!!

Devon Harding - GTHLA DHarding at gilatla.com
Fri Jul 12 13:56:21 UTC 2002


DELEGATION!!!

Made one phone call to AT&T, Provided them with new NS IP's and fqdn.
Within an hour everything worked fine!

Thanks for all your help!

-Devon

-----Original Message-----
From: those who know me have no need of my name
[mailto:not-a-real-address at usa.net] 
Sent: Thursday, July 11, 2002 2:48 AM
To: comp-protocols-dns-bind at isc.org
Subject: Re: reverse DNS


you probably could have saved a lot of time if you would have just posted
the real ip block in question.  is 12.108.32.65 supposed to be one of your
addresses?  if so the `problem' for the rest of the world is that at&t
hasn't delegated that address to any other server, they provide resolution
directly.  if you only expect it to resolve locally and you are *sure* that
your resolv.conf doesn't reference a server other than your dmz nameserver
then there's something else which is wrong, e.g., the zone doesn't load.

in comp.protocols.dns.bind i read:

>                   DMZ------DNS Server (Bind 9.1.3)

update.

-- 
bringing you boring signatures for 17 years


More information about the bind-users mailing list