DC has no DNS Name

  • Thread starter Thread starter Gary
  • Start date Start date
G

Gary

I get a 414 error in the DNS Event Log on my only Domain
Controller that states:

"DNS name is a single label hostname with no domain
(example: "host" rather than "host.microsoft.com").

You might have forgotten to configure a primary DNS domain
for the server computer. For more information, see
either "DNS server log reference" or "To configure the
primary DNS suffix for a client computer" in the online
Help."

Obviously on a domain controller I cannot go into the
Network Properties under system and reset those. I have
also run the script from Knowledge Base Article - 257623
and that did not seem to work (the proper settings seem to
be set in the registry)

I am having several strange problems such as Exchange
won't start because it says it cannot contact my domain
controller, I get errors when I run DCDIAG:

"SERVER's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name (7942fd1f-bf54-4105-a1d5-
45f6824bfbab._msdcs.domain.com) couldn't be resolved, the
server name (SERVER) resolved to the IP address
(xx.xx.xx.xx) and was pingable. Check that the IP address
is registered correctly with the DNS server."

and when I run NETDIAG it says there is no host name.

Does anyone know how to "reset" the host name and/or
primary dns name for a domain controller?
 
In
Gary said:
I get a 414 error in the DNS Event Log on my only Domain
Controller that states:

"DNS name is a single label hostname with no domain
(example: "host" rather than "host.microsoft.com").

You might have forgotten to configure a primary DNS domain
for the server computer. For more information, see
either "DNS server log reference" or "To configure the
primary DNS suffix for a client computer" in the online
Help."

Obviously on a domain controller I cannot go into the
Network Properties under system and reset those. I have
also run the script from Knowledge Base Article - 257623
and that did not seem to work (the proper settings seem to
be set in the registry)

I am having several strange problems such as Exchange
won't start because it says it cannot contact my domain
controller, I get errors when I run DCDIAG:

"SERVER's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name (7942fd1f-bf54-4105-a1d5-
45f6824bfbab._msdcs.domain.com) couldn't be resolved, the
server name (SERVER) resolved to the IP address
(xx.xx.xx.xx) and was pingable. Check that the IP address
is registered correctly with the DNS server."

and when I run NETDIAG it says there is no host name.

Does anyone know how to "reset" the host name and/or
primary dns name for a domain controller?
Click to expand...

Use the script in this KB to fix the Primary DNS suffix on your domain
controller, then run this from a CMD Prompt: netdiag /fix

257623 Domain Controller's Domain Name System Suffix Does Not Match Domain
Name
http://support.microsoft.com/?id=257623
 
Yes, I mentioned below that I actually tried that based on
one of your posted response a week or so ago. That didn't
seem to take care of the problem. I even ran it again
just to see if it would help. No luck.

Any other ideas?
 
In
Gary said:
Yes, I mentioned below that I actually tried that based on
one of your posted response a week or so ago. That didn't
seem to take care of the problem. I even ran it again
just to see if it would help. No luck.

Any other ideas?
Click to expand...

Not without you posting an unedited ipconfig /all, Domain name from ADUC and
your list of zones in DNS.
 
Here is the output. I also added the netdiag and dcdiag
results, thinking those might help. The domain name in
ADUC is signet-computers.com.
Thanks in advance.
_____________________________
IPCONFIG:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : CHEF
Primary DNS Suffix . . . . . . . : signet-
computers.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : signet-
computers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys
LNE100TX(v5) Fast Ethernet A
dapter
Physical Address. . . . . . . . . : 00-04-5A-4B-2B-
8A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 66.92.163.216
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 66.92.163.1
DNS Servers . . . . . . . . . . . : 66.92.163.216
66.92.163.218
_____________________________
NETDIAG
.......................................

Computer Name: CHEF
DNS Host Name: CHEF
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 5 Model 8 Stepping 12,
AuthenticAMD
List of installed hotfixes :
KB819696
KB823182
KB823559
KB823980
KB824105
KB824141
KB824146
KB825119
KB826232
KB828028
KB828035
KB828741
KB828749
KB835732
KB837001
KB839643
KB839645
KB840315
KB841872
KB841873
KB842526
Q147222
Q295688
Q816093

Netcard queries test . . . . . . . : Passed

Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . :
IP Address . . . . . . . . : 66.92.163.216
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 66.92.163.1
Dns Servers. . . . . . . . : 66.92.163.216
66.92.163.218


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation
Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this
interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{43E3537C-05D0-4577-B390-37B20EE23183}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the
<00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on
DNS server '66.92.163.21
6' and other DCs also have some of the names registered.
[WARNING] The DNS entries for this DC cannot be
verified right now on DNS
server 66.92.163.218, ERROR_TIMEOUT.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{43E3537C-05D0-4577-B390-37B20EE23183}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{43E3537C-05D0-4577-B390-37B20EE23183}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on
DC 'CHEF'.


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is
assigned.


The command completed successfully
_____________________________
DCDIAG
DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: DC-Site\CHEF
Starting test: Connectivity
CHEF's server GUID DNS name could not be resolved
to an
IP address. Check the DNS server, DHCP, server
name, etc
Although the Guid DNS name
(7942fd1f-bf54-4105-a1d5-
45f6824bfbab._msdcs.signet-computers.com)
couldn't be resolved, the server name (CHEF)
resolved to the IP
address (66.92.163.216) and was pingable. Check
that the IP address
is registered correctly with the DNS server.
......................... CHEF failed test
Connectivity

Doing primary tests

Testing server: DC-Site\CHEF
Skipping all tests, because server CHEF is
not responding to directory service requests

