Why Bind searches two times before answearing?

[Kevin Darcy]

Well, you say your forwarder "works great when directly contacted", but
the symptoms you describe sound more like the forwarder is taking too
long to answer the queries. What happens if you query the forwarder
directly from your nameserver? Is the response time reasonable? This
should mimic exactly what your nameserver is doing when resolving queries
for its clients.


- Kevin

Roberto wrote:

> Hi all,
>  I installed Bind on a Redhat 7.2 but it seems not so good :-) , but
> aybe it's just me not configuring it well :-|
>
> I use dig to check for outer domain names but I have to query any
> domain name two times before getting an answer.
> I use it as a caching nameserver. I have a forwarder (external DNS)
> that works great when directly contacted.
>
> 192.168.1.1 is my Caching DNS host IP.
> /etc/resolv.conf contains:
> domain mydomain
> nameserver 192.168.1.1
>
> 192.168.200.254 is the external DNS IP.
> /etc/named.conf contains
> options {
>         directory "/var/named";
>         forward only;
>         forwarders {
>                 192.168.200.254 ;
>         };
>         listen-on {192.168.1.1; 127.0.0.1; };
> }
>
> First time I try "dig www.yahoo.com" I get "connection timed out; no
> server could be reached".
> The second time I get the answer. It works this way for every domain
> name I try. Starting at the second time the answer is in the NS Cache.
>
> What's wrong? Any idea? Any suggestion? Where to read about?
>
>  thank you all,
>           Roberto
>
> Please post via email too.