Query Refused

[Kevin Darcy]

nslookup sucks. It aborts if it can't reverse-resolve the address of the
nameserver(s) it is trying to use. In this case, it can't get an answer for
reverse queries of 202.5.65.66 and 202.5.65.67. So it just gives up. Charming.

Use a real lookup tool instead, like "dig". Failing that, find out why those
addresses don't reverse-resolve and fix the problem. Of course, it might be
difficult to troubleshoot that problem using nslookup...


- Kevin

Allie Syadiqin wrote:

> Hi,
>      I am using Wirex's Immunix ISP Appliance OS based on RH 7.0. The OS is
> currently using Bind 8.2.3. I installed the OS without any hitch, and
> everything was fine, until a few days later.
>
> I tried to perform an nslookup using the following command :-
>
> # nslookup -q=any abc.com ns1.abc.com
>
> and received the following errors :-
>
> *** Can't find server name for address 202.5.65.66: Query refused
> *** Can't find server name for address 202.5.65.67: No response from server
> *** Default servers are not available
>
> I tried do the nslookup from both external and on the local machine but
> both response are the same. Any idea what went wrong?