I'm managing a small enterprise network that has a an SBS 2003 server.
There are multiple unsolved issues of which the DNS problem is the most impacting one.
Problem is that if ISP or gateway's IPes are not added on the worksations as secondary DNS server (and even on the server itself), Internet browsing is a nightmare (pages need to be refreshed 2/3 times to fullly load, when they load ...). I know there should only be the SBS server as primary DNS server, but this is not sustainable.
There is only one SBS 2003 server acting as DC, DNS and Echange server. Server is configured with its own IP address as DNS and nothing else (192.168.1.200).
Primary DNS server of the SBS server is himself
Forwarders are also configured.
On PCs, I needed to add the ISP's gateway IP address (192.168.1.1) as second DNS entry to allow normal Internet browsing.
Behaviour is the same on the server itself: as soon as the ISP gateway's IP address is added as second DNS entry (which I didn't do), normal Internet browsing is possible, otherwise not !
Forward and reverse lookup zone are there
I have already rebuilt DNS but it didn't change anything
I dond't find particular DNS error messages in the DNS log
IPCONFIG is OK
What is interesting to know:
nslookup is NOT working fine with one primary DNS server only (tilming out 3 times out of 4)
Once a day in average, I have error 2013 in the system log: "SMTP could not connect to any DNS server. Either none are configured, or all are down. "
I have no _msdc.domain.local forward lookup zone, Could this be the problem?