strange DNS problem

[Bill Moran]

Wojciech Puchar <wojtek at tensor.3miasto.net> wrote:

> >>
> >> where's a problem? while hostr is able to get IP addresses but then
> >> reports servfail?
> >
> > I don't see that error when I try the same lookups.
> > host -t a hermes01.mil.be
> > hermes01.mil.be has address 194.7.21.40
> > hermes01.mil.be has address 193.191.219.40
> >
> > I suspect the problem is in your resolver config and/or caches.
> >
> possibly. but where to look? no other site behaves like this.
> 
> my named.conf:
> 
> acl seconds { 153.19.176.2; 10.254.1.254; 83.16.196.26;};
> acl locals {10/8; 127.0.0.1/32;};
> 
> options {
>          directory "/etc/namedb";
>          allow-transfer {seconds;};
>          pid-file        "/var/run/named/pid";
>          dump-file       "/var/dump/named_dump.db";
>          statistics-file "/var/stats/named.stats";
>          listen-on       { 127.0.0.1; 10.254.1.248; 83.18.148.142; };
>          listen-on-v6    { any; };
> };
> #logging {category lame-servers { null; };};
> 
> zone "." in {type hint; file "root.cache";};
> zone "0.0.127.in-addr.arpa" in { type master; file "127";};
> 
> and then master and slaves domains definitions below.

Just a theory:  Do you possibly have recursive queries locked down too
far, and does resolution of that name require recursion?

-- 
Bill Moran

I lay down for a while, and I woke up on the ocean,
floating on my back, and staring at the grey.
It was completely still, 'cept for the pounding of my heart,
was bring me back to life, from three strange days.