Need help configuring AD DNS on DC

  • Thread starter Thread starter Jeff Fink
  • Start date Start date
J

Jeff Fink

Recently upgraded our PDC from NT4 to Win2K. Actually did this by
installing a fresh BDC, promoting, upgrading to Win2K. The DNS server
entries didn't get populated at all during the process. Now I'm trying to
add machines to the domain and am getting the standard error dialog telling
me to go to http://go.microsoft.com/fwlink/?LinkId=5171 . Have gone through
the article and fixed the problems there. But it still doesn't work.

I need some kind of a template showing me what default DNS entries should be
in ActiveDS for a PDC. I have the SOA and NS record for the domain and the
appropriate A record for the DC. I had to manually create the _sites, _tcp,
and _udp subdomains, and don't know what SRV records I need in each. I have
added the _ldap SRV record since I can see the DNS queries for it in Netmon.
Anyone have any ideas here?

Thanks,
-Jeff
 
In
Jeff Fink said:
Recently upgraded our PDC from NT4 to Win2K. Actually did this by
installing a fresh BDC, promoting, upgrading to Win2K. The DNS server
entries didn't get populated at all during the process. Now I'm
trying to add machines to the domain and am getting the standard
error dialog telling me to go to
http://go.microsoft.com/fwlink/?LinkId=5171 . Have gone through the
article and fixed the problems there. But it still doesn't work.

I need some kind of a template showing me what default DNS entries
should be in ActiveDS for a PDC. I have the SOA and NS record for
the domain and the appropriate A record for the DC. I had to
manually create the _sites, _tcp, and _udp subdomains, and don't know
what SRV records I need in each. I have added the _ldap SRV record
since I can see the DNS queries for it in Netmon. Anyone have any
ideas here?

Thanks,
-Jeff
Click to expand...

You should not have to create the subfolders, If the DC is pointing to its
own address for DNS and the forward lookup zone matches the domain name
these folders are created.

You may have other problems such as a disjointed namespace, which can happen
on NT4 upgrades if the Domain suffix in TCP/IP properties does not match the
Win2k domain name.

If you will post an ipconfig /all AND the Win2k domain name from Active
Directory Users and Computers we can help you resolve this.
 
Kevin D. Goodknecht said:
If you will post an ipconfig /all AND the Win2k domain name from Active
Directory Users and Computers we can help you resolve this.
Click to expand...

C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : bdc
Primary DNS Suffix . . . . . . . : dev.1cis.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dev.1cis.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : dev.1cis.com
Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet
Adapter
Physical Address. . . . . . . . . : 00-06-29-05-90-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.79
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.1.1.1
DNS Servers . . . . . . . . . . . : 10.0.0.79


Win2k domain name from Active Directory Users and Computers is dev.1cis.com.
Don't let the name fool you, it's the only domain controller on the domain
right now.
 
In
Jeff Fink said:
C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : bdc
Primary DNS Suffix . . . . . . . : dev.1cis.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dev.1cis.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : dev.1cis.com
Description . . . . . . . . . . . : AMD PCNET Family PCI
Ethernet Adapter
Physical Address. . . . . . . . . : 00-06-29-05-90-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.79
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.1.1.1
DNS Servers . . . . . . . . . . . : 10.0.0.79


Win2k domain name from Active Directory Users and Computers is
dev.1cis.com. Don't let the name fool you, it's the only domain
controller on the domain right now.
Click to expand...

That actually looks good.


Did you create a zone called dev.1cis.com in your DNS server and did you
enable dynamic updates on the dev.1cis.com zonename's properties in DNS?

If you have, then perform these steps:

Delete the netlogon.dns and netlogon.dnb files from the system32\config
folder.
Goto a cmd prompt, type in:
ipconfig /registerdns
net stop netlogon
net start netlogon

Then all the SRV records will automatically populate under the dev.1cis.com
zone name.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
"Ace Fekay [MVP]"
Did you create a zone called dev.1cis.com in your DNS server and did you
enable dynamic updates on the dev.1cis.com zonename's properties in DNS?
Yes.

Delete the netlogon.dns and netlogon.dnb files from the system32\config
folder.
Goto a cmd prompt, type in:
ipconfig /registerdns
net stop netlogon
net start netlogon

Then all the SRV records will automatically populate under the dev.1cis.com
zone name.
Click to expand...

Ok, I can see all the SRV records now. Here's something strange. If I go
to add machines using domain "DEV" (the NT domain name) I can get it to work
(could before these changes also). If I use dev.1cis.com, it still does not
work.

-Jeff
 
In
Jeff Fink said:
"Ace Fekay [MVP]"


Ok, I can see all the SRV records now. Here's something strange. If
I go to add machines using domain "DEV" (the NT domain name) I can
get it to work (could before these changes also). If I use
dev.1cis.com, it still does not work.

-Jeff
Click to expand...

Glad the SRVs showed up.

It should also work using the FQDN. Is the client machine ONLY pointing to
10.0.0.79? Need to remove the ISP's if it's in there. If it is, and the SRVs
finally showed up, maybe the client still has the old info cached. You try
to cancel the join, do an ipconfig /flushdns to flush the client's cache,
then try again and it should work.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
"Ace Fekay [MVP]"
It should also work using the FQDN. Is the client machine ONLY pointing to
10.0.0.79? Need to remove the ISP's if it's in there. If it is, and the SRVs
finally showed up, maybe the client still has the old info cached. You try
to cancel the join, do an ipconfig /flushdns to flush the client's cache,
then try again and it should work.
Click to expand...

Must have been the cache. Everything seems to be working now. Thanks for
the help.
-Jeff
 
In
Jeff Fink said:
"Ace Fekay [MVP]"


Must have been the cache. Everything seems to be working now.
Thanks for the help.
-Jeff
Click to expand...

Sounds good!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top