[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: nslookup not finding server
- From: Kevin Colby <kevinc grainsystems com>
- To: redhat-install-list redhat com
- Subject: Re: nslookup not finding server
- Date: Thu, 22 Jun 2000 16:49:44 -0500
It looks like it can't connect to the DNS server.
Try telnetting to the 204.167.104.162, port 53.
You should get something like:
--------------------------------
Connected to ns.n-p-i.net.
Escape character is '^]'.
--------------------------------
If not, either you have networking/routing issues
or that machine is not running a DNS server.
- Kevin Colby
kevinc grainsystems com
"Brian A. Bucher" wrote:
>
> Greetings again,
>
> My question is: Why is nslookup not finding the server, even though it's
> listed in /etc/resolv.conf and is running named? It's actually running two
> named daemons listening on different interfaces, as described in the "Setting
> Up Your New Domain Mini-HOWTO". What a superb document. Anyways, here is the
> relevant info as far as I can tell:
>
> [~](13)$ more /etc/resolv.conf
> search n-p-i.net
> nameserver 204.167.104.162
> nameserver 192.233.85.129
> [~](14)$ nslookup
> *** Can't find server name for address 204.167.104.162: Non-existent host/domain
> Default Server: frigate.shore.net
> Address: 192.233.85.129
>
> > exit
> [~](15)$
>
> So, where is nslookup supposed to find the "server name" for address
> 204.167.104.162?
>
> Thanks!
>
> Brian
>
> --
> To unsubscribe: mail redhat-install-list-request redhat com with
> "unsubscribe" as the Subject.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]