Help with reverse lookup file.
Danny Mayer
mayer at gis.net
Fri Oct 6 04:02:25 UTC 2000
What''s in the resolv.conf file on the system on which you are running
nslookup.
This file resides in /etc and needs to contain the domain name and a list
of nameserver
IP addresses. It looks like this:
domain memeticcandiru.com
nameserver 10.0.0.2
nameserver 10.0.0.3
I just went through this getting the tools to run on NT and this turned
out to
be the reason that it nslookup wasn't able to do anything. nslookup
needs to find
a nameserver to ship the requests to. nslookup also needs to be able to do
reverse name lookups so it can get the nameserver name from the IP address.
Dig doesn't require the latter step.
Danny
At 05:20 AM 10/5/00 +0000, $kr1p7_k177y at salmahayeksknockers.edu wrote:
>I'm running a caching DNS, for my internal network. The hostname
>is memeticcandiru.com, and has an external, public IP, and an internal IP,
>10.0.0.1. When I start nslookup, it complains that it can't resolve the
>address. I usually use Dig, but I'd like to get this fixed anyways.
>
>in my /etc/hosts, I have the entry "10.0.0.1 internal.memeticcandiru.com"
>
>here is the contents of /var/named/pz/10.0.0.1:
>
>@ IN SOA memeticcandiru.com. root.memeticcandiru.com (
> 1 ; Serial
> 8H ; Refresh
> 2H; Retry
> 1W ; Expire
> 1D) ; Minimum TTL
> NS memeticcandiru.com.
>1 PTR internal.memeticcandiru.com.
>
>
>I'm sure I'm close... Where did I go wrong?
>
>Any help appreciated,
>Dan.
>
>--
>............................................................................
>Even if you do learn to speak correct English, whom are you going to speak
>it to? - Clarence Darrow
>............................................................................
>www.geocities.com/pentagon/bunker/1022 swan_daniel at my-dejanews.com
>
More information about the bind-users
mailing list