DNS Question

[Netman06]

Hello,

I have an issue with multiple ip addresses, showing up on our primary dns server.

mydomain is say for testing local.ad

for our HP teaming connection x 3
1 for nic 1
1 for nic 2
1 for HP teaming connection
1 for MS cluster ip address

Only one of these are setup with register this connection in DNS, so how are these registering them selfs.

Also should my PTR records have .ad appended to it, also should my forward lookup zones be domainname with appended .ad also? local.ad

Thanks,


Mike

 

[ITPangaeaArchitect]

is this a DC?

-Brandon Wilson
MCSE:Security00/03
MCSA:Messaging00
MCSA:Security03
A+

 

[Netman06]

Yes, This is a DC Windows Server 2003 R2 64-Bit.

Thanks,

Mike

 

[ITPangaeaArchitect]

#1 you cant have a DC running cluster services
#2 a DC can only have one NIC enabled at a time (not counting NIC teaming), with one IP address assigned to that NIC (it should also be at the top of the binding order)

why its happening:

netlogon service - the netlogon service registers A, PTR, and SRV resource records for the DC. The more IP addresses you have, the greater the likelihood that netlogon will assign an SRV record to the wrong interface and cause any number of critical problems, including complete business down issues. in addition to the netlogon service, the dhcp client service will register A records for additional interfaces that have registration enabled via the checkbox. The netlogon service does not care whatsoever about that checkbox.



for your dns question:

if you install dns before a dcpromo, or during, the dns zone with the fully qualified domain name will be created automaticcally, including the _msdcs zone. This equates to, for example, using .ad as you were in place of .com or whatever, ParentDomain.ad & _msdcs.ParentDomain.ad. This assumes your domain was created properly and is not a single label domain name (also not supported). This menas domain.com and not just domain for a name.

records that are created here are typically displayed as the netbios name, but the true dns name is always machine.parentdomain.ad.

If your DNS console is showing fully qualified domain names, be sure you dont have a disjointed namespace on your DC, or whatever system is showing with the .ad. Can't remember off the top of my head if there is a view option to see FQDN instead of

-Brandon Wilson
MCSE:Security00/03
MCSA:Messaging00
MCSA:Security03
A+