General discussion

Locked

DNS ain't right after PDC upgrade

By syoung640 ·
I recently upgraded my PDC from NT4.0 to Win2k, and installed DNS via the wizard, etc., but the DNS I've got isn't right. I don't have any of the _ldap or other SRV records, and when I run the diag. tool DCDIAG.EXE it reports communication errors.
On the other hand, the new Win2k machine is replicating fine with the old NT4 BDCs. Can I just delete my DNS setup and re-do it? Suggestions are welcomed.

--Steve

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

DNS ain't right after PDC upgrade

by frujim In reply to DNS ain't right after PDC ...

Yes, you can reinstall DNS without hurting anything.

You may want to ensure that the server is set to use itself for primary and secondary DNS.

You can also check to see if any workstation records(A records and PTR records) are being registered. If so you know that DNS is working properly and that there is probably a problem with the way the DC is setup to register it's records.

Collapse -

DNS ain't right after PDC upgrade

by syoung640 In reply to DNS ain't right after PDC ...

Thanks for the reply. I found msKB#294328 about how to re-install, tried it, but it's still not creating the SRV records like it's supposed to, nor is it registering A or PTR records (DHCP is on another server-ok? dhcp client is running per the kb article tho server has a static ip). Should I try setting up DNS while off the network? I'll keep futzing with it.

Collapse -

DNS ain't right after PDC upgrade

by gregross In reply to DNS ain't right after PDC ...

you need to point your DC to itself for DNS
it will force you to reboot
should be all set after that

Collapse -

DNS ain't right after PDC upgrade

by syoung640 In reply to DNS ain't right after PDC ...

Thanks. Here's the REST of the story: I unplugged the server from the net and re-installed DNS, and it worked as advertised (except it thought it was the root of the world, and created a "." forwarding domain, which I deleted). The server running Act.Dir. was pointing _only_ to itself, but I had another Win2k server (without AD) running a public DNS domain that was above the AD domain I wanted to set up. I.e.,
A-D domain: TB.BG.COM
Existing (public) domain on stand-alone: BG.COM
I guess theinstaller was getting confused when it saw BG.COM as an existing SOA, and wouldn't set up any .SRV records. (why?).

Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums