Re: Router pointing to Windows DNS Server: OK?
- From: "Rich Roller" <rich@*REMOVE-THIS*r2c.com>
- Date: Fri, 21 Oct 2005 22:42:55 -0400
Thanks for the quick feedback Kevin. Very helpful.
See my comments/questions in-line below...
"Kevin D. Goodknecht Sr. [MVP]" <admin@xxxxxxxxxxxxxx> wrote in message
news:uZAUtxq1FHA.3204@xxxxxxxxxxxxxxxxxxxxxxx
> Rich Roller <rich@*REMOVE-THIS*r2c.com> wrote:
>> I've got a new, tiny, single-server WS2003 SP2 domain which has
>> periodic major slowdowns with external Internet communications. I'm
>> running "ping -t www.dell.com" and when it's good it's at 50ms but
>> several times a day it'll go to 800-1400ms!
>>
>> If I reboot the Netgear router/gateway it usually fixes it and the
>> ping's go back to 50ms. The same seems true if I reboot the Verizon
>> DSL box. So I'm not sure where the problem lies but I'm wondering
>> about the router, and in particular how it points to the internal DNS
>> server.
>>
>> The router is also being the DHCP Server (I may change this over the
>> the WS2003 DC soon). But with this router there is only one place
>> you can enter static DNS servers. I have entered 10.11.0.21 (WS2003
>> DC/DNS) and 151.202.0.85 (Verizon). These same DNS entries get used
>> by it's DHCP server function and given out to the client PC's.
>
> You are right you should move DHCP to the Win2k3 server, because you
> cannot
> use Verizones DNS on any client in any position.
> All client should use the server's IP for DNS, you can use the router or
> Verizon as a forwarder for the Win2k3 DNS.
I guess the rationale for the clients having DNS as 1=DC, 2=ISP was for
fault tolerance. In a single server network if the clients only point DNS
to the DC and if it goes down then no-one can access the Internet. (a 2nd
server is not in the cards unfortunately for budget & political reasons)
>
>> So is there anything fundamentally wrong with this design, especially
>> with the static DNS entries on the router?
>
> The router should use the ISP for DNS, the server can forward to the
> router.
> No client should use the router for DNS, this is the problem with using
> DHCP
> on the router.
What are the pros/cons of having WS2003 DNS Server forwarders to router vs.
direct to ISP?
Also, do you think that the periodic slowness they've been experiencing is
due to the above configuration? My hunch said probably, but I couldn't
figure the reason, since the DNS actually seems to resolve fine... it's just
the response time from the target host which is slow. And why would it be
periodic and why would rebooting the router or DSL fix it temporarily?
The last questions are a little academic and so perhaps not as critical, if
in fact I can solve the speed problems through DNS changes.
-Rich
.
- Follow-Ups:
- Re: Router pointing to Windows DNS Server: OK?
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: Router pointing to Windows DNS Server: OK?
- References:
- Router pointing to Windows DNS Server: OK?
- From: Rich Roller
- Re: Router pointing to Windows DNS Server: OK?
- From: Kevin D. Goodknecht Sr. [MVP]
- Router pointing to Windows DNS Server: OK?
- Prev by Date: Re: DNS Problems
- Next by Date: Re: Trying to connect W2k3 file server with W2k3 DC with no luck
- Previous by thread: Re: Router pointing to Windows DNS Server: OK?
- Next by thread: Re: Router pointing to Windows DNS Server: OK?
- Index(es):
Relevant Pages
|
