failed DNS lookup



  • 1. Why run a backup before running ADPrep?
    Funny question, huh? In KB325379 - How to upgrade Windows 2000 domain controllers to Windows Server 2003, it reads, "Make a system state backup of at least two domain controllers in every domain in the forest. You can use the backup to recover all the domains in the forest if the upgrade does not work." Only problem is, you can't restore Schema changes, even if you use an Authoritative Restore. So unless your AD domain consists of a single Domain Controller, I guess you are out of luck. Of course, the reason for the backup is to restore your DC that you are doing the upgrade on should the upgrade fail (this assumes that you have turned off outbound replication). May have been worth being more clear on this in the KB article.
  • 2. Security Groups and OU Delegation Wizard
    I've just setup AD Win2k3 and we have several independent OUs defined under a single domain which are managed individually by dedicated people. I've used Delegation Wizard to delegate control to given user groups in each individual OU to manage their own OU...... What I want to do is for example if I have a user in OU1 and another user in OU2 each seperate and independently managed. Is there any way of restricting an administrator in OU1 adding a user from OU2 into a security group in OU1..... As I have already use delegation wizard to restrict each OUs admin to be only allowed to modify objects within their own OU......... Any suggestions please HELP!!!!!!!!!!!!!! Thanks in advance
  • 3. windows 2000 + windows 2003
    hi all, i am using windows 2000 server as a domain controller, and i want to add one more server with windows 2003 for reduce the loading of windows 2000 server, is that use the dcprom to add other domain controller to same domain ??? what should i pay attention to ? thanks ! tony
  • 4. Windows large file copying problem
    Hi all, When copying large files in windows explorer from client to server station (win2000), very often copying breaks with message: "An error ocurred while reconnecting... Microsoft Windows Network: The local device name is already in use This connection has not been restored" Copying the same file with FTP protocol is OK. What could it be? Thanks in advance, Ivana

failed DNS lookup

Postby troy » Mon, 15 Nov 2004 12:20:09 GMT

When I run DCDIAG /f:logname I get the following error. How can I fix this?

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\DCCIPDC
      Starting test: Connectivity
         The host 
could not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name 
( couldn't 
be resolved, the server name ( resolved to the 
IP address ( and was pingable.  Check that the IP 
address is registered correctly with the DNS server.
         ......................... DCCIPDC failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\DCCIPDC
      Skipping all tests, because server DCCIPDC is
      not responding to directory service requests

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test 
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test 
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test 
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : dcci
      Starting test: CrossRefValidation
         ......................... dcci passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... dcci passed test CheckSDRefDom

   Running enterprise tests on :
      Starting test: Intersite
         ......................... passed test Intersite
      Starting test: FsmoCheck
         ......................... passed test FsmoCheck

Re: failed DNS lookup

Postby Miha Pihler » Mon, 15 Nov 2004 17:45:46 GMT

i Troy,

How is DNS configured (under TCP/IP properties) on your domain controllers?

If your domain controllers are also DNS servers they should point back to
themselves -- on Windows 2003 you can enter as preferred DNS
server under TCP/IP properties and on Windows 2000 DC you should enter it's
real IP (it won't allow you to enter Preferred DNS on your DC
should not point to e.g. your ISP.
If you do these changes, make sure you restart NetLogon service.


"troy" <troyds@deltaprocess(NoSpam).com> wrote in message
news: XXXX@XXXXX.COM ...

Similar Threads:

1.replication failing, dns lookup failure

I ran repadmin agains one of my domain controllers and all of the 
replications with partners a completing except one. It is failing with "the 
dsa operation is unable to proceed because of a dns lookup failure".  I went 
into sights and services and clicked on the ntds settings for the server 
that isn't replicating, right clicked on NTDS settings, and chose replicate 
now. I get the following:

The following error occurred during the attempt to contact the domain 
controller "dc":
The RPC server is unavailable.
This condition may be caused by a DNS lookup problem.

Anyone know what is going on? 

2.Problem with XP caching failed DNS lookups

I have a problem with a windows XP box I have recently acquired

I connect this box to the net through a proxy machine with a modem. On
attempting to connect the proxy dials on demand and connects and
everything is automatic from then on - usually.

What happens with the XP client is that I will attempt to go to a web
page ( for example ), the proxy dials up and connects. By
this time XP has decided it would get no response and returned an
error. Now on every other box I have used as a client I could then
reload and the page would come up, ie it is only a spurious error
because the dial up connection is slower than the application's
timeout. But with XP it appears to have cached the name server
information so that subsequent connection attempts will also fail,
albeit that they fail immediately, but connections to a new address (
e.g. ) work correctly.

The only way to connect to the original page appears to be to reboot
XP. How can I persuade XP that it really doesn't know as much as it
thinks it does and make this box connect?


3.DNS lookup is failing

4.reverse DNS lookup test failed

5.To add... DNS lookup is failing

Krish Sundaresan [MSFT] < XXXX@XXXXX.COM > posted their
thoughts, then I offered mine
> unlikely to be a hosts file issue, since seems to work fine with
> pointing against public DNS Server.

If there's a firewall blocking TCP 53, then that may also cause the issue
(assuming that the domains they are trying to get to are returning a
response larger than 500 bytes).


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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. -- 

6. DNS Reserve Lookup Fails

7. W2K DNS Server fails on unqualified name lookup

8. DNS lookup fails on first attempt only



Who is online

Users browsing this forum: No registered users and 21 guest