asked on

Windows SBS 2003 DNS issue

We changed ISPs and the gateway address our network and now the SBS DC is struggling to route DNS requests to the correct provider.

We updated the Server DNS to forward to the new DNS for the new ISP. The update took effect immediately and outbound DNS requests were served just fine. This works fine all day. But every morning since we made the change, we have to re-boot the Windows Server in order to restore DNS to the computers on the LAN.

What could be happening overnight to knock out DNS on the server?

Cliff Galiher

First guess, someone incorrectly added ISP DNS servers to DHCP so when the leases renew, problems arise until ther server reboots and AD asserts its will.

Karl

when you say forward to the isp dns, have you hard coded their IP into the forwarder on the server DNS?

d4nnyo

ASKER

cgaliher: In fact DHCP is not set up on the server. There are no servers set up in the DHCP list. Previous admin left DHCP to the router -- network was running fine. Perhaps this is the real source of the problem.

But all wired workstations have Static IP with DNS pointed at the SBS. Only wifi guests pick up DHCP.

karliangston: DNS/Server/Properties/Forwarders tab -- this is where I replaced previous ISP DNS with new ISP DNS.

Rob Williams

If the SBS is not your only DNS server they will not get the updates. They are likely using the router's configuration.
Firstly the server should be updated by running the connect to the Internet wizard under server management | Internet and e-mail.
Then you should have the SBS as the DHCP server so that it can hand out all the necessary scope options IP, net mask, gateway, DNS, WINS, and DNS suffix.

d4nnyo

ASKER

2nd NIC on the server was enabled, somehow bringing down DNS requests on the server overnight. Disabled the NIC, solved the problem.

ASKER CERTIFIED SOLUTION

Rob Williams

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial