Rich Payne <[EMAIL PROTECTED]> writes: > Your DNS server should have 2 files, one that does ip->name and one that > does name->ip. For exmaple I take care of monadlug.org and I have > db.monadlug that contains any/all hosts in that domain. Then I have a > db.43.22.207 file that includes reverse mappings, with records like this: > > 150 IN PTR talisman.monadlug.org. >
The blu.org DNS server actually does have the zone file for the reverse
lookup, and returns the correct reverse record:
jabr@asgard:~ $ host blu.org
blu.org. has address 216.235.254.231
jabr@asgard:~ $ host asgard
asgard.blu.org. has address 216.235.254.231
jabr@asgard:~ $ host 216.235.254.231
231.254.235.216.in-addr.arpa. domain name pointer asgard.blu.org.
This works fine locally on the blu.org server, where it refers to its
own dns server on localhost. From outside the blu.org server, using
some other dns server, the reverse lookup fails:
jabr@vishnu:~ $ host 216.235.254.231
Host 231.254.235.216.in-addr.arpa. not found: 3(NXDOMAIN)
It looks to me like DNS is working correctly on blu.org, but the
secondaries are failing to pick up our reverse-lookup zone.
I had originally set up blu.org as a cname to asgard.blu.org, but
USDataCenters had some sort of problem with that, and insisted that
blu.org had to be an address record, otherwise their DNS servers would be
unable to do a zone transfer from blu.org at all.
--
John Abreau / Executive Director, Boston Linux & Unix
ICQ 28611923 / AIM abreauj / JABBER [EMAIL PROTECTED] / YAHOO abreauj
Email [EMAIL PROTECTED] / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99
msg12805/pgp00000.pgp
Description: PGP signature
