Long Pause Before FQDN gets Resolved Using Forwarders - Why?

  • Thread starter Thread starter NewUser
  • Start date Start date
N

NewUser

Dear Group,

After having read the Microsoft FAQ on setting up DNS with AD. I
removed all DNS from all NICs in the domain. Pointed all internal
servers and clients to the internal Name Server and set up the Name
Server with forwarders to my ISP's DNS servers.

Now that I've done that, the all web traffic has a 3 to 5 second pause
before the page begins to build. This was not that case before. Any
ideas on why this is happening? I know that the process is a little
longer now that my internal DNS has to execute a query to the ISP's
DNS.

I'm running a 2003 server with AD Integrated DNS. I have an IDSL
line. 144kbps up and down. The server is a 1.5Ghz PIII with a Gig of
Ram.

Thanks,

Keeper
 
NewUser said:
After having read the Microsoft FAQ on setting up DNS with AD. I
removed all DNS from all NICs in the domain. Pointed all internal
servers and clients to the internal Name Server and set up the Name
Server with forwarders to my ISP's DNS servers.
Click to expand...

That's right. The above includes the DCs and the DNS servers (NICs)
Now that I've done that, the all web traffic has a 3 to 5 second pause
before the page begins to build. This was not that case before. Any
ideas on why this is happening? I know that the process is a little
longer now that my internal DNS has to execute a query to the ISP's
DNS.
Click to expand...

Actually it shouldn't be noticable -- especially if you repeat the query or
refresh the page. Presumably your DNS server is on the same net,
maybe even same subnet.
I'm running a 2003 server with AD Integrated DNS. I have an IDSL
line. 144kbps up and down. The server is a 1.5Ghz PIII with a Gig of
Ram.
Click to expand...

Plenty of server -- I have a pair of weaker servers that do my DNS, and
an extra layer of forwarder between them.

DNS Client --> Internal DNS ---> Firewall DNS ---> ISP DNS

What's running on the server? Try NSLookup from the command line
without the -time parameter (default is 2 seconds).

If that fails, try it with -time=10 and see how long it takes.

Do the clients have (large) hosts files?
 
In
NewUser said:
Dear Group,

After having read the Microsoft FAQ on setting up DNS with AD. I
removed all DNS from all NICs in the domain. Pointed all internal
servers and clients to the internal Name Server and set up the Name
Server with forwarders to my ISP's DNS servers.

Now that I've done that, the all web traffic has a 3 to 5 second pause
before the page begins to build. This was not that case before. Any
ideas on why this is happening? I know that the process is a little
longer now that my internal DNS has to execute a query to the ISP's
DNS.

I'm running a 2003 server with AD Integrated DNS. I have an IDSL
line. 144kbps up and down. The server is a 1.5Ghz PIII with a Gig of
Ram.

Thanks,

Keeper
Click to expand...

It shouldn't be happening.
Try a different forwarder, such as 4.2.2.2.
Let us know if it helped.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top