> On Jan 26, 11:09*am, "Ace Fekay [MVP-DS, MCT]"
> <ace...@mvps.RemoveThisPart.org> wrote:
>> "Ploutos" <godsofwea...@gmail.com> wrote in message
>>
>> news:8d2e1d6c-a214-4a86-b287-...
>>
>>> I have a few domain controllers in a domain that will not hold SRV
>>> records. *I run Netdiag /fix and the SRV records are present for
>>> awhile, but then they go away (less than a day, usually shorter). *I
>>> have no errors in any eventviewers. *I find the error on a DCDIAG /
>>> test:dns, which fails on Records Registration. *I have read other
>>> posts related to this referring to W2K but we are all 2003.
>>> W2k3 Domain Functional Level.
>>> About 40 Domain Controllers with the problem on about 6
>>> Not a single label domain
>>> Disabled Unused NIC's and moved primary NIC to first in list
>>> Scavenging is 3 no-refresh and 6 for refresh
>>> Any tips would be greatly appreciated.
>>
>> Are you inmplying that some of your DCs are multihomed? If so, this scenario
>> is unfortunately problematic with domain controllers. If the DCs are
>> multihomed, please read my blog on this, why it is happening, and how to
>> configure your DCs, if you want to keep them multihomed.
>>
>> Multihomed DCs with DNS, RRAS, multiple IPs, and/or PPPoE
>> adaptershttp://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-wi...
>>
>> To better help diagnose what's going on, please post:
>>
>> 1.An unedited ipconfig /all from one of the problem DCs
>> 2. An ipconfig /all from a working DC
>> 3. Any EventID# errors that are occuring
>> 4. Any services disabled, such as the DHCP Client service?
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit among
>> responding engineers, and to help others benefit from your resolution.
>>
>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
>> MCSA 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>> Microsoft MVP - Directory Services
>>
>> If you feel this is an urgent issue and require immediate assistance, please
>> contact Microsoft PSS directly. Please checkhttp://support.microsoft.com
>> for regional support phone numbers.
>
> I read your blog, but our set up is all internal. There is only one
> functional NIC on all DC's, the second nic points to IP's on the same
> subnet, no gateway, but the NIC is disabled.
>
> 1.An unedited ipconfig /all from one of the problem DCs
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : ALLDNT10
> Primary Dns Suffix . . . . . . . : omi.com
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : omi.com
> adroot.net
> om-inc.com
> omi
> omi-inc
>
> Ethernet adapter LAN:
>
> Connection-specific DNS Suffix . : omi.com
> Description . . . . . . . . . . . : HP NC7781 Gigabit Server
> Adapter #2
> Physical Address. . . . . . . . . : 00-11-85-6B-B5-B7
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 10.176.100.6
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 10.176.100.1
> DNS Servers . . . . . . . . . . . : 10.176.100.6
> 167.213.174.20
> 167.213.242.67
> Primary WINS Server . . . . . . . : 167.213.174.20
> Secondary WINS Server . . . . . . : 167.213.242.67
> -------------------------------------------------------------------------------------
> 2. An ipconfig /all from a working DC
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : MINDNT10
> Primary Dns Suffix . . . . . . . : omi.com
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : omi.com
> adroot.net
> om-inc.com
> omi
> om-inc
>
> Ethernet adapter Lan:
>
> Connection-specific DNS Suffix . : omi.com
> Description . . . . . . . . . . . : HP NC7781 Gigabit Server
> Adapter #2
> Physical Address. . . . . . . . . : 00-11-0A-E9-E9-50
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 10.61.100.6
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 10.61.100.1
> DNS Servers . . . . . . . . . . . : 10.61.100.6
> 167.213.174.20
> 167.213.242.67
> Primary WINS Server . . . . . . . : 167.213.174.20
> Secondary WINS Server . . . . . . : 167.213.242.67
> ----------------------------------------------------------------------------------------------------
> 3. Any EventID# errors that are occuring
>
> No event errors.
>
> 4. Any services disabled, such as the DHCP Client service?
>
> DHCP Client Service enabled on both, comparison of all services are
> the same.
Hello Ploutos,
Actually multihoming doesn't just include a NIC pointing tothe outside,
it's just the mere fact of having more than one active unteamed NIC, IP
address and/or RRAS installed that makes a machine multihomed. As long
as the additional NICs are not active in an unteamed configuration,
then it won't be multihomed.
As for your ipconfigs, thank you for posting them. Can you elaborate on
the 167.213.174.20 and other 167.x.x.x IP addresses? They appear to be
external, public IPs. If so, how are these DCs connected to the
external IPs? IS there a NAT between them?
The ipconfigs look relatively ok, other than the public IPs, which I
assume are DCs on the public DMZ or such, which I am not sure how you
have that configured to communicate assuming tehre is a NAT between
them (NAT cannot translate RPC, LDAP or Kerberos communications),
unless there's a VPN between them.
I assume the zone name in DNS is "omi.com."
I am curious why the additional Search Suffixes, such as:
omi.com
adroot.net
om-inc.com
omi
om-inc
Are they additional DNS zones that exist inside the infrasrtucture?
What worries me is that although they have nothing to do with Dynamic
DNS registration, they will affect DNS hostname resolution when the
client side resolver tries to devolve a single name when prefixing the
single name with the suffix because two of the names, "omi" and
"Om-inc," are single label names. The client side resolver in Windows
2000 and SP4 and all newer operating systems have difficulty resolving
single label names. The resolver service will treat "omi" and the other
one as a TLD, which will force it to search the Root DNS servers before
it looks at it's own DNS servers, as the way it treats trying to
resolve "com" "edu" etc.
And no errors are evident in any of the event logs (app, DNS, NTFRS,
system, etc), which is interesting and makes it harder to diagnose,
unless I am missing something basic.
Just an FYI, registration will work if the following are configured:
1. Primary DNS matches the zone name in DNS.
2. Zone properties in DNS allows updates.
3. The AD DNS domain name matches the Primary DNS Suffix and the zone
name in DNS.
4. The DHCP Client (not server) service is started.
5. The DNS addresses are set to DNS servers that host the zone name (in
your case, "omi.com." If the 167.x.x.x addresses do not host the zone,
it can cause issues.
.. No firewall (either Windows or in the infrastructure) is blocking
traffic.
I hope that helps.
Ace
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.
Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE
& MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
If you feel this is an urgent issue and require immediate assistance,
please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Similar Threads
Linear Mode
