I'm having problems with my DNS services and hope someone here can help.
Here's the situation. I've got two NetWare 6.5 SP4 servers. Up until recently we housed our DNS on border, to resolve an internal problem we moved out DNS to LCS.
I work for a school so the state holds our secondary NS record. I've gotten them to update it to point to LCS, and that appears to be working fine. The problem comes when I go to the domains like "www" or "mail", etc. All of those are reporting that there is no NS record available or that the query has timed out. This effectively stops anyone from reaching our sites. I can still reach the sites just fine with the IP address.
In my DNS/DHCP tool I have 3 zones. A RootServerInfo, a IN-ADDR-ARPA, and the domain.
Under the IN_ADDR-ARPA there is a domain name entry for each server's public IP. As well as an "@" entry which I'm assuming is the root. Under the entries for servers there are PTR records pointing to the full site address of that server. For example server 184.108.40.206 has a domain name entry of 220.127.116.11.IN-ADDR-ARPA and under that entry has a PTR record of border.mysite.com as well as www.mysite.com. Yes, both "border" and "www" are the same server.
The "@" entry is the only entry that has an NS record, the NS entry is the only entry under the "@" entry. The NS record I have gives the full URL for our dns server. Example lcs.mysite.com
Moving on to the domain entries:
This area contains the entries such as "WWW" with an A record to point to the public IP address of the server. There is one "@" entry which contains our MX records and an NS record. All entries under the "@" entry give the full URL of the correct server. Example NS record = LCS.MYSITE.COM, MX record = mail.mysite.com.
Last but not least is the RootServerInfo. Along with the a.root-servers.net entries there is one "@" entry, with an NS record. The NS record again gives the full URL of the DNS server.
Now, moving on to other concerns. Named.nlm is loaded on the server and the server states that the DNS services are running. I've loaded and unloaded named.nlm several times all without success.
We have a PIX firewall which I've opened TCP and UDP traffic to port 53 for the DNS server as well as port 80 and other ports for their respective services.
I also know that entries with DNS take as long as 2 days to circulate the web so changes won't be noticed immediately. What miffs me is that Friday afternoon everything was working fine, Saturday at noon things have gone to poop again.
Thanks in advance for any assistance.