If this server hosts DNS, then you need to enter 127.0.0.1 in the DNS box - no other servers.
Main Topics
Browse All TopicsHi,
The following msg keeps poping up.
Registration of the DNS record '_kpasswd._udp.example.com
Pl. Note::: skpskpSOL00 is a non existing server name and example.com is a non existing domain.
The DNS server fails every time. Could anyone tell me how I can fix the above problem and bring the DNS server up?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
now when i run the dcdiag.exe i get the following errors..
Starting test: Connectivity
Example server GUID DNS name could not be resolved to am IP address. Check the NDS server, DHCP, server naem etc
Although the guid DNS name
<................name.com>
Doing Primary tests
Tetsing server: default-first-site-name\wa
skipping all test, because server example is not responding to directory service request
This behavior can occur if the DNS domain name for the computer does not match the Active Directory domain name -
Try running at a command prompt
netdiag /fix
Have a look at this:
http://support.microsoft.c
Let us know how you get on
Deb :))
Hi Wilkersons - It's a bit like groundhog day!
Have you setup DNS-server, General tabs on Forward and Reverse Lookup Zone (have you got a reverse look-up zone?)
to 'allow dynamic updates' ? What server ip's are listed in your preferred dns servers - your isp's shouldn't be on there at all? Have you still got the " . " zone in dns?
could you post an ipconfig /all result?
Is this the only dns server? Is this the pdc/emulator on the domain? What's happening to the clients - can they log on ok?
I know questions,questions but the best and fullest picture that you can post of your full network setup, the better now - we'll get there,
Deb :))
Hi Deb,
Thanks for all the help. I am new to DNS server thing hence all the problems :) But i am learning. So pl bear with me ;) Ok the way our system is set up is as follows.
We have outsourced our web services. We have a domain www.example.com. Now i am trying to add one server (domain cont. with DNS-- wadcsol00.example.com) under the domain www.example.com thro the internet. Our ISP has assigned us 2 static ip's. We r connected thro a cable/DSL router to the internet. Right now we have a Novel network in place and we will be migrating to W2K. So this is the present setup.
The clients can log on to the EXAMPLE domain. And this is the only DNS server on our network again I am not sure how the novel servers r configured. The server ip's listed are preferred dns srv 192.168.1.175, alternate dns srv the one that has assigned to us by the isp (U have stated that it should'nt be the case could u please explain). wadcsol00.example.com is the PDC.
The Zones under the DNS Wadcsol00 are cached lookups, forward lookup zones and reverse lookup zones. Under cached lookup i have a "." .com, .edu etc ..which is standard. Under Active Directory users and computers i see wadcsol00.example.com and I object (example.com)
when i ran the ipconfig /resisterdns the error ws that the re-registration of DNS failed
I ran the netdiag /fix and got the following
Computer Name: WADCSOL00
DNS Host Name: WADCSOL00.example.com
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : WADCSOL00
IP Address . . . . . . . . : 192.168.1.175
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Primary WINS Server. . . . : 192.168.1.175
Dns Servers. . . . . . . . : 192.168.1.175
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
No remote names have been found.
WINS service test. . . . . : Passed
DNS test . . . . . . . . . . . . . : Failed
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.2c77ccd6-f5fb-4
790dd4f.domains._msdcs.exa
.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Sit
example.com. re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry example.com. re-registeration on DNS
server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry example.com. re-registeration on DNS
server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.example.com. re-registerat
ion on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.example.com. re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.exam
-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.examp
registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.gc._msdcs.example.com. re-registeration on DNS server '192.168.1.175' faile
d.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry gc._msdcs.example.com. re-registerati
on on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry gc._msdcs.example.com. re-registerati
on on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry c606213d-b83b-4a95-ae77-4f
dcs.example.com. re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.e
re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-Fir
sites.dc._msdcs.example.co
ailed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.examp
registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.dc._msdcs.example.com. re-registeration on DNS server '192.168.1.175' faile
d.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.example.com
eration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-Fir
sites.example.com. re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _gc._tcp.example.com. re-registeratio
n on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._udp.example.com
eration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.example.com.
ration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kpasswd._udp.example.com.
ration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for th
is DC on DNS server '192.168.1.175'.
[FATAL] No DNS servers have the DNS records for this DC registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{E108BD89-F9AD
NetBT_Tcpip_{14C9B8E4-B3D8
The redir is bound to 2 NetBt transports.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{14C9B8E4-B3D8
NetBT_Tcpip_{E108BD89-F9AD
The browser is bound to 2 NetBt transports.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Passed
The command completed successfully
i hope this will help u help me :)
Ok - just so I understand this - you have your internet site yourdomain.com being hosted by an external company? What are you wanting to do with these static public ip's - presumably one will be for the router? Do you have a firewall then, software or hardware - What did your isp advise you to do, or who intially advised you on your setup and what did they suggest?
What's the name and model no. of the router?
I know, more questions, just trying to understand.
"Now i am trying to add one server (domain cont. with DNS-- wadcsol00.example.com) under the domain www.example.com thro the internet." - not sure exactly what you mean here -
"The server ip's listed are preferred dns srv 192.168.1.175, alternate dns srv the one that has assigned to us by the isp (U have stated that it should'nt be the case could u please explain)."
DNS servers mean - these are the addresses of the dns servers that are used to resolve ip names and addresses. So one must be your dns server - ie Dns Servers. . . . . .192.168.1.175
However if, as it sounds, you've entered your public ip address in there, then it won't work. All the public ip address is, is the ip address that your router presents to the world. It isn't a dns server so it won't work and no wonder you're having problems.
Take it out of the dns server config and see what happens. Please do this or we're going nowhere.
Now the dns server needs somewhere else to turn if it can't resolve an ip address itself, which is why we use forwarding.You should try configure a forwarder to your isp's dns server address (not your public ip), and you can't do that if you've got the "." zone listed in the forard lookup zone first.
Let me know how you get on.
Deb :))
Deb,
"The server ip's listed are preferred dns srv 192.168.1.175, alternate dns srv the one that has assigned to us by the isp (U have stated that it should'nt be the case could u please explain)."
alternate dns srv ....i ment the ISP's DNS server IP ....not the public static IP address.
in the forwarding i have the ISP's DNS server ip address.
Under Forward looup zone i have .....
wadcsol00.example.com
(same as parent folder)... SOA... [2], wadcsol00.example.com.,adm
(same as parent folder)... NS...wadcsol00.example.com
(same as parent folder)....A ....192.168.1.175
Ok - isp's dns address is meant for forwarding - so you've got that right. Your dns server needs to be the only one in the list of servers - because it's looking for an alternate dns server within your local network and their aren't any (if there are put them in). For anything your server can't resolve it uses the forwarder ie the isp's dns server. How are your clients being authenticated on the network - ie dhcp, static ip's?
Take the isp's server out of the alternate dns (doesn't need to be there - that's what your forwarder does). Are you running active directory? If so is the name of the domain the same? - active directory users and groups.
Also enable dynamic updates, stop and restart dns, and try the netdiag /fix again. Let's see what happens. May have to rebuild the zone.
Deb :)
I am running active directory ..the AD is as follows
Left Side:
Active Directory Users and Computers[WADCSOL00.exampl
+ example.com
Right Side:
example.com domain
ran netdiag /fix got these errors...
The command completed successfully
C:\Documents and Settings\Administrator>net
..........................
Computer Name: WADCSOL00
DNS Host Name: WADCSOL00.example.com
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
List of installed hotfixes :
KB820888
KB822831
KB823182
KB823559
KB824105
KB824141
KB824146
KB825119
KB826232
KB828028
KB828035
KB828749
KB829558
KB830352
KB832359
Q147222
Q828026
Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'Intel(R) PRO/1000 XT Network Connection' may not be
working.
Per interface results:
Adapter : Local Area Connection 2
Netcard queries test . . . : Failed
NetCard Status: DISCONNECTED
Some tests will be skipped on this interface.
Host Name. . . . . . . . . : WADCSOL00
Autoconfiguration IP Address : 169.254.55.207
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . :
Adapter : Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : WADCSOL00
IP Address . . . . . . . . : 192.168.1.175
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Primary WINS Server. . . . : 192.168.1.175
Dns Servers. . . . . . . . : 192.168.1.175
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
WINS service test. . . . . : Passed
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{E108BD89-F9AD
NetBT_Tcpip_{14C9B8E4-B3D8
2 NetBt transports currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Failed
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.2c77ccd6-f5fb-4
790dd4f.domains._msdcs.exa
.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Sit
example.com. re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry example.com. re-registeration on DNS
server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry example.com. re-registeration on DNS
server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.example.com. re-registerat
ion on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.example.com. re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.exam
-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.examp
registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.gc._msdcs.example.com. re-registeration on DNS server '192.168.1.175' faile
d.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry gc._msdcs.example.com. re-registerati
on on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry gc._msdcs.example.com. re-registerati
on on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry c606213d-b83b-4a95-ae77-4f
dcs.example.com. re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.e
re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-Fir
sites.dc._msdcs.example.co
ailed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.examp
registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.dc._msdcs.example.com. re-registeration on DNS server '192.168.1.175' faile
d.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.example.com
eration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-Fir
sites.example.com. re-registeration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _gc._tcp.example.com. re-registeratio
n on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kerberos._udp.example.com
eration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.example.com.
ration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Failed to fix: DC DNS entry _kpasswd._udp.example.com.
ration on DNS server '192.168.1.175' failed.
DNS Error code: DNS_ERROR_RCODE_REFUSED
[FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for th
is DC on DNS server '192.168.1.175'.
[FATAL] No DNS servers have the DNS records for this DC registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{E108BD89-F9AD
NetBT_Tcpip_{14C9B8E4-B3D8
The redir is bound to 2 NetBt transports.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{14C9B8E4-B3D8
NetBT_Tcpip_{E108BD89-F9AD
The browser is bound to 2 NetBt transports.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Passed
The command completed successfully
Ok, only thing to do is to re-create the zone. Delete the forward look-up zone in dns, highlight zone, delete it from the action menu.
Then right- clik the server object, click on new zone - New forward look-up zone. Create it as a standard primary first, and ensure that you type in the correct name for the zone listed in active directory. ie example.com.
Let's hope that this solves the problem!
Deb :)
Hi,
Not heard from you for a while - had hoped things would be sorted :(
If you want to use AD you need dns, but a lot depends on your network setup - but as you have said, it is the only dns server on your network, and if clients want to authenticate to this server, you need to run AD, then you have to have dns on it.
Given that there are no other dns servers on the network,
In dns Recreate the forard lookup zone, make it AD integrated and call it your domain name - ie example.com
Once created in the forward lookup zone , highlight the zone called example.com then click on the action menu in dns then properties and then the general tab. Check the allow dynamic updates, then click ok.
This really should work -
And I've just spotted this:
" Under Forward looup zone i have .....
wadcsol00.example.com
(same as parent folder)... SOA... [2], wadcsol00.example.com.,adm
(same as parent folder)... NS...wadcsol00.example.com
(same as parent folder)....A ....192.168.1.175 "
It looks like the zone is called wadcsol00.example.com, when it should be called just example.com - is it or have I got wrong end of stick?
The fully qualified domain name of your server is wadcsol00.example.com, but the zone itself is example.com, and needs to be called just example.com which must be the same as the name in AD users and computers. Try this next, make sure it can accept dynamic updates, points to itself - has a forwarder setup to your isp's dns then let me know how you get on.
Deb :))
Sure - just check your event logs on the server - if you're clear ie no error or warning logs in dns since the time you implemented the last set of changes changes then you're home and dry - Try stopping then starting the dns serverif this isn't the case to see what it now brings up - I'm keeping my fingers crossed that we can happily close this!
Deb :))
That's great Wilkerson - but please don't forget to close this question!
Make sure the clients can see the server - they need to have it listed as their dns server - At a client bring up a command prompt and type ipconfig /all - the dns server listed must be the same IP as your local dns server ie '192.168.1.175'
They shouldn't have the isp dns server listed as a secondary dns either - the forwarding takes care of that.
Good Luck
Deb :))
Business Accounts
Answer for Membership
by: Debsyl99Posted on 2004-03-10 at 10:03:53ID: 10563205
Have you specified your DNS server as the machine's own address in your TCP/IP properties?