DNS records where not created
Mikael Schvili
After promoting av Windows 2000 Server to DC no AD-records where created in
DNS. Only classic host-records were created. Also, the DNS-service doesn't
respond to NSLOOKUP.
I ran dcdiag /test:dns and ended up with the result below. Last in this post
is an extract of the error-log.
Any suggestions on what might be causing this problem and how to fix it
would be deeply appreciated.
BR,
Mikael Schvili MCSE
resursit
**** START OF RESULT OF DCDIAG ****
C:\Documents and Settings\Administrator.LADC01>dcdiag /test:dns
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\mydc
Starting test: Connectivity
LAKRSRV3'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
(ede64421-5095-475f-9540-91ccedf76483._msdcs.mycompany.local)
couldn't be
resolved, the server name (mydc.mycompany.local) resolved to the IP
address (10.224.216.226) and was pingable. Check that the IP address
is registered correctly with the DNS server.
......................... LAKRSRV3 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\LAKRSRV3
Running enterprise tests on : mycompany.local
C:\Documents and Settings\Administrator.LADC01>
**** END OF RESULT OF DCDIAG ****
**** START OF LOG ENTRY ****
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 2005-12-01
Time: 16:36:20
User: N/A
Computer: LAKRSRV3
Description:
Registration of the DNS record
'ede64421-5095-475f-9540-91ccedf76483._msdcs.bila.local. 600 IN CNAME
lakrsrv3.bila.local.' failed with the following error:
DNS RR set that ought to exist, does not exist.
Data:
0000: 30 23 00 00 0#..
**** END OF LOG ENTRY ****
Kevin D. Goodknecht Sr. [MVP]
Make sure the DC has only the IP of the DNS that hosts the AD domain zone,
no ISP or external DNS that does not support the AD domain.
Usually the DC hosts the zone for the AD domain, so your DC would have its
own IP address for DNS.
--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
Mikael Schvili
Thanks for your reply. The server has its own IP specified as the DNS-server
in TCP/IP settings. Also note that the server doesn't respond to nslookup,
even when I run it locally. Nslookup just tells me that it can't find any
DNS-server at the IP-adress specified.
(The DNS server service is started and I can connect to it normally through
the MMC console.)
One thought that just crossed my mind is that the server has two NICs,
though only one is in use. Could it be that the DNS service is bound to the
other NIC only, although it's diasabled. If so, where can the bindings be
manually changed to the NIC that's being used?
BR
Mikael
Kevin D. Goodknecht Sr. [MVP]
> Hi Kevin,
>
> Thanks for your reply. The server has its own IP specified as the
> DNS-server in TCP/IP settings. Also note that the server doesn't
> respond to nslookup, even when I run it locally. Nslookup just tells
> me that it can't find any DNS-server at the IP-adress specified.
>
> (The DNS server service is started and I can connect to it normally
> through the MMC console.)
>
> One thought that just crossed my mind is that the server has two NICs,
> though only one is in use. Could it be that the DNS service is bound
> to the other NIC only, although it's diasabled. If so, where can the
> bindings be manually changed to the NIC that's being used?
In the DNS management console, right click on the DNS server name and select
properties, check the interfaces tab and DNS should be listening ONLY on the
IP of the enabled interface.
Also, if the nslookup message says "Can't find server name for address
<IPAddressofDNSServer>", this is not really an error and does not mean that
DNS is not working. It simply means that nslookup cannot find a PTR record
for the IP of the DNS server. (Even though you did not tell nslookup to
perform the PTR lookup)
If you will create a reverse lookup zone and PTR record the message will go
away.