Multi-home machine showing up twice on dns server

  • Thread starter Thread starter tshad
  • Start date Start date
T

tshad

We have a W2k server that houses our dns server. We have a web server with
Nic cards in it (10.0.1.10) and (10.0.3.10). Both addresses are showing up
in the DNS Lookup zone for our Domain.

We have tried to delete it but it keeps coming back.

How do we get rid of one of the addresses?

Thanks,

Tom
 
tshad said:
We have a W2k server that houses our dns server. We have a web server
with Nic cards in it (10.0.1.10) and (10.0.3.10). Both addresses are
showing up in the DNS Lookup zone for our Domain.

We have tried to delete it but it keeps coming back.

How do we get rid of one of the addresses?
Click to expand...

There is a check box on the DNS (Advanced) Properties
of each NICs IP settings. Clear the box for "Register this
Connection" on the one you do not wish to register.

OR (I do this): Give the other NIC-DNS setting a connection
specific DNS name, add the check for "register connection
specific DNS name", and leave the registration box checked.
 
Don't delete it. Go to the server properties page from the DNS snap-in
and disable round-robin. Make sure netmask ordering is enabled. Then you
will correctly resolve the server's IP address on the local subnet of
the machine making the DNS query.

...kurt
 
Herb Martin said:
There is a check box on the DNS (Advanced) Properties
of each NICs IP settings. Clear the box for "Register this
Connection" on the one you do not wish to register.
Click to expand...

Looks good. I'll give it a try tomorrow.
OR (I do this): Give the other NIC-DNS setting a connection
specific DNS name, add the check for "register connection
specific DNS name", and leave the registration box checked.
Click to expand...
Where is this?

Are you talking about the "DNS suffix for this Connection" entry on the same
page as the check box?

Thanks,

Tom
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Thanks,

Tom
Click to expand...
Click to expand...
 
Kurt said:
Don't delete it. Go to the server properties page from the DNS snap-in
and disable round-robin. Make sure netmask ordering is enabled. Then you
will correctly resolve the server's IP address on the local subnet of
the machine making the DNS query.
Click to expand...

What does "Round Robin" do and why would I want to disable it?

Thanks,

Tom
 
Kurt said:
What does "Round Robin" do and why would I want to disable it?
Click to expand...

That answer was off the mark -- it won't solve
the request you made to delete (or prevent) the
registration of the second NIC.

It is also generally askew since both Round Robin
and Netmask Ordering can be enabled together with
Netmask Ordering taking precedence.

And this would not necessarily work anyway, depending
on your actual subnets.

Your settings are on the Advanced->DNS tab for the
NIC->IP properties where you can stop registration or
set a connection specific name to register the machine's
extra NIC under another name.
 
Kurt said:
Don't delete it. Go to the server properties page from the DNS snap-in
and disable round-robin. Make sure netmask ordering is enabled. Then you
will correctly resolve the server's IP address on the local subnet of
the machine making the DNS query.

..kurt
Click to expand...
Round Robin tells the DNS server to provide multiple addresses in
revolving order. So if you have 3 NICs on server01 at 192.168.0.1,
192.168.1.1, and 10.1.1.1, DNS queries will be answered (as the primary
address):

First query:
192.168.0.1
Next query
192.168.1.1
then
10.1.1.1

If you disable it and netmask ordering is enabled, a query for server01
from a computer who's address is 10.1.23.105 will be resolved to
10.1.1.1. Herb may be right that you can force netmask ordering to be
applied before round robin, but this works for me. (netmask ordering
tells the server to resolve the query to the IP address of the interface
closest to the IP address the query came from). I have a triple homed DC
plus other multi-homed servers that must resolve to IP address on the
same subnet as the querying computer (obviously). There are situations
where this won't work, like if you have routed segments where netmask
ordering would resolve to an IP address to which there is no route. But
on multiple non-routed segments, this works great for me.

....kurt
 
Back
Top