We have a AD server that is doing DNS for us on the inside and then we have
forwards to the ISP for external requests (web surfing)

The AD server DNS entry is set to it's self.. not sure that is correct but
has been that way for some time.

We currently are experince slowness in DNS request's.. and sometime's we
aren't getting the pages to displayed..

I have verified this not to be a bandwidth issue..

Does anyone have any thought's on this.. or places to start.. Event log
doesn't show much.

"Stup88" <Stup88@discussions.microsoft.com> wrote in message
news:13567EDE-5262-4562-A760-A89A416A279D@microsoft.com...
> We have a AD server that is doing DNS for us on the inside and then we
> have
> forwards to the ISP for external requests (web surfing)
>
> The AD server DNS entry is set to it's self.. not sure that is correct but
> has been that way for some time.

Correct and irrelevant to it's performance AS A DNS Server.

> We currently are experince slowness in DNS request's.. and sometime's we
> aren't getting the pages to displayed..
>
> I have verified this not to be a bandwidth issue..
>
> Does anyone have any thought's on this.. or places to start.. Event log
> doesn't show much.

Start with NSlookup against EACH specific DNS server involved and
determine if any of them are slow when asked a direct question...

nslookup -time=1 internal.domain.com Internal.DNS.IP.Address

nslookup -time=1 external.domain.com ISP.DNS.IP.Address

etc.

Keep changing the time parameter until you see the speed -- and try
any other DNS servers involved (e.g., additional ISP or internal DNS
servers.)

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

Thanks for your . I ran both ttest's and they don't seem to be delayed at
all.
I get the response back really quick.. Does the -time have a max number ?

I also ran a DCDiag /c and everything is good. So time to move on to the
next thing.

Thanks


"Herb Martin" wrote:

>
> "Stup88" <Stup88@discussions.microsoft.com> wrote in message
> news:13567EDE-5262-4562-A760-A89A416A279D@microsoft.com...
> > We have a AD server that is doing DNS for us on the inside and then we
> > have
> > forwards to the ISP for external requests (web surfing)
> >
> > The AD server DNS entry is set to it's self.. not sure that is correct but
> > has been that way for some time.
>
> Correct and irrelevant to it's performance AS A DNS Server.
>
> > We currently are experince slowness in DNS request's.. and sometime's we
> > aren't getting the pages to displayed..
> >
> > I have verified this not to be a bandwidth issue..
> >
> > Does anyone have any thought's on this.. or places to start.. Event log
> > doesn't show much.
>
> Start with NSlookup against EACH specific DNS server involved and
> determine if any of them are slow when asked a direct question...
>
> nslookup -time=1 internal.domain.com Internal.DNS.IP.Address
>
> nslookup -time=1 external.domain.com ISP.DNS.IP.Address
>
> etc.
>
> Keep changing the time parameter until you see the speed -- and try
> any other DNS servers involved (e.g., additional ISP or internal DNS
> servers.)
>
> --
> Herb Martin, MCSE, MVP
> http://www.LearnQuick.Com
> (phone on web site)
>
>
>

"Stup88" <Stup88@discussions.microsoft.com> wrote in message
news:2D6A9D21-33A6-4505-A020-50949AB13AE3@microsoft.com...
> Thanks for your . I ran both ttest's and they don't seem to be delayed
> at
> all.
> I get the response back really quick.. Does the -time have a max number ?

Nothing small enough to matter but after about 10 or 20 seconds I consider
the
DNS Server to be unusuable or in need of some correction.

> I also ran a DCDiag /c and everything is good. So time to move on to the
> next thing.

Ok.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

Stup88, did you ever pinpoint the problem?

I've had the same problem more than once in the past with a similar setup.
And I must say I've never come up with a magic answer.

Coincidentally today I just installed a new single-server domain today and
it seems more sluggish if I point the DHCP clients to use Windows Server for
DNS rather than pointing them to the ISP's DNS. I didn't have a chance to
really troubleshoot it yet.

I was curious to see if you learned/resolved anything?

-Rich

