DNS server order in TCP/IP settings when mixing local and remote (ISP) DNS servers

[Ratmoler Hamstak]

Sorry for the confusing subject, couldn't figure out a concise
description.

I have a Windows 2000 Server with Active Directory and DNS installed
and running. I also have a Win2K Pro workstation (located on the same
network) whose TCP/IP settings establish multiple DNS servers: one
local (the Win2K server) and three belonging to my ISP.

The problem is that in attempting to access a VS.NET project located
on the server I may only do so if this server's IP address is listed
first in the DNS list of the TCP/IP settings for the workstation. If
the server is shut off (which it is most of the time), then there is a
long delay when I attempt to open Internet Explorer (presumably the OS
is attempting to locate the local DNS server before skipping to the
next DNS server listed). If my local server is listed 2nd or later,
then I am not able to connect to the VS.NET project (or more simply to
website through shorthand, http://mysitename).

Keeping the server on all the time is not an option. This being the
case, is it (1) possible to reduce the amount of time the OS takes to
locate a DNS server before it gives up and attempts to access the next
one in the list or (2) ensure that a name resolving to a local IP
address will not attempt to be resolved agasint a remote DNS server?

Any other suggestions? I am sure you will let me know if I am not
being clear

Thanks,
Tom McCoid

 

[Ace Fekay [MVP]]

In

Sorry for the confusing subject, couldn't figure out a concise
description.

I have a Windows 2000 Server with Active Directory and DNS installed
and running. I also have a Win2K Pro workstation (located on the same
network) whose TCP/IP settings establish multiple DNS servers: one
local (the Win2K server) and three belonging to my ISP.

The problem is that in attempting to access a VS.NET project located
on the server I may only do so if this server's IP address is listed
first in the DNS list of the TCP/IP settings for the workstation. If
the server is shut off (which it is most of the time), then there is a
long delay when I attempt to open Internet Explorer (presumably the OS
is attempting to locate the local DNS server before skipping to the
next DNS server listed). If my local server is listed 2nd or later,
then I am not able to connect to the VS.NET project (or more simply to
website through shorthand, http://mysitename).

Keeping the server on all the time is not an option. This being the
case, is it (1) possible to reduce the amount of time the OS takes to
locate a DNS server before it gives up and attempts to access the next
one in the list or (2) ensure that a name resolving to a local IP
address will not attempt to be resolved agasint a remote DNS server?

Any other suggestions? I am sure you will let me know if I am not
being clear

Thanks,
Tom McCoid

Sounds clear enough. Maybe use a HOSTS files with the necessary data for the
records that you need when the server is down. If using AD, it's wise only
to use your internal DNS for AD functionality. If not, well, toggling DNS
addresses back and forth ain;'t much fun.

--
Regards,
Ace

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

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

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================

 

[Jonathan de Boyne Pollard]

RH> I [...] have a Win2K Pro workstation [...] whose TCP/IP settings
RH> establish multiple DNS servers: one local (the Win2K server) and
RH> three belonging to my ISP.

Don't do that.

<URL:http://homepages.tesco.net./~J.deBo...nt-all-proxies-must-provide-same-service.html>

RH> Keeping the server on all the time is not an option.

Then it isn't suitable for supplying DNS service.

"Doctor, it hurts when I turn my DNS server off!"