Re: Can't get NSlookup to work with 2003 dns
- From: "Kevin D. Goodknecht Sr. [MVP]" <admin@xxxxxxxxxxxxxx>
- Date: Tue, 15 Jul 2008 18:43:28 -0500
Read inline please.
In news:4889FFD8-D530-4205-BDB7-AA09C950C707@xxxxxxxxxxxxx,
CryptiniteDemon <CryptiniteDemon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I've tried everything on this one and I just can't solve it.
I'm running a few virtual LANs over a router and a switch. I'm able
to ping every computer from every other computer on the lan using
both the IP address and host names.
However, every time I try nslookup, i just can't get it to give me the
correct results. And I've set up the reverse zone a few different
ways with no luck in getting it to give me any host names of the
computers. So far the only thing I've been able to get is nslookup
to look up the DNS server ON the DNS server. If I do "nslookup
THETEST" from any machine but "THETEST" it doesn't work.
Here are the errors I'm getting with no reverse zone:
timeout was 2 seconds.
*** Can't find server name for address 10.99.6.100: Timed out
*Default servers are not avilable.
Server: UnKnown
Address: 10.99.6.100
*** UnKonw can't find THETEST: Server failed
You can't do an A record lookup and expect to get an answer from a reverse
zone.
when I create a reverse lookup zone for 10.in-addr.arpa along with a
pointer to THETEST, I still get the same crap when I do nslookup from
any computer that's not the DC.
So what's wrong here?
If the zone name is 10.in-addr.arpa., in order to create a PTR for IP
10.99.6.100, you need to create a sub-domain named 99, with a sub-domain
named 6 in it, then create a PTR named 100 with the server's name.
10.in-addr.arpa
|99
|6
100 PTR thetest.domain.com
Or create 6.99.10.in-addr.arpa.
100 PTR thetest.domain.com
Now, if you want to do "nslookup thetest"
Since "thetest" is not a valid DNS name, you need a DNS Suffix search list
and a zone for the domain name in the DNS suffix search list to make it
fully-qualified as a DNS name, thetest is not fully qualified, but
thetest.domain.com. is.(Yes, it requires the "." after the name to make it
fully-qualified as a DNS name.
Example, check your ipconfig /all, it will have your DNS Suffix search list
in it, if for example domain.com is your DNS Suffix search list, you need a
zone named domain.com for nslookup to do a single-label name lookup in. Then
you can create a host named thetest in the zone, and nslookup will find the
name by appending domain.com to the lookup.
--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
.
- Prev by Date: Re: Production DNS configuration help.
- Next by Date: Re: Problems with reverse zone resolution and BIND
- Previous by thread: Last Update - Anyone else having issues getitng root hints?
- Next by thread: DNS set up with dot-nothing
- Index(es):
Relevant Pages
|
