Re: DNS Registration on a domain controller

Hi Austin and Jorge,

My problem seems to be solved.
Here's what we've made.
We deleted the A record pointing to the wrong interface. There were only
one record with the wrong address. There were no domain record on the wrong
address.
We disabled the listening on the wrong interface for the DNS server.
We leaved only TCP/IP bound the interface.
We ran "ipconfig /registerdns" and the record was not recreated.
We've done this yestarday morning and the record is still not recreated so I
assume it is correct.

Many thanks for your help on this.
Dominic
"Austin Osuide" wrote:

Hi Dominic,
Also untick "Client for Microsoft Networks".
Only TCP/IP should be selected.

Regards,

Austin

"Dominic" <Dominic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1F79293E-0797-4D63-914E-DE82C0ED2A80@xxxxxxxxxxxxxxxx
Hi Austin,

Many thanks again for your help.

We have deleted the record and unbound F&P Sharing. The record have been
recreated anyway.

You are right, what we want here is that only TCP/IP to be bound to the
interface and the record in DNS for this interface should not be created.

The binding order is correct.

In the KB272294, it says we need to disable round robin on the DNS server.
We need this enabled because we use it for another system.
Can I leave this enabled ? Anyway, if the record isn't created, we should
not need to disable it...

Dominic

"Austin Osuide" wrote:

Ah,
What's happens when you delete the record registered for that interface
in
DNS and then untick F&P sharing?
Since the interface shouldn't be registered in DNS, you need to delete it
from DNS (unless you are saying unticking F&P sharing does not also
affect
the auto DNS registration of that interface). It should be selected on
the
Interface you want to use for domain coms though.
My thinking is, you want only TCP/IP traffic on the 2nd interface and you
do
not want this registered in DNS. unticking the "register this interface
in
DNS" should do the trick. but you're not seeing that. Check the adapter
binding order as well and make sure the 1st NIC has precedence.
This KB might give you an idea: http://support.microsoft.com/kb/272294

Regards,

Austin


"Dominic" <Dominic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:708B4E18-AC91-4EDB-A0C7-F4914B01CFAA@xxxxxxxxxxxxxxxx
Hi Austin,

Thanks for the quick reply !
We already have tried that and it has caused us a great deal of
troubles.
When only TCP/IP is bound to the NetCard2, domain users can't log in on
member servers. The computer queries the DNS, it sometimes receives
the
IP
address of NetCard2. If "File and Print Sharing" is not bound to the
NetCard2, no authentication is possible on the interface.

Dominic

"Austin Osuide" wrote:

Hi Dominic,
Do you have "File and Printer Sharing" installed on the NIC?
If you do, uncheck it and have only TCP/IP installed and the DNS
registration unchecked. That will help.

Regards,

Austin

"Dominic" <Dominic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:460A6541-B2F9-4105-BDEE-BB9D9AB2D1A4@xxxxxxxxxxxxxxxx
Hi Jorge,

"Register this connection's addresses in DNS" is already uncheck on
NetCard2.
The problem is that NetLogon register the address of NetCard2 in DNS
even
if
this is unchecked.

The fact to restrict the listening on NetCard2 for the DNS service
haven't
changed the behavior of the NetLogon Service.

Thanks again,
Dominic

"Jorge Silva" wrote:


Uncheck the "Register this connection's addresses in DNS" in the
advanced
TCP/IP options on NetCard2.
Than you can restrict DNS service for selected IP addresses under
DNS
properties. When this feature is used, the DNS Server service only
listens
for and answers DNS requests that are sent to the IP addresses
specified
on
the Interface tab in Server properties.
Does this help?
--
===================================
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
===================================

"Dominic" <Dominic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E25CA637-790A-458B-937C-DD764C420E4B@xxxxxxxxxxxxxxxx
Thanks Jorge for the quick answer !

KB246804 will stop the registration for all interfaces. We do
not
want
this. We want to only block the DNS registration for one network
interface.

KB275554 applies only to Windows 2000...

Any other hint ?
Thanks again,
Dominic

"Jorge Silva" wrote:

Hi
Check if helps
http://support.microsoft.com/?id=246804
http://support.microsoft.com/?id=275554


--
===================================
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
===================================

"Dominic" <Dominic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:10580005-57A3-4B71-9F97-C8026576C2E8@xxxxxxxxxxxxxxxx
Hi All,

We have a multihomed domain controller. NetCard1 for the
production
network
and NetCard2 for our backup network.

We do not want the DHCP Service and the Netlogon service to
register
in
DNS
the IP address of NetCard2 since we do not want clients
computer
to
be
redirected to the IP address in the backup network.

Our DC is Windows Server 2003 R2 Std SP2 with all current
updates.

We saw the hotfix KB832478 that was supposed to solve the
problem
and
it
is
pre-SP1. This hotfix obviously don't install on our DC since
it
has
SP2,
but
the probleme is still present.

We and uncheck the "Register this connection's addresses in
DNS"
in
the
advanced TCP/IP options on NetCard2 and it stills register.

We don't want to disable the automatic DNS registrations on
NetCard1
since
we'll have to do it manually.

Anyone having a clue on this ?
Thanks,
Dominic












.

Relevant Pages

  • Re: DNS Registration on a domain controller
    ... connection's address in DNS"., also make sure that no DNS are define. ... MCSE, MVP Directory Services ... When only TCP/IP is bound to the NetCard2, domain users can't log in on ... The problem is that NetLogon register the address of NetCard2 in DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Registration on a domain controller
    ... interface and the record in DNS for this interface should not be created. ... it says we need to disable round robin on the DNS server. ... When only TCP/IP is bound to the NetCard2, domain users can't log in on ... "Register this connection's addresses in DNS" is already uncheck on ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Registration on a domain controller
    ... "Register this connection's addresses in DNS" is already uncheck on NetCard2. ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Registration on a domain controller
    ... Uncheck the "Register this connection's addresses in DNS" in the advanced ... TCP/IP options on NetCard2. ... Than you can restrict DNS service for selected IP addresses under DNS ... redirected to the IP address in the backup network. ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Registration on a domain controller
    ... When only TCP/IP is bound to the NetCard2, domain users can't log in on ... uncheck it and have only TCP/IP installed and the DNS ... The problem is that NetLogon register the address of NetCard2 in DNS even ...
    (microsoft.public.windows.server.active_directory)