WinNT BIND8.3.1 Tools - autodetect nameserver/domainname
John Tobias
JTobias at gilead.com
Wed May 22 16:18:55 UTC 2002
I've never user this tool, however, the symptoms appear as if the tool isn't
using the standard Windows resolver. Look for a resolv.conf file and edit
appropriately.
Hth,
John Tobias
Sr. Network Engineer
Gilead Sciences
-----Original Message-----
From: J.Smith [mailto:lbalbalba at hotmail.com]
Sent: Wednesday, May 22, 2002 2:03 AM
To: bind-users at isc.org
Subject: WinNT BIND8.3.1 Tools - autodetect nameserver/domainname
Hi.
I have just downloaded and installed the BIND8.3.1 Tools for Windows NT4.
Although the 'lookup' tools (host, nslookup, etc) seem to work, I have some
minor problems with them:
- automatic dns nameserver detection
When I run host like this :
host hostnam-i-want-to-resolve.domainname
I get the error that ti cant find a dns server, even though the 'ipconfig'
command shows I have a DNS server configured on my system.
But running host like this :
host hostnam-i-want-to-resolve.domainname ip-adress-of-my-dns-server
host runs fine.
Would it be possible to let these command retrieve the DNS Server I have
configured on my system and use that as the default ?
- automatic 'default domain' detection
When I run host like this :
host hostnam-i-want-to-resolve.domainname ip-adress-of-my-dns-server
host works fine
but when I leave out the domainname, like this:
host hostnam-i-want-to-resolve ip-adress-of-my-dns-server
host complains that there is now such host, even though I have a domain name
configured on my NT system.
Would it be possible to let these command retrieve the 'default domain name'
I have configured on my system and use that as the default ?
By the way, similair things happen for nslookup (and dig too, I suspect). I
am not running them on a dns server, just on a simple client.
Sincerely,
J.Smith
More information about the bind-users
mailing list