AD DNS records? Never seen them :(

  • Thread starter Thread starter Bram
  • Start date Start date
B

Bram

Hi,

I'm trying to build a little NT network myself here, at home, and I have
a problem (uh-oh). My Primary DNS server is set to 127.0.0.1, but when I
restart the Net Logon service, the records aren't replicated. Instead, I
get these three Warnings in the System Event Log...

Numbers 2 and 3 are the same as 1, only with a different description.


--- NUMBER ONE ---
Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5781
Date: 14/07/2003
Time: 11:01:36
User: N/A
Computer: VOYAGER
Description:
Dynamic registration or deletion of one or more DNS records associated
with DNS domain 'home.' failed. These records are used by other
computers to locate this server as a domain controller (if the specified
domain is an Active Directory domain) or as an LDAP server (if the
specified domain is an application partition).

Possible causes of failure include:
- TCP/IP properties of the network connections of this computer contain
wrong IP address(es) of the preferred and alternate DNS servers
- Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registered is not running
- Preferred or alternate DNS servers are configured with wrong root hints
- Parent DNS zone contains incorrect delegation to the child zone
authoritative for the DNS records that failed registration

USER ACTION
Fix possible misconfiguration(s) specified above and initiate
registration or deletion of the DNS records by running 'nltest.exe
/dsregdns' from the command prompt or by restarting Net Logon service.
Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..


--- NUMBER TWO ---
Description:
Dynamic registration or deletion of one or more DNS records associated
with DNS domain 'DomainDnsZones.home.' failed. These records are used by
other computers to locate this server as a domain controller (if the
specified domain is an Active Directory domain) or as an LDAP server (if
the specified domain is an application partition).


--- NUMBER THREE ---
Description:
Dynamic registration or deletion of one or more DNS records associated
with DNS domain 'ForestDnsZones.home.' failed. These records are used by
other computers to locate this server as a domain controller (if the
specified domain is an Active Directory domain) or as an LDAP server (if
the specified domain is an application partition).


In addition, I've found these errors in my DNS Event Log...


--- NUMBER ONE ---
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date: 13/07/2003
Time: 22:44:20
User: N/A
Computer: VOYAGER
Description:
The DNS server has encountered a critical error from the Active
Directory. Check that the Active Directory is functioning properly. The
extended error debug information (which may be empty) is "". The event
data contains the error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 51 00 00 00 Q...


--- NUMBER TWO ---
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4004
Date: 13/07/2003
Time: 22:44:20
User: N/A
Computer: VOYAGER
Description:
The DNS server was unable to complete directory service enumeration of
zone 0.0.10.in-addr.arpa. This DNS server is configured to use
information obtained from Active Directory for this zone and is unable to
load the zone without it. Check that the Active Directory is functioning
properly and repeat enumeration of the zone. The extended error debug
information (which may be empty) is "". The event data contains the
error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..


--- NUMBER THREE ---
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4004
Date: 13/07/2003
Time: 22:44:20
User: N/A
Computer: VOYAGER
Description:
The DNS server was unable to complete directory service enumeration of
zone home. This DNS server is configured to use information obtained
from Active Directory for this zone and is unable to load the zone
without it. Check that the Active Directory is functioning properly and
repeat enumeration of the zone. The extended error debug information
(which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..


When I look in my DNS, there aren't any records for the AD, which can't
be good. There must be a way to fix it, without reinstalling Win2K3
Server -- I just installed W2K3 and upgraded it at once to a domain
controller, so there can't be much bad settings. dcpromo complained about
a faulty DNS, but I chose to let dcpromo fix it. That's the last thing I
heard about it, but it didn't seem to work very good.

What am I missing here? What am I doing wrong? And, very important... How
do I fix it? :)

Thank you!
Bram

PS: W2K3 isn't that different from W2K when it comes to installing AD. Is
it?
 
Let me clarify this a bit :)

What I mean to say was: there aren't any AD records in the DNS server,
resulting in the problem that Net Logon comlains too.

The complaints are in the original posting.
 
My Primary DNS server is set to 127.0.0.1, but

Don't use that IP address. Use the actual IP address.

hth
DDS W 2k MVP MCSE
 
Don't use that IP address. Use the actual IP address.
Click to expand...

Changed that, but that didn't bring my records back and Net Logon keeps
complaining.

What do I do now?

Thanks,
Bram
 
post the ipconfig /all output from the ser and let's take a lookie.

Also post your DNS config information (Listening on which NIC, what zones do
you have, which records do you have in the zone). also, if you try simple
and recursive query test from the DNS console, what are the results?

Someone here will be able to better help you with those information
provided.

HTH
Deji
 
Have you enable Dynamic updates on your zones in your AD ? You can manualy
recreate DNS records (not a normal procedure). What DNS records should be
there is written in %systemroot%\system32\config\netlogon.dns file on your
DC.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), MVP
(e-mail address removed)
http://ladava.com
 
post the ipconfig /all output from the ser and let's take a lookie.

Also post your DNS config information (Listening on which NIC, what
zones do you have, which records do you have in the zone). also, if
you try simple and recursive query test from the DNS console, what are
the results?

Someone here will be able to better help you with those information
provided.

HTH
Deji
Click to expand...

--- ipconfig /all ---
Windows IP Configuration

Host Name . . . . . . . . . . . . : voyager
Primary Dns Suffix . . . . . . . : home
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Xircom CardBus Ethernet 100 +
Modem 56 (Ethernet Interface)
Physical Address. . . . . . . . . : 00-10-A4-FC-C0-53
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.11
DNS Servers . . . . . . . . . . . : 10.0.0.5


--- DNS config (all on the Xircom NIC) ---
** Forward Lookup Zones
home
- SOA, Primary server: voyager.home.
- NS: voyager.home.
- A: voyager --> 10.0.0.5

** Reverse Lookup Zones
10.0.0.x Subnet
- SOA, Primary server: voyager.home.
- NS: voyager.home.
- PTR: 10.0.0.5 --> voyager

** Simple Query Test: Pass
** Recursive Query Test: Pass


--- Domain Controller Diagnosis ---
Testing server: Home\VOYAGER
Starting test: Connectivity
The host 51a1733a-8585-4ce9-89a2-11d857aa95c8._msdcs.home could
not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(51a1733a-8585-4ce9-89a2-11d857aa95c8._msdcs.home) couldn't be
resolved, the server name (voyager.home) resolved to the IP
address (10.0.0.5) and was pingable. Check that the IP address
is registered correctly with the DNS server.
......................... VOYAGER failed test Connectivity

--- NL Test ---
nltest /dsregdns
Click to expand...

Flags: 0
Connection Status = 0 0x0 NERR_Success
The command completed successfully

Still no zones :/


Thanks,
Bram
 
You are using a single labeled domain name. There are issues in doing
that (it has to do with host registrations). Please read
http://support.microsoft.com/?id=300684
Click to expand...

So, if I get it right, I need to do the following:

1. Remove the AD
2. Recreate the AD using "home.network" or similar (I don't want to use an
official TLD as I don't want to interfere with an existing and registered
domain name)

Bram
 
rather use home.local, but basicaly if you don't mind recreating AD and all
the objects, then yes, reinstall AD.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), MVP
(e-mail address removed)
http://ladava.com
 
rather use home.local, but basicaly if you don't mind recreating AD
and all the objects, then yes, reinstall AD.
Click to expand...

It worked! Thanks! :)

Just for the record (because I'm curious): was there a way of renaming the
AD without reinstalling it?

Bram
 
Nup. This is possible only in WS2k3 domains with some limitations ;-)
Click to expand...

Wieh, I'm running WS2k3 Enterprise Edition! Maybe I should read the "FM"
(derived from "RTFM")? :)

Thanks,
Bram
 
Back
Top