Change default DNS server on client with 2 nics

[Nick Trenary]

I have a Win2k Pro machine with 2 nics. Currently the default dns server is
set to an address on nic#1. I need the default server to be one from nic#2.
How can I specify a dns server when more than one nic is involved?

Nick Trenary
Computer Information Systems Analyst
Cedar Rapid Public Library

 

[Scott Harding - MS MVP]

Remove DNS from the first NIC? Why do you have 2 NICS anyways? I this
machine a router?

 

[Doug Sherman [MVP]]

The primary DNS server can be configured on a per adapter basis. The
adapter's primary DNS server can have any IP address which is reachable from
the client machine regardless of which adapter is used to send the packets.
See:

http://www.microsoft.com/windows200...techinfo/reskit/en-us/prork/prcc_tcp_ngjq.asp

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Herb Martin]

Just received a refurbished Dell Lapttop with win2kpro
loaded and can't get full screen display. What to do?

Just do it. Take off any you don't want and add any you do.

You can even add the same one to both NICs.

DNS is a ROUTABLE service since it uses IP and therefore
it doesn't really matter as long as the DNS server is specified.

 

[Phillip Windell]

I prefer 127.0.0.1

It always works and that is what the system will default to if you don't
include one at all.

 

[Ace Fekay [MVP]]

I prefer 127.0.0.1

It always works and that is what the system will default to if you don't
include one at all.

Hi Phillip,

Its actually preferred to use tha actual IP address. The loopback will show
up if dcpromo installs DNS for you. Using the loopback also causes that
familiar 'domain not found' message when nslookup invokes. If you ever tried
to put in 127.0.0.1, it won't let you anyway. You would need to go thru the
reg to do it. But as for best practice, its recommened to use the actual IP.

Cheers!!

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[Phillip Windell]

Its actually preferred to use tha actual IP address. The loopback will show
up if dcpromo installs DNS for you. Using the loopback also causes that
familiar 'domain not found' message when nslookup invokes. If you ever tried
to put in 127.0.0.1, it won't let you anyway. You would need to go thru the
reg to do it. But as for best practice, its recommened to use the actual

IP.

I've seen it claimed both ways. I am in fact using 127.0.0.1 on a 2003 dc
in a network with only a single DC and did not have to adjust the registry.
If you leave the DNS entry blank and try to leave the dialog box it will
automatically put in 127.0.0.1, ....I don't see why it would do that if it
wan't a valid entry.

 

[Ace Fekay [MVP]]

In

I've seen it claimed both ways. I am in fact using 127.0.0.1 on a
2003 dc in a network with only a single DC and did not have to adjust
the registry. If you leave the DNS entry blank and try to leave the
dialog box it will automatically put in 127.0.0.1, ....I don't see
why it would do that if it wan't a valid entry.

If you tried to type it in, it won't accept it, saying its an ivalid IP. Try
it.

Sure, you can use it, not saying you can't and dcpromo will put it in for
you if you don't already point to yourself for DNS (it does it thru the
reg), but its not really recommended. It can also cause issues with RAS
(article below describing that). You can also ask some of the others here as
well. Here's a repost from awhile ago discussing it ...

====================
Q172060 - NSLOOKUP Can't Find Server Name for Address 127.0.0.1 -
(another good reason not to use the loopback):
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q172060&

Q254715 - RAS Clients Receive 127.0.0.1 for DNS Server Address:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q254715&

And here's a post from Thomas Lee from awhile back about it:
============================
----- Original Message -----
From: "Thomas Lee [MVP]" <[email protected]>
Newsgroups: microsoft.public.win2000.dns
Sent: Saturday, October 12, 2002 11:13 AM
Subject: Re: DNS configeration

Ipconfig /displaydns should show you that a reverse lookup for 127.0.0.1
is already in place. Set your reverse lookup to the actual IP address of
your server.

127.0.0.0 is not a valid IP address for a host. This range is always a
local loopback address.

Thomas

===================

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[Phillip Windell]

"Ace Fekay [MVP]"

it.

Well, I don't know what to tell you then. I did type it in, it did accept
it, never complained, and has ran for a long time that way. The network I
use it on only has one DC. All the Clients use the actual IP# of DC (both
DHCP, and static clients). RRAS client have never gotten the wrong IP# and
have always gotten the right DNS IP# that they should.

 

[Ace Fekay [MVP]]

"Ace Fekay [MVP]"


Well, I don't know what to tell you then. I did type it in, it did accept
it, never complained, and has ran for a long time that way. The network I
use it on only has one DC. All the Clients use the actual IP# of DC (both
DHCP, and static clients). RRAS client have never gotten the wrong IP# and
have always gotten the right DNS IP# that they should.

Interesting! Well, I guess if its not broke, don't fix it!

Its usually one of the first things I mention go change.... just in case.



Ace

 

[Phillip Windell]

Interesting! Well, I guess if its not broke, don't fix it!

Its usually one of the first things I mention go change.... just in case.

Well, if it helps, next time I will simply suggest to people that the DC
should point to itself and not specify what address they use and just leave
it up to them.

As far as the KB articles, many of them result from customer problems
resolved by the guys at PSS. On more than one occasion we couldn't verify
with absolute certainy that what we thought we did really cured the problem,
or if it was something else, or maybe just a coincidence. If an article was
written based on a such a situation it is possible that the article is wrong
or at least not entirely accurate or only partially acuarte,.....or even
just accuarte under certain very narrow conditions. So even with as high
regaurd that I hold those articles, there is still room for doubt when the
article says one thing and I see something else with my own eyes.

 

[Ace Fekay [MVP]]

In

Well, if it helps, next time I will simply suggest to people that the
DC should point to itself and not specify what address they use and
just leave it up to them.

As far as the KB articles, many of them result from customer problems
resolved by the guys at PSS. On more than one occasion we couldn't
verify with absolute certainy that what we thought we did really
cured the problem, or if it was something else, or maybe just a
coincidence. If an article was written based on a such a situation
it is possible that the article is wrong or at least not entirely
accurate or only partially acuarte,.....or even just accuarte under
certain very narrow conditions. So even with as high regaurd that I
hold those articles, there is still room for doubt when the article
says one thing and I see something else with my own eyes.

I have to agree with you. Some of the articles can be ambiguous. I remember
finding one and reporting it awhile ago. I don't remember which one it is
now, and forgot all about it.

One thing about the loopback, the nslookup message will come up alarming
some folks. I guess if not for any other reason, at least using the actual
IP will eliminate that message, provided they have a reverse zone and a PTR.

Cheers!

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.