failed DNS lookup



  • 1. SYSVOL problem
    Hi we have a windows 2003 server that is having problems. It is the only server in the domain so we decided to install a second one get everything replicated and rebuild the first. The problem we are having is trying to get the SYSVOL to replicate onto the new server. In the old server we have an error; Event ID 13568 - The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. How can we fix this so that we can get replication working to the new server? Thanks in advance Nat
  • 3. Disk Quota
    How can i apply disk quota in a domain after configuring group policy?
  • 4. can only see local machine users when trying to add users allowed for remote desktop access
    Hi, I have a windows 2003 server on my network(its actually a virtual machine running on windows server 2008), that I have enabled remote access to (via properties of 'My Pc/Remote') In the permission of the remote user tab, I can not find any domain users, if I try to change location it only allows me to see the local machine, and if i enter manually the domain\user name it always rejects it. I can see the entire network when I browse the network from file explorer and I can access shares on remotes machines with no problem, so I am on the network and authenticated by the domain controller.. How can I get this problem solved ?
  • 5. symbolic link not working via share ?
    I have a shared folder on a win2008 server, which has several folders and files which are read for domain users, and also a symbolic link to another folder on the same drive which has again read permission for domain users. However when I access the share and navigate down to the symbolic link and click on that folder I get various error messages. On a server 2003 and an xp machine I get "\\server2008\folder\link is not accessible......cannot find message number 0x in the message file for \\server2008\folder\link". I guess this is because xp/2003 does not understand symbolic links ? (which is a real drop off to using them). From a vista machine ( Note: I have allowed L2L/R2R/R2L/L2R) I get a different error. When I browse to the linked folder I get a message saying the folder accessed is not available. If I logon to the machine hosting the share with the same user credentials I can browse to the linked folder fine. Tony

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 42 guest