DNS server is not configured

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

Gary

A 3 year old 2000 server with 2 network cards and is DC.


Now it appears the DNS server is not configured. The zone is here but the
dns MMC is telling me it is not configured yet.


Also I am getting the following errors:

Event ID: 1000
Windows cannot determine the user or computer name. Return value (1703).


Event ID: 1655
The attempt to communicate with global catalog
\\server-1.office.botekusa.com failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup failure.

The operation in progress might be unable to continue. The directory
service will use the locator to try find an available global catalog server
for the next operation that requires one.

The record data is the status code.

Event ID: 1126
Unable to establish connection with global catalog.

Event ID: 6702

DNS Server has updated its own host (A) records. In order to insure that
its DS-integrated peer DNS servers are able to replicate with this server,
an attempt was made to update them with the new records through dynamic
update. An error was encountered during this update, the record data is the
error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's ActiveDirectory replication partners do not have the
correct IP address(es) for this server, they will be unable to replicate
with it.



Any Ideas
 
In
Gary said:
A 3 year old 2000 server with 2 network cards and is DC.


Now it appears the DNS server is not configured. The zone is here but
the dns MMC is telling me it is not configured yet.
Click to expand...


You can run this command to kill the unconfigured mis-message.

dnscmd /Config /AdminConfigured 1

Or you can just ignore it. It's not a problem. The server state that
triggers this message is only read and written by the UI tool. It has no
impact whatsoever on the DNS Server's ability to resolve names.
Also I am getting the following errors:

Event ID: 1000
Windows cannot determine the user or computer name. Return value
(1703).


Event ID: 1655
The attempt to communicate with global catalog
\\server-1.office.botekusa.com failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup
failure.

The operation in progress might be unable to continue. The directory
service will use the locator to try find an available global catalog
server for the next operation that requires one.

The record data is the status code.

Event ID: 1126
Unable to establish connection with global catalog.

Event ID: 6702
Click to expand...

These above errors (not the config message) are *usually* attributed to
using an external DNS in your machines' IP properties. These need to be
removed and only use the internal DNS servers. That's why a DNS lookup
problem will occur. If you are using your ISP's, it maybe asking your ISP,
'where is my domain controller?'

It may also be caused by the fact that you have SP4 installed and your AD
DNS Domain name is a single label name
('domain' rather than the required format of 'domain.com').

If you can post an unedited ipconfig /all of the three DCs, that would be of
great benefit to diagnose this and usually will help us in 95% of the time
to come up with a resolve.

DNS Server has updated its own host (A) records. In order to insure
that its DS-integrated peer DNS servers are able to replicate with
this server, an attempt was made to update them with the new records
through dynamic update. An error was encountered during this update,
the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this
error should be ignored.

If this DNS server's ActiveDirectory replication partners do not have
the correct IP address(es) for this server, they will be unable to
replicate with it.
Click to expand...

This can be caused by a misconfig on the Interface tab (DNS server
properties) as to what IP it's listening on.

Any Ideas
Click to expand...




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In Gary <[email protected]> posted a question
Then Kevin replied below:
: A 3 year old 2000 server with 2 network cards and is DC.
:
:
: Now it appears the DNS server is not configured. The zone is here but
: the dns MMC is telling me it is not configured yet.
:
:
: Also I am getting the following errors:
:
: Event ID: 1000
: Windows cannot determine the user or computer name. Return value
: (1703).
:
:
: Event ID: 1655
: The attempt to communicate with global catalog
: \\server-1.office.botekusa.com failed with the following status:
:
: The DSA operation is unable to proceed because of a DNS lookup
: failure.
:
: The operation in progress might be unable to continue. The directory
: service will use the locator to try find an available global catalog
: server for the next operation that requires one.
:
: The record data is the status code.
:
: Event ID: 1126
: Unable to establish connection with global catalog.
:
: Event ID: 6702
:
: DNS Server has updated its own host (A) records. In order to insure
: that its DS-integrated peer DNS servers are able to replicate with
: this server, an attempt was made to update them with the new records
: through dynamic update. An error was encountered during this update,
: the record data is the error code.
:
: If this DNS server does not have any DS-integrated peers, then this
: error should be ignored.
:
: If this DNS server's ActiveDirectory replication partners do not have
: the correct IP address(es) for this server, they will be unable to
: replicate with it.
:
:
:
: Any Ideas

Check the DNS servers listening addresses.
This can be one of the many problems with multihomed DCs. What is the
purpose of the second NIC? Is file sharing bound to the NIC?
If one NIC is internal and one is external, make sure the internal NIC is at
the top of the binding order and that DNS is listening only on the internal
IP. You will also have to make modifications to the registry to prevent the
creation of the Global catalog records and the blank <domainname> records.
All of these errors can be cause by improper bindings on a multihomed DC.
Please verify what the second NIC is so as to help advise you correctly.
 
Back
Top