Gerald,
Thanks for the information, I think you may be on to something. I am not very
familiar with the 'dig' command, however when I use it against the reverse
address it does not resolve? As far as I can tell, I think the reverse tables
are set up correctly - is there a particular way I could tell?
Thanks again,
|--------+----------------------->
| | "Gerald |
| | Waugh" |
| | <gerald@waugh|
| | .com> |
| | |
| | 03/02/2001 |
| | 01:23 PM |
| | |
|--------+----------------------->
>--------------------------------------------------------|
| |
| To: Ashley E Andrews/Rush/RSH@RSH, "Lisa |
| Burke" <lbu...@once.com> |
| cc: bind-us...@isc.org |
| Subject: Re: nslookup - help. |
>--------------------------------------------------------|
> Hello,
> when using nslookup on one of the DNS servers here I can type for example
> test1.test and nslookup gives the response I am looking for - and
> automatically
> adds on to the end the last two segments rpslmc.edu - I don't have to. On
> another DNS machine here this is not happening. When I type in
test1.test -
> nslookup states it can't find test1.test. :NXDOMAIN. I guess I do not
> understand where nslookup pulls the last two segments in the host name
from
> (in
> this case rpslmc.edu). Strange that it works on one machine and not the
> other
> since they are using the same software?
> Ideas?
It may be that the reverse lookup is not working, for the IP.
nslookup will not work if it can't do both reverse and froward lookups.
Check your in-addr.arpa zone file.
Also, try 'dig'.
Gerald