"Herb Martin" <news@learnquick.com> wrote in message
news:uharH4%23ZHHA.4948@TK2MSFTNGP05.phx.gbl...
>
> "Stup88" <Stup88@discussions.microsoft.com> wrote in message
> news:2D6A9D21-33A6-4505-A020-50949AB13AE3@microsoft.com...
>> Thanks for your . I ran both ttest's and they don't seem to be
>> delayed at
>> all.
>> I get the response back really quick.. Does the -time have a max number ?
>
> Nothing small enough to matter but after about 10 or 20 seconds I consider
> the
> DNS Server to be unusuable or in need of some correction.
>
>> I also ran a DCDiag /c and everything is good. So time to move on to the
>> next thing.
>
> Ok.
>
> --
> Herb Martin, MCSE, MVP
> http://www.LearnQuick.Com
> (phone on web site)
>

"Herb Martin" <news@learnquick.com> wrote in message
news:OfyoMK2ZHHA.4684@TK2MSFTNGP05.phx.gbl...
>
> Start with NSlookup against EACH specific DNS server involved and
> determine if any of them are slow when asked a direct question...
>
> nslookup -time=1 internal.domain.com Internal.DNS.IP.Address
>
> nslookup -time=1 external.domain.com ISP.DNS.IP.Address
>
> etc.
>
> Keep changing the time parameter until you see the speed -- and try
> any other DNS servers involved (e.g., additional ISP or internal DNS
> servers.)

Herb,

I may try your commands when I get back on-site where I may have a problem.
I tried them at home and wasn't sure if I was doing it right.

I always get the same results regardless of whether I use -time=1 or 10 or
100. I don't understand what I'm supposed to see when you say "until you
see the speed". And what is the meaning of -time?

Here are some examples I tried:

1) c:\>nslookup -time=1 acme.com 10.10.10.10
Server: sc420.acme.com
Address: 10.10.10.10

Name: acme.com
Address: 10.10.10.10

2) c:\>nslookup -time=1 dell.com 10.10.10.10
Server: sc420.acme.com
Address: 10.10.10.10

Non-authoritative answer:
Name: dell.com
Addresses: 143.166.224.244, 143.166.83.38

Thanks for the !

-Rich

"Rich Roller" <rich@*REMOVE-THIS*r2c.com> wrote in message
news:uVVpRV2aHHA.1508@TK2MSFTNGP06.phx.gbl...
> "Herb Martin" <news@learnquick.com> wrote in message
> news:OfyoMK2ZHHA.4684@TK2MSFTNGP05.phx.gbl...
>>
>> Start with NSlookup against EACH specific DNS server involved and
>> determine if any of them are slow when asked a direct question...
>>
>> nslookup -time=1 internal.domain.com Internal.DNS.IP.Address
>>
>> nslookup -time=1 external.domain.com ISP.DNS.IP.Address
>>
>> etc.
>>
>> Keep changing the time parameter until you see the speed -- and try
>> any other DNS servers involved (e.g., additional ISP or internal DNS
>> servers.)
>
> Herb,
>
> I may try your commands when I get back on-site where I may have a
> problem. I tried them at home and wasn't sure if I was doing it right.
>
> I always get the same results regardless of whether I use -time=1 or 10 or
> 100. I don't understand what I'm supposed to see when you say "until you
> see the speed". And what is the meaning of -time?

-t = provides a timeout -- NSLookup only waits 2 seconds by default which is
the equivalent of -t=2.

> Here are some examples I tried:
>
> 1) c:\>nslookup -time=1 acme.com 10.10.10.10
> Server: sc420.acme.com
> Address: 10.10.10.10
>
> Name: acme.com
> Address: 10.10.10.10

Works fine -- and within 1 second due to time parameter.


> 2) c:\>nslookup -time=1 dell.com 10.10.10.10
> Server: sc420.acme.com
> Address: 10.10.10.10
>
> Non-authoritative answer:
> Name: dell.com
> Addresses: 143.166.224.244, 143.166.83.38

Good again, and since you asked the same question your (internal) DNS
server resolved it from "cache" (i.e., non-authoritative answer) this time.

> Thanks for the !
>
> -Rich
>
>
>