The problem was error messages of the type:
> Dec 12 11:51:52 mainsrvr named-xfer[22480]: [123.45.89.1] not authoritative for 67.45.123.in-addr.arpa, SOA query got rcode 0, aa 0, ancount 1, aucount 0
Thanks to Jason Grove, Dan Anderson, Bismark Espinoza and others. As Jason
said, the messages meant what they said - the problem was not in our DNS
setup, but in the server which was supposed to be the primary for the
various subdomains.
An nslookup:
> server 123.45.89.1
> set type=soa
> 67.45.123.in-addr.arpa
produced a "non-authoritative reply" that 123.45.89.1 was supposed to be the
SOA origin!!
We had no access to 123.45.89.1. Tracking down the supposed sysad for it
revealed it was a Cisco server with some duff definitions of their inverse
zones. Problem solved (including the main problem - those ten megabyte
/var/adm/messages logs!!)
Hector Davie
UNIX & Gateways
Ascom Ltd
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:24 CDT