nslookup error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am running DNS on my Win2003 server with WinXP Pro clients. we have a
broadband connection that servers as our internet gateway. All clients up
static ip address and so does the server. The router gets its own ip from the
ISP. we have DNS forward lookup running but no reverse. All of the clients
are set to the server as the primary DNS and our ISP DNS as the secondary in
case the server is down. The server only has itself as the DNS. Question:
When I run NSLOOKUP from my clients, I get the following error:
***Can't find server name for address 192.168.1.101: Non-existent domain
Default Server: ns01.taylor01.mi.comcast.net
Address: 68.42.244.5

It is obviously resolving my servers IP because it is displayed, why does it
show this error message and what can I do to fix it?
 
You said it yourself: "we have DNS forward lookup running but no reverse"
You need the reverse lookup setup.
 
ok, how do I do this? Origianally, we had a microsoft tech remote into our
server and help us setup the DNS, apparently he did not provide a reverse and
our support has run out.
 
In
Jon Domke said:
ok, how do I do this? Origianally, we had a microsoft
tech remote into our server and help us setup the DNS,
apparently he did not provide a reverse and our support
has run out.
Click to expand...

Create a new reverse lookup zone for the 192.168.1 Subnet. Don't reverse
these in the wizard.
You also have a choice to use a reverse lookup zone name, this one is
reversed, use 1.168.192.in-addr.arpa.
 
Jon Domke said:
When I run NSLOOKUP from my clients, I get the following error:
***Can't find server name for address 192.168.1.101: Non-existent domain
Default Server: ns01.taylor01.mi.comcast.net
Address: 68.42.244.5
Click to expand...

This error message can be safely ignored as nslookup per default always
performs a reverse DNS lookup of the DNS Server when first started.
Subsequent DNS queries will work just fine.

As suggested by the others, create a corresponding reverse DNS zone would be
the solution. If the DNS Server IP points to a hardware device e.g. NAT
router, this may not be necessary.

Hope this helps. Do let us know. Thanks!
 
Thanks, works great now.

Desmond Lee said:
This error message can be safely ignored as nslookup per default always
performs a reverse DNS lookup of the DNS Server when first started.
Subsequent DNS queries will work just fine.

As suggested by the others, create a corresponding reverse DNS zone would be
the solution. If the DNS Server IP points to a hardware device e.g. NAT
router, this may not be necessary.

Hope this helps. Do let us know. Thanks!
Click to expand...
 
Back
Top