Registration of the DNS record _ldap._tcp.pdc._msdcs Failed

D

Del

I upgraded an NT40 PDC server to W2K this past weekend.
The NT server had mypublicdomain.com as it's internal dns
name when I started the upgrade. After the upgrade was
finished I went to configure DNS in W2K and noticed the NS
and SOA records had the external domain instead of the
internal domain name. I went through and verified the
server was looking at itself for DNS resolution and it
was. In DNS mmc I verified the server was listening on the
correct internal IP and the correct forwarders where
setup. On the zone in the SOA record I manually changed
the Primary server entry from servername.outsidedomain.com
to servername.insidedomain.com and I had to change the ip
address of the name server from what the ISP has has our
outside domain name to the internal dns server. After I
refresh the record the outside ip reappears. I am also
getting:
Registration of the DNS record '_kpasswd._tcp
Registration of the DNS record '_ldap._tcp.pdc._msdcs
failed with the following error: DNS server unable to
interpret format.
errors in the event log and none of the normal AD entries
are appearing in the DNS mmc.
Even though I allow dynamic updates none of the
workstations or other 2k servers are appearing in DNS. I
can't seem to figure this one out. No where on any of the
netowrking tabs does it point to anyting on the outside
world. Only on the forward tab in DNS does there appear an
outside IP.
What am I missing that is not allowing the AD folders and
the other w2k worksations and servers to register with
DNS. DNS is forwarding everyones web and email request so
they can surf and send email.
 
K

Kevin D. Goodknecht [MVP]

In
Del said:
I upgraded an NT40 PDC server to W2K this past weekend.
The NT server had mypublicdomain.com as it's internal dns
name when I started the upgrade. After the upgrade was
finished I went to configure DNS in W2K and noticed the NS
and SOA records had the external domain instead of the
internal domain name. I went through and verified the
server was looking at itself for DNS resolution and it
was. In DNS mmc I verified the server was listening on the
correct internal IP and the correct forwarders where
setup. On the zone in the SOA record I manually changed
the Primary server entry from servername.outsidedomain.com
to servername.insidedomain.com and I had to change the ip
address of the name server from what the ISP has has our
outside domain name to the internal dns server. After I
refresh the record the outside ip reappears. I am also
getting:
Registration of the DNS record '_kpasswd._tcp
Registration of the DNS record '_ldap._tcp.pdc._msdcs
failed with the following error: DNS server unable to
interpret format.
errors in the event log and none of the normal AD entries
are appearing in the DNS mmc.
Even though I allow dynamic updates none of the
workstations or other 2k servers are appearing in DNS. I
can't seem to figure this one out. No where on any of the
netowrking tabs does it point to anyting on the outside
world. Only on the forward tab in DNS does there appear an
outside IP.
What am I missing that is not allowing the AD folders and
the other w2k worksations and servers to register with
DNS. DNS is forwarding everyones web and email request so
they can surf and send email.

This could be a disjointed name space, post an ipconfig /all with the domain
name from AD Users & Computers.
-or-
Follow this article:
257623 Domain Controller's Domain Name System Suffix Does Not Match Domain
Name
http://support.microsoft.com/?id=257623
 
G

Guest

This appears to be the issue I am experiancing!
THe AD domain name is pace.com
The ipconfig /all reports
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : ntsvr
Primary DNS Suffix . . . . . . . : paceairfreight.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : paceairfreight.com

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : IBM Netfinity Fault
Tolerance PCI Adapter
Physical Address. . . . . . . . . : 00-06-29-39-DD-B4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.200
DNS Servers . . . . . . . . . . . : 192.168.1.100
192.168.1.1
 
K

Kevin D. Goodknecht [MVP]

In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
This appears to be the issue I am experiancing!
THe AD domain name is pace.com
The ipconfig /all reports
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : ntsvr
Primary DNS Suffix . . . . . . . : paceairfreight.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : paceairfreight.com

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : IBM Netfinity Fault
Tolerance PCI Adapter
Physical Address. . . . . . . . . : 00-06-29-39-DD-B4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.200
DNS Servers . . . . . . . . . . . : 192.168.1.100
192.168.1.1

The article I posted will fix this, create the script form the template on
the page.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top