Nameserver problem when "-q=any" is used.

[Kevin Darcy]

The problem with -q=any is that most nameservers (most BIND nameservers at
least) treat -q=any queries as non-recursive even if they would normally honor
recursion. So if the PTR record you wanted to see didn't happen to be in the
cache of upoint.net.my, that explains why the lookup failed. Why don't you just
leave off the "-q=any"? upoint.net.my seems quite able to resolve a reverse
record for 216.98.150.25 now. Maybe you should re-submit your application or
get more clarification of what is meant by "[your] nameservers are not in
order".


- Kevin


Blue wrote:

> I recently have my ISP setting up virtual nameservers for me. The direct and
> reverse DNS are correctly shown when checked with NSLOOKUP:
> $NSLOOKUP ns1.updnnetwork.net >> 216.98.150.25
> $NSLOOKUP 216.98.150.25 >> ns1.updnnetwork.net
> (NS2 not shown in example)
>
> I then requested for a domain transfer. The domain registrar of my country
> rejected my application saying that my nameservers are not in order:
>
> % nslookup -q=any upoint.net.my 216.98.150.25
> *** Can't find server name for address 216.98.150.25: Non-existent
> host/domain
> *** Default servers are not available
>
> 1) What does "-q=any" for? The query result is negative when it is added to
> NSLOOKUP.
>
> 2) What is actually wrong with the nameservers?
>
> 3) How do I solve this problem?
>
> Thanks.