Error: Impossible to find server name for address w.x.y.z - Non-existent domain

  • Thread starter Thread starter Vince C.
  • Start date Start date
V

Vince C.

Hi.

When I'm issuing the command "nslookup" I get the error message above. Whatever
the address I type I get that error message. The IP is still resolved but there
is that additional error on the first line:

C:\WINNT\System32>nslookup www.cybernet.be
*** Impossible to find server name for address 192.168.x.y : Non-existent domain
*** Default servers are not available
Server : UnKnown <-- There was my server's name before
Address: 192.168.x.y

Non-authoritative response :
Nom : www.cybernet.be
Address: 213.177.65.10

The error is on the first line. It appears when I issue the command on the
server itself as well. Can someone explain to me why I'm getting this all at
once (I didn't get it before)? I have 2 NICs on the server. Is there a quirk
with the adapter and/or TCP/IP config or something?

Thanks,
Vince C.
 
From:
242906 "DNS Request Timed Out" Error Message When You Start Nslookup From a
http://support.microsoft.com/?id=242906

When Nslookup starts, it attempts to resolve the IP address of its host's
DNS server to its fully qualified domain name (FQDN). If the DNS server
does not respond or if the DNS server's reverse lookup zones do not contain
a PTR record for the DNS server's IP address, the error message is
displayed.

Most likely explanation is the PTR record for the DNS server is missing

--------------------
Hi.

When I'm issuing the command "nslookup" I get the error message above. Whatever
the address I type I get that error message. The IP is still resolved but there
is that additional error on the first line:

C:\WINNT\System32>nslookup www.cybernet.be
*** Impossible to find server name for address 192.168.x.y : Non-existent domain
*** Default servers are not available
Server : UnKnown <-- There was my server's name before
Address: 192.168.x.y

Non-authoritative response :
Nom : www.cybernet.be
Address: 213.177.65.10

The error is on the first line. It appears when I issue the command on the
server itself as well. Can someone explain to me why I'm getting this all at
once (I didn't get it before)? I have 2 NICs on the server. Is there a quirk
with the adapter and/or TCP/IP config or something?

Thanks,
Vince C.
Click to expand...

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
 
Back
Top