Multi-homed server and DNS

  • Thread starter Thread starter Neil Bullock
  • Start date Start date
N

Neil Bullock

Hello,

I am having a problem with a new domain controller (and
new domain) using existing DNS servers. The new DC has
two network cards, one internal and one for external
things. This DC does not handle DNS itself, but relies on
two other DCs in another AD domain, in another tree (but
the same forest).

As you would expect, the DC with two network cards
registers both of the network cards in DNS. The problem
comes about because it appears to ignore the checkbox
telling it not to register the external-facing NIC in
DNS. This means that things can only resolve the domain
name 50% of the time (because of round-robin). Are there
any common causes for this sort of behaivour and/or
anything I can do about it without turning off round-
robin? I've looked fairly extensively and not found
anything.

Thanks,
Neil.
 
In
Neil Bullock said:
Hello,

I am having a problem with a new domain controller (and
new domain) using existing DNS servers. The new DC has
two network cards, one internal and one for external
things. This DC does not handle DNS itself, but relies on
two other DCs in another AD domain, in another tree (but
the same forest).

As you would expect, the DC with two network cards
registers both of the network cards in DNS. The problem
comes about because it appears to ignore the checkbox
telling it not to register the external-facing NIC in
DNS. This means that things can only resolve the domain
name 50% of the time (because of round-robin). Are there
any common causes for this sort of behaivour and/or
anything I can do about it without turning off round-
robin? I've looked fairly extensively and not found
anything.

Thanks,
Neil.
Click to expand...

You will have to disable dynamic registration on that NIC IIRC you can do it
on a per interface basis. 246804 - How to Enable/Disable Windows 2000
Dynamic DNS Registrations
http://support.microsoft.com/default.aspx?scid=kb;EN-US;246804&FR=1
 
Back
Top