Running enterprise tests on : signet-computers.com
Starting test: Intersite
......................... signet-computers.com
passed test Intersite
Starting test: FsmoCheck
......................... signet-computers.com
passed test FsmoCheck
_____________________________
DNS Zones
Name Type Status
mdcarpetcare.com Standard Primary Running
motherboardmedia.com Standard Primary Running
sigcomp.com Secondary Running
signet-computers.com Standard Primary Running
slyrooster.com Standard Primary Running
_____________________________
DNS for Signet-computers.com:
Name Type Data
_msdcs
_sites
_tcp
_udp
(same as parent folder) Start of Authority [2453],
chef.signet-computers.com., info.signet-computers.com.
(same as parent folder) Name Server ns.signet-
computers.com.
(same as parent folder) Name Server chef.signet-
computers.com.
(same as parent folder) Name Server ns2.signet-
computers.com.
(same as parent folder) Name Server chef.
(same as parent folder) Host 66.92.163.218
(same as parent folder) Host 66.92.163.216
(same as parent folder) Mail Exchanger [10] mail.signet-
computers.com.
(same as parent folder) Mail Exchanger [20]
mail.sigcomp.com.
bwi Host 66.92.20.101
chef Host 66.92.163.216
ftp Host 66.92.20.101
gateway1 Host 192.168.1.101
mail Host 66.92.163.216
ns Host 66.92.163.216
ns2 Host 66.92.163.218
signet-4 Host 192.168.254.19
signet2 Host 192.168.1.100
signet218 Host 192.168.254.20
www Host 66.92.163.216
_____________________________
 
In
Gary said:
Here is the output. I also added the netdiag and dcdiag
results, thinking those might help. The domain name in
ADUC is signet-computers.com.
Thanks in advance.
_____________________________
IPCONFIG:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : CHEF
Primary DNS Suffix . . . . . . . : signet- computers.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : signet- computers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys
LNE100TX(v5) Fast Ethernet A
dapter
Physical Address. . . . . . . . . :
00-04-5A-4B-2B- 8A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 66.92.163.216
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 66.92.163.1
DNS Servers . . . . . . . . . . . : 66.92.163.216
66.92.163.218
Click to expand...

If this ipconfig /all is not edited it appears to me that when you ran the
script you put a space between the - and the c in signet-computers.com
That said, does the DNS at 66.92.163.218 have a copy of the AD zone?
 
Unfortunately the space in the domain name was due to the
cut and paste into the email. The ipconfig output has the
name correctly entered.

the 66.92.163.218 server does act as a secondary DNS
server and has a copy of the AD zone.

Any other thoughts?
 
In
Gary said:
Unfortunately the space in the domain name was due to the
cut and paste into the email. The ipconfig output has the
name correctly entered.

the 66.92.163.218 server does act as a secondary DNS
server and has a copy of the AD zone.
Click to expand...

From looking at your zone data, I suggest you re-install the AD zone to
clear the bad data. This DC has the correct records in the zone, but it also
still has the data from when it had no Primary DNS suffix.
Follow this KB exactly to clear the bad data from the zone, I think it will
clear this up. Do not miss a step!
294328 - How to Reinstall a Dynamic DNS Active Directory- Integrated Zone
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294328


signet-computers.com. IN ANY

ANSWER SECTION:
signet-computers.com. 600 IN A 66.92.163.216
signet-computers.com. 600 IN A 66.92.163.218
signet-computers.com. 3600 IN NS ns.signet-computers.com.
signet-computers.com. 3600 IN NS
chef.signet-computers.com.<--Correct
signet-computers.com. 3600 IN NS
ns2.signet-computers.com.<--Does not answer
signet-computers.com. 3600 IN NS
chef.<-----------------------------Incorrect
signet-computers.com. 3600 IN SOA chef.signet-computers.com.
info.signet-computers.com. 2453 900 600 86400 3600
signet-computers.com. 3600 IN MX 10
mail.signet-computers.com.
signet-computers.com. 3600 IN MX 20 mail.sigcomp.com.

ADDITIONAL SECTION:
ns.signet-computers.com. 3600 IN A 66.92.163.216
chef.signet-computers.com. 3600 IN A 66.92.163.216
ns2.signet-computers.com. 3600 IN A 66.92.163.218<--Does not
answer
mail.signet-computers.com. 3600 IN A 66.92.163.216
mail.sigcomp.com. 3600 IN A 66.92.163.216
 
I tried to reinstall the dynamic DNS AD Integrated Zone
and that did not work. The problem does not seem to be
that there are incorrect settings from some old
configuration that needs to be cleaned up. The problem is
that the Dyanamic DNS keeps jamming those incorrect
entries in there. The real question is why does Dyanamic
DNS feel that it has to regenerate those settings and
where is it getting that information from?

I appreciate your help, but I think I am going to have to
spring for the Microsoft Support. In most of the
Knowledge base articles they define this as a known
problem, yet I still have to pay to get it fixed.

Thanks - Again
 
In
Gary said:
I tried to reinstall the dynamic DNS AD Integrated Zone
and that did not work. The problem does not seem to be
that there are incorrect settings from some old
configuration that needs to be cleaned up. The problem is
that the Dyanamic DNS keeps jamming those incorrect
entries in there. The real question is why does Dyanamic
DNS feel that it has to regenerate those settings and
where is it getting that information from?

I appreciate your help, but I think I am going to have to
spring for the Microsoft Support. In most of the
Knowledge base articles they define this as a known
problem, yet I still have to pay to get it fixed.

Thanks - Again
Click to expand...


From what I'm reading into this thread having not seen your zone, it seems
that you have mutliple entries for the same computer account or it is
registering without a suffix? If that is the case, do all your machines have
a Primary DNS suffix configured?

I apologize if my assumptions are incorrect.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top