I have a w2k Adv. Server machine which is a domain controller. Its also performs DNS for the domain which it controls, lilzeus.net. Internet access is via a cable modem. At first I had 2 NICS, ICS on the server and a hub to run the internal network. Everything was pretty much OK. I recently bought a router. It provides IPs for all the machines so I uninstalled the DHCP service on the server. I am not running AD.
My problem is that I am getting netlogon errors every 2 hours. Here are a couple examples:
Registration of the DNS record 'lilzeus.net. 600 IN A 192.168.0.101' failed with the following error:
DNS server not authoritative for zone.
Registration of the DNS record '_gc._tcp.Default-First-Site-Name._sites.lilzeus.net. 600 IN SRV 0 100 3268 ns1.lilzeus.net.' failed with the following error:
DNS server not authoritative for zone.
The router assigns address, 192.168.0.101, to the server. The address, 68.58.103.37, is the IP for the WAN/router. My server's TCP/IP is set to dynamic at the moment. Here are some pics of my DNS setup:
I got rid of this problem by setting the forward lookup zone to allow dynamic updates BUT it ended up changing the IP address for the ns1 record to a 192.168.0.101 address which killed the websites.
What can I do to set this straight? I have been trying different settings for a while now.
My problem is that I am getting netlogon errors every 2 hours. Here are a couple examples:
Registration of the DNS record 'lilzeus.net. 600 IN A 192.168.0.101' failed with the following error:
DNS server not authoritative for zone.
Registration of the DNS record '_gc._tcp.Default-First-Site-Name._sites.lilzeus.net. 600 IN SRV 0 100 3268 ns1.lilzeus.net.' failed with the following error:
DNS server not authoritative for zone.
The router assigns address, 192.168.0.101, to the server. The address, 68.58.103.37, is the IP for the WAN/router. My server's TCP/IP is set to dynamic at the moment. Here are some pics of my DNS setup:
I got rid of this problem by setting the forward lookup zone to allow dynamic updates BUT it ended up changing the IP address for the ns1 record to a 192.168.0.101 address which killed the websites.
What can I do to set this straight? I have been trying different settings for a while now.