In
CST said:
Well on my DC1 I have two NICS. One for the WAN (Public
Internet) and one for my LAN. The WAN side is using
DHCP. I have a static IP assigned to my LAN and the DNS
is pointing to my IP Address on DC1. I can add my DC2 to
the network, I can ping DC1 by IP Address and by name. I
just cant promote it to another domain controller on my
network. On my DNS it seems to be set up correctly. I
have my zone set to "yes" for dynamic updates.
Do you still think it's some kind of misconfiguration on
my DNS based on the information I have provided above? If
so where should I begin or what should I look for in my
DNS to see how\where it is misconfigured.
Ooo, multihomed DC with one NIC using DHCP, ouch.
On the DHCP NIC Manually enter the IP of the private NIC for DNS.
Add the PublishAddresses and RegisterDnsARecords registry values for the DNS
and Netlogon services
1.. Click Start, click Run, type regedit, and then click OK.
2.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
3.. On the Edit menu, point to New, and then click String Value to add the
following registry value:
Value name: PublishAddresses
Data type: REG_SZ
Value data: IP address of the server's local network adapter. If you have
to specify more than one IP address, separate the addresses with spaces.
4.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
5.. On the Edit menu, point to New, and then click DWORD Value to add the
following registry value:
Value name: RegisterDnsARecords
Data type: REG_DWORD
Value data: 0
6..
7.. Add the A Records in DNS
8.. Complete these steps only if the Routing and Remote Access server is a
domain controller.
1.. Click Start, point to Programs or All Programs, point to
Administrative Tools, and then click DNS.
2.. In the DNS console, expand the server object, expand the Forward
Lookup Zones folder, and then click the folder for the local domain.
3.. On the Action menu, click New Host.
4.. In the IP address text box, type the IP address of the server's
local network adapter.
5.. Leave the Name box empty, click Create Associated PTR Record, and
then click Add Host.
6.. When you receive the "(same as parent folder) is not a valid host
name. Are you sure you want to add this record?" message, click Yes.
Note If the server is a global catalog server, go to step 7. If the
server is not a global catalog server, you do not have to complete steps 7
through 11. To determine if the server is a global catalog server, follow
these steps:
1.. Click Start, point to Programs or All Programs, point to
Administrative Tools, and then click Active Directory Sites and Services.
2.. In the Active Directory Sites and Services console, expand the
Sites folder, expand the site that contains the server, and then expand the
server object.
3.. Right-click NTDS Settings, and then click Properties.
4.. On the General tab, locate the Global Catalog check box. If this
check box is checked, the server is a global catalog server.
7.. Under the Forward Lookup Zones folder in the DNS console, expand the
folder for the local domain, expand the MSDCS folder, and then click the GC
folder.
8.. On the Action menu, click New Host.
9.. In the IP address box, type the IP address of the server's local
network adapter.
10.. Leave the Name box empty, click Create Associated PTR Record, and
then click Add Host.
11.. When you receive the "(same as parent folder) is not a valid host
name. Are you sure you want to add this record?" message, click Yes.
Run netdiag /fix
Then try DCPROMO again.
