Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Oct 2006 14:28:49 +0200 (CEST)
From:      Wojciech Puchar <wojtek@tensor.3miasto.net>
To:        Bill Moran <wmoran@collaborativefusion.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: strange DNS problem
Message-ID:  <20061006142718.T74782@chylonia.3miasto.net>
In-Reply-To: <20061006072907.cf58999a.wmoran@collaborativefusion.com>
References:  <20061006105745.V54913@chylonia.3miasto.net> <20061006072907.cf58999a.wmoran@collaborativefusion.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
>>
>> 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.





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20061006142718.T74782>