Missing Information

  • Thread starter Thread starter TJ
  • Start date Start date
T

TJ

If I type NSLookup at a command prompt, the first line
says it can't find the server name for address
192.168.x.x; then the line for default server reads
Unknown.

Am I missing a record in my DNS for NSLOOKUP to return
the name of my server? Thanks.

TJ
 
It's a common (non-)error. You can ignore it and you'll be fine or you can
"fix" it be creating a PTR for your DNS server in the Reverse lookup zone.



--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
If I type NSLookup at a command prompt, the first line
says it can't find the server name for address
192.168.x.x; then the line for default server reads
Unknown.

Am I missing a record in my DNS for NSLOOKUP to return
the name of my server? Thanks.

TJ
Click to expand...
Hi TJ,

Yes, this line states that nslookup was unable to make a reverse lookup query
to verify the fqdn of ip 192.168.x.x.

Look into or create a reverse lookup zone for your subnet. If the zone is set
on dynamic the DHCP-Client service is responsible to create the PTR-Record in
the zone, so just restart the service when the zone is available.

Gruesse - Sincerely,

Ulf B. Simon-Weidner
 
This is because of the way the programmed the tool. The first thing it does
is try to resolve the IP to a name so it can show it. If it can't, it posts
that message. Its not really an error, more like a status message. They
probably should supply a switch to turn resolving off of IPs. You can
ignore it.
 
Hi TJ,
Everyone is correct. The way NSLOOKUP works is it looks at your DNS
Settings, it selects the preffered DNS server, then does a REVERSE LOOKUP
on that name, this is by Design. If you don't have reverse lookup created,
then you can safely ignore the error. If you want it to go away, the
create the reverse lookup zone make it accept dynamic updates and the
server will register it's PTR records.


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

This article has a section on how to create the reverse lookup zone.
308201 HOW TO: Create a New Zone on a DNS Server in Windows 2000
http://support.microsoft.com/?id=308201

Hope this Helps!


Alan Wood[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
 
AWM> If you don't have reverse lookup created, then you can safely
AWM> ignore the error. If you want it to go away, [...]

.... then don't actually use "nslookup" in the first place, since this is but
one of its many flaws, and use a better DNS diagnosis tool instead.
Unfortunately, Microsoft doesn't provide one of its own along with its server
software (unlike the case with other DNS server softwares), so one has to
obtain other tools such as "dig" (which isn't hard, of course, as such tools
are freely and readily available).

I have suggested before that Microsoft's DNS server needs a good DNS diagnosis
tool, without any of the numerous flaws that "nslookup" has, and with a
textual user interface so that its output can be copied and pasted into a
newsgroup posting. It needs an equivalent to "dnsqr", "dnsq", "dig",
"dnsquery", "dnsqry", and "askmara" (which are some of the various such tools
that come bundled with other DNS server softwares).
 
Back
Top