[LONG - PLS HELP] Issues on DNS

I recently rebooted my PDC (w2k3 r2) and noticed that during startup
remains 5, 6 minutes on logon box saying "Waiting network
connections" ...

I opened event viewer and found the following:

1) Directory Service

Source: NTDS Replication
Category: DS RPC Client
Type: warning
User: NT AUTHORITY\ANONYMOUS LOGON
Event ID: 2088

Active Directory could not use DNS to resolve the IP address of the
source domain controller listed below. To maintain the consistency of
Security groups, group policy, users and computers and their
passwords, Active Directory successfully replicated using the NetBIOS
or fully qualified computer name of the source domain controller.

2) DNS Server:

Source: DNS
Category: none
Type: error
User: N/A
Event ID: 4007

The DNS server was unable to open zone mydomain.local in the Active
Directory from the application directory partition
DomainDnsZones.mydomain.local. This DNS server is configured to obtain
and use information from the directory for this zone and is unable to
load the zone without it. Check that the Active Directory is
functioning properly and reload the zone. The event data is the error
code.

Source: DNS
Category: none
Type: error
User: N/A
Event ID: 4007

The DNS server was unable to open zone _msdcs.mydomain.local in the
Active Directory from the application directory partition
ForestDnsZones.mydomain.local. This DNS server is configured to obtain
and use information from the directory for this zone and is unable to
load the zone without it. Check that the Active Directory is
functioning properly and reload the zone. The event data is the error
code.

3 System:

Dynamic registration or deletion of one or more DNS records associated
with DNS domain 'mydomain-ring.local.' 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.


My environment is:

1 PDC w2k3 r2
1 DC w2k3 r2 (for high availability)
1 sql server w2k3 x64 r2
1 application server (IIS) w2k3 r2
n xp/vista clients


I looked at DNS service on PDC and noticed that in:

DC
-- Forward Lookup Zones
------ mydomain-ring.local
------------ _msdcs

properties

IP Address of mydomain-dc01.mydomain.local. missed in Name Servers
tab, so I added it. Then I restarted machine bu it didn't resolve
problem.

I can see 2 new eventS now:

Source: NTDS KCC
Category: knowledge consistency
Type: Information
User: NT AUTHORITY\ANONYMOUS LOGON
Event ID: 1404

The local domain controller is now the intersite topology generator
and has assumed responsibility for generating and maintaining
intersite replication topologies for this site.


Source: NTDS KCC
Category: knowledge consistency
Type: Information
User: NT AUTHORITY\ANONYMOUS LOGON
Event ID: 1308


The Knowledge Consistency Checker (KCC) has detected that successive
attempts to replicate with the following domain controller has
consistently failed.

Attempts:
2
Domain controller:
CN=NTDS
Settings,CN=DC02,CN=Servers,CN=mylocation,CN=Sites,CN=Configuration,DC=mydomain-
ring,DC=local
Period of time (minutes):
135

The Connection object for this domain controller will be ignored, and
a new temporary connection will be established to ensure that
replication continues. Once replication with this domain controller
resumes, the temporary connection will be removed.


Any help MUCH appreciated.

Best regards and thanks fo reading.
.

Relevant Pages

  • RPC Endpoint Mapper Error
    ... We are adding our first Windows 2003 Domain Controller to a Windows ... I checked DNS entries with articles from Microsoft on ... PASS - All the DNS entries for DC are registered on DNS server ... List of NetBt transports currently bound to the Redir ...
    (microsoft.public.win2000.active_directory)
  • Re: DHCP Clients getting DNS lookup failures
    ... It sounds to me like you had a DNS issue but you fixed it, ... The DNS server has encountered a critical error from the Active ... Check that the Active Directory is functioning properly. ... Active Directory for this zone and is unable to load the zone without ...
    (microsoft.public.windows.server.sbs)
  • Re: Global Catalog %%5?
    ... Active Directory could not resolve the following DNS host name of the source ... domain controller to an IP address. ... server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE ...
    (microsoft.public.windows.server.active_directory)
  • Re: Global Catalog %%5?
    ... Active Directory could not resolve the following DNS host name of the source ... domain controller to an IP address. ... server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE ...
    (microsoft.public.windows.server.active_directory)
  • Re: the system cannot log you on now because the domain <domain>is not available
    ... What I would suggest trying, at least temporarily, is to open Domain Controller ... The other main concern is that dns is configured correctly for the whole domain. ... controllers running dns with the AD domain zone and NEVER an ISP dns server anywhere ... > event log showed teh failed attempts at locating the DC. ...
    (microsoft.public.windows.server.networking)