Don't know if this is the problem, but it is worth looking into. Our local
DNS is on NT and I found that in order to make "something" work from our
3000s (I forget what since it was some time ago), I had to put a localhost
entry (127.0.0.1) into our DNS. It seems that in an all NT network, having
the localhost entry was not necessary, but it sure prevented "something"
from working on our 3000s.

John Burke

-----Original Message-----
From: Mark Bixby [mailto:[log in to unmask]]
Sent: Wednesday, May 17, 2000 1:20 PM
To: [log in to unmask]
Subject: Re: Using NT DNS server


Chuck Ryan wrote:
>
> I am attempting to get my 3000 to use our local DNS running on Windows NT
> 4.0.
>
> This server has a list of our local machines and if the name is not found
> locally, it forwards the request to our ISP's DNS. When I try an do an
> nslookup from the 3000, I get the following result:
>
> shell/iX> /BIND/PUB/bin/nslookup
> *** Can't find server name for address 192.0.0.98: Non-existent
host/domain
> *** Default servers are not available
>
> My RESLVCNF looks like this:
>
> domain svmic.com
> search svmic.com
> nameserver 192.0.0.98
>
> Any ideas on how I can make this work?

I believe nslookup is telling you that the nameserver running on 192.0.0.98
lacks a PTR record that maps 192.0.0.98 back to a host name.

Alas, I've never tried to run a DNS server on NT, so I don't know where to
tell
you to look to confirm or correct this.

- Mark B.