NSlookup Issues

  • Thread starter Thread starter pittspeed
  • Start date Start date
P

pittspeed

Hello everyone,

I have a weird issue... on my dns server or any of my clients the
following happens:

I grab an IP address, 192.168.0.1

so i type nslookup 192.168.0.1 and return a computer name Computer1

if i nslookup Computer1 i get no record found and if i ping Computer1 i get
no reply... as Computer1 isn't a computer on my network.

BUT if i jump into my DHPC and see who's pulling address 192.168.0.1 to see
it's ClientComputer, and nslookup ClientComputer i return 192.168.0.1

i can ping ClientComputer and get a responce, as well as browse into is, as
it IS a computer on my network...

So basically i get an incorrect / non-existant computer name while using
NSlookup on an IP address, but if i NSlookup the correct machine name, i
return the same IP.

needless to say, i'm confused. any help?
 
Check the append these suffixes, connection and primary dns suffix in the
NIC properties on computer1. Nslookup uses the suffix list when you
nslookup computer1. What is the domain you get for computer1 when you
nslookup by ip? If you nslookup or ping with the full dns name for
computer1 I'd bet all is well.

Lee
 
In
pittspeed said:
Hello everyone,

I have a weird issue... on my dns server or any of my clients the
following happens:

I grab an IP address, 192.168.0.1

so i type nslookup 192.168.0.1 and return a computer name Computer1

if i nslookup Computer1 i get no record found and if i ping Computer1
i get no reply... as Computer1 isn't a computer on my network.

BUT if i jump into my DHPC and see who's pulling address 192.168.0.1
to see it's ClientComputer, and nslookup ClientComputer i return
192.168.0.1

i can ping ClientComputer and get a responce, as well as browse into
is, as it IS a computer on my network...

So basically i get an incorrect / non-existant computer name while
using NSlookup on an IP address, but if i NSlookup the correct
machine name, i return the same IP.

needless to say, i'm confused. any help?
Click to expand...

If this is happening when you initialize nslookup (prior to entering any
commands), since nslookup uses the DNS server by default, (whatever IP is
configured for DNS in the machine's IP properties), it will look in the
reverse zone for an IP to name match. . That is the DNS server that nslookup
will use. If there is a PTR entry, it will return that. But that doesn't
mean the forward entry exists.

As Lee said, when you enter a command, if you use a single name, it will
suffix your searchlist suffix, which by default, unless it was changed, is
the Primary DNS SUffix of the machine. So it depends on the FQDN that is
being queried.

Keep in mind, that nslookup and ping uses two different resolution methods.
Ping uses the system's DNS Client and DHCP client services together.
Nslookup has a built in resolution in the executable itself and does not
rely on system services.

Check both forward and reverse entries for what is being queried to see if
they exist.

Ace
 
Back
Top