At 10:26 AM 11/22/98 +0000, Glynn Clements wrote:
>Your reverse DNS isn't configured.
This is almost certainly true. type "host 192.168.0.2" and see if it gets
figured out. Or, from nslookup on Zaphod, try "192.168.0.2" or even "ls
0.168.192.IN-ADDR.ARPA" (assuming your netmask is 255.255.255.0.) Remember
that the DNS server must have entries going both ways (typically in a
.hosts and a .rev file)
However, I noticed something else as well:
At 01:59 PM 11/21/98 -0600, you wrote:
>Hi,
>
>pgmr$nslookup
>*** Can't find server name for address 192.168.0.2: Non-existent
>host/domain
>Default Server: ns01.ny.us.ibm.net
>Address: 165.87.194.244
>
192.168.x.x is reserved for disconnected networks. (I'm assuming that
Marvin is inside the LAN, right?) ns01.ny.us.ibm.net certainly isn't going
to be able to resolve names in 192.168.x.x. So, if you *have* configured
DNS to do reverse lookups, you would need to type "server 192.168.0.1"
before you would expect names to resolve in nslookup. Depending on your
setup, you might considering configuring Zaphod as a forwarder as well:
(a portion of named.boot)
forwarders 165.87.194.244
primary megadodo.umb mynet.hosts
primary 0.168.192.in-addr.arpa mynet.rev
That way you can use Zaphod as your default DNS server and everything will
be happy.
-Mike
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
