DNS issue Windows Server 2008
We have a simple configuration.
Server 2008 R2, File Server, Domain Controller, DHCP Server.
Terminal Server (Citrix), Server 2008 R2.
Exchange Server 2007.
Print Server.
We changed ISP recently, and now internet connection on the File Server is extremely slow, but ok after connecting.
The workstations on the LAN appeared to lose internet connection unless I changed their DNS Primary & Secondary to the DNS server of the new ISP provider, then all is well. Before IP & DNS were obtained automatically.
The primary DNS on the Files Server is 127.0.0.1, Secondary is the IP of the new ISP DNS server.
The DNS cache on the file server has been cleared.
Any ideas as to how to resolve this
Server 2008 R2, File Server, Domain Controller, DHCP Server.
Terminal Server (Citrix), Server 2008 R2.
Exchange Server 2007.
Print Server.
We changed ISP recently, and now internet connection on the File Server is extremely slow, but ok after connecting.
The workstations on the LAN appeared to lose internet connection unless I changed their DNS Primary & Secondary to the DNS server of the new ISP provider, then all is well. Before IP & DNS were obtained automatically.
The primary DNS on the Files Server is 127.0.0.1, Secondary is the IP of the new ISP DNS server.
The DNS cache on the file server has been cleared.
Any ideas as to how to resolve this
Natty Greg
File server needs static ip address, and its preferable not to use the loop back address, which is built in into every computer.
ASKER
The File server has a static IP address.
Should I use the DNS server IPs of the new ISP for both Primary & Secondary DNSs ?
Should I use the DNS server IPs of the new ISP for both Primary & Secondary DNSs ?
The primary dns should be your local dns, and the secondary should be that of the isp, reason you want local look ups to your local dns and if the lockup requires external help it will go through the isp dns
It depends on how many the domain controllers that you have ,your primary and secondary static IP's should be those of your internal DNS servers. Then your DNS servers should have as their forwarding IP's the address of the ISP DNS servers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Excellent clear answer.
Remove ISP DNS server IP from lan card properties on DC, since it is the culprit
Point DC server to its own IP in DNS (not 127.0.0.1) and restart netlogon service and dns service
Put public dns server IP as forwarder
On domain controllers, to get internet name resolution you must use either forwarders OR root hints
Point DC server to its own IP in DNS (not 127.0.0.1) and restart netlogon service and dns service
Put public dns server IP as forwarder
On domain controllers, to get internet name resolution you must use either forwarders OR root hints