Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4373
  • Last Modified:

Windows Server 2008R2 DNS causing slow web browsing

I have a home office Active Directory domain setup with two domain controllers and each DC is a DNS/DHCP server as well.  I have the first DNS server setup to point to itself (actual IP address as opposed to 127) and the secondary points to the secondary DNS server.

The second DNS server's DNS settings are: first DNS server points to DNS server A and the secondary DNS server points to DNS server B (which is itself).

I have forwarders setup to point to 8.8.8.8 and 8.8.8.4 which is Google's DNS servers.

How I uncovered the slow browsing was changing my computer's DNS servers to point at Googles.  Upon doing this pages load instantly as opposed to taking 3-5 seconds before loading

Here are some problems I'm having, obviously slow browsing.  Second is from my computer when I try to do a nslookup to amazon.com, google.com, various other domains, more often than not the initial request times out and then if I try again it'll go through.

Unfortunately it looks like I did not have DNS scavange stale records turned on but it is now enabled.

The two DNS servers are setup to be active directory integrated zones.  It's the basic default that is created when you setup DNS for the first time.

Any ideas?

DNS request timed out.
    timeout was 2 seconds.
*** Request to blah.blah.local timed-out
>

This is what I am getting right after I notice a site is really slow to load and then doing a nslookup.

Ok so another bit of info is that if I am going to a new page I haven't gone to in a while, say news.com which I never go to and either browse to the page or do a nslookup, it'll either be slow when browsing and then again nslookup will timeout as it's trying to obtain the DNS info.

As it stands I've removed the forwarders from my two DNS servers and only have the two DNS servers pointing to each other.
0
OBESEJESUS
Asked:
OBESEJESUS
  • 2
2 Solutions
 
OBESEJESUSAuthor Commented:
DNS request timed out.
    timeout was 2 seconds.
*** Request to blah.blah.local timed-out
>

This is what I am getting right after I notice a site is really slow to load and then doing a nslookup.

Ok so another bit of info is that if I am going to a new page I haven't gone to in a while, say news.com which I never go to and either browse to the page or do a nslookup, it'll either be slow when browsing and then again nslookup will timeout as it's trying to obtain the DNS info.
0
 
DrDave242Commented:
Is it any quicker when using root hints for external resolution as opposed to forwarders?  How about resolution of names in your domain?  Is that quick or also slow?
0
 
OBESEJESUSAuthor Commented:
Right now I've removed all forwarders and am only using root hints.  So far so good but I have a certain page that I go to that has problems and the only way to resolve that is by adding a forwarder.  Otherwise I'll keep an eye out.
0
 
MMe12Commented:
Have you tried disabling EDNS on your DNS servers?
Commandline to do so:
dnscmd /config /EnableEDNSProbes 0

See this article for more details:
http://weblogs.asp.net/owscott/archive/2009/09/15/windows-server-2008-r2-dns-issues.aspx
1

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now