DNS

[Kevin Wright]

I am dumbfounded as to what is going on here and would appreciate any ideas.
The internal DNS server is set up with a forwarders line to the firewall. named.ca also contains this same host.the firewall then goes to the external primary DNS server for the domain xxx.com which serves the web site as well.
every domain you do an nslookup on using the internal server, replies as non authoritive..even after a kill and restart?
However, nslookup does NOT work for our own domain UNLESS it is on the internal server???

why doesn't the internal server forward requests to the firewall for our own domain like it does for every other domain out there???? am I missing something here?

[Shannon Petry]

Well, where to begin....
First the answer "non-authoritative" is normal for any DNS server which is NOT the authority for the domain. Since it appears that your internal DNS server is forwarding to an external, the there are one of two things going on.
1. The internal server is setup as secondary for the domain.
2. The SOA record is bad!
If it is item 2, the easiest way to find this is by checking /var/adm/syslog/syslog.log. One of the cache files or hints files is corrupt!

Depending on how much is corrupt, and how much you need to do I would suggest downloading bind tools from www.bind.org (link to www.isc.org/products/bind). These tools contain h2n which is a more advanced hosts_to_named with much more flexibility and functionality than what is shipped with HP-UX. There are loads of other nice tools as well.

Anyway, hope this gets you pointed in the right direction.

Regards,
Shannon

[Berlene Herren]

Non-authoritative means it is answering your request out of the cache.

Try putting your forwarder IP in twice (in named.boot), like so:

forwarders 15.253.24.10 15.253.32.10 15.253.8.10 15.253.40.10 15.253.48.10

Berlene