Re: [cobalt-users] [raq 3i] dns problem (nxdomain)

[flash22@xxxxxxx]

On Thu, 29 Mar 2001, John F. McClure wrote:

> I have a dns problem.
> [root@ns1 /root]# nslookup costaricaweb.com
> Server:  ns1.allbite.net
> Address:  216.88.27.4
> 
> *** ns1.allbite.net can't find costaricaweb.com: Non-existent host/domain

Remember to 'set debug' or set 'type=any', the above isn't necessarily an
error...It's really only saying there are no A records

The only thing i see wrong with costaricaweb.com is it's only listing one
of it's 2 nameservers...(and the nameserver is timing out a lot)
--
> Mar 29 09:17:24 ns1 named[2246]: sysquery: findns error (NXDOMAIN) on
> NS1.CENTRALAMERICAINTERNET.COM?
Possibly a side effect of below...
---

> 27.88.216.in-addr.arpa. IN      NS      ns1.centralamericainternet.com.

Something is very screwy with your reverse, when i do a query for 
96.27.88.216.in-addr.arpa, i get a spew of resolver errors, (truncated
replys) and a list of about 50 domain names on the same IP address//

eg:
    ANSWERS:
    ->  96.27.88.216.in-addr.arpa
        name = apartotel.com
        name = centralamericainternet.com
        name = costaricaabogado.com
        name = costaricaavvocato.com
.....

Which is not what i should get from what you say is in the zone..
> 96      in      ptr     ns1.centralamericainternet.com.
> 97      in      ptr     ns2.centralamericainternet.com.
> 
> There are more records, but they all seem to be correct.
> If I do a nslookup from a machine that uses a different name server (other
> than my cobalt) the nslookup works.

Your nameserver isn't in fact authorative for that in-addr range...

Authoritative answers can be found from:
27.88.216.in-addr.arpa  nameserver = ns1.exsbs.net
27.88.216.in-addr.arpa  nameserver = ns2.exsbs.net

Also the authority path in general to there is somewhat bogus, this is
probably partly someone elses problem, 

root->ns1.exsbs.net
but ns1.exsbs.net claims 4 nameservers, 
27.88.216.in-addr.arpa  nameserver = ns1.exsbs.net
27.88.216.in-addr.arpa  nameserver = ns2.exsbs.net
27.88.216.in-addr.arpa  nameserver = ns1.connectup.com
27.88.216.in-addr.arpa  nameserver = ns2.connectup.com

but the second 2 claim only themselves
Server:   209.211.1.2
96.27.88.216.in-addr.arpa       name = ip096.tteam.com
27.88.216.IN-ADDR.ARPA  nameserver = ns1.connectup.com
27.88.216.IN-ADDR.ARPA  nameserver = ns2.connectup.com


None of these are your nameserver, so using a nameserver other than yours
will not see any of this screwed up zone ;)


gsh