BIND 9.3.2-P1 failing completely on some domains

[Paul A. Hoadley]

On Mon, 18 Sep 2006 20:59:38 -0400, Barry Margolin <barmar at alum.mit.edu> wrote:
> In article <eemed2$1vht$1 at sf1.isc.org>,
>  "Paul A. Hoadley" <paulh at logicsquad.net> wrote:
>
>> Why can I get an A record for a.podbase.com when tracing is on, and
>> not without?]
>
> Because the address is coming from the GTLD server as a glue record,
> not from 85.228.72.199.

Ah, thanks.

> So it looks like there's something preventing you from communicating
> with a.podbase.com.

As someone else (I think it was Kevin) noted, BIND was telling me that
the address for a.podbase.com was 192.168.0.1, which is obviously
incorrect.  I have noticed this before with my BIND setup: sometimes
when it's queried for a non-existent domain, or a domain it
temporarily can't find any information about, it will return
192.168.0.1 (the nameserver's own address).  This bogus address will
eventually expire, and it will return useful information again: today
I can dig 'a.podbase.com' and 'www.eve-files.com' just fine.

There is clearly a problem with my BIND configuration.  If anyone has
the time and inclination to look over it for me, I've put up
named.conf and the zone files here:

http://logicsquad.net/namedb/

(I can also post them to the newsgroup if that is preferred.)


-- 
Paul.

Logic Squad -- Technical Publishing with XML -- http://logicsquad.net/