Bind behaves weirdly

[Vinny Abello]

At 07:05 PM 12/27/2004, Bill Larson wrote:
>On Dec 27, 2004, at 3:06 PM, jc pinoteau wrote:
>
> > I am using bind 9.2.3 for caching only on several gateways with
> > different
> > ISPs. On one of them I get weird results. It won't resolve google.com
> > (for
> > instance) for a few hours then it would do it again (without any
> > action from
> > my part). It will give the same result as if I was digging on a non
> > existing
> > domain.
> >
> > It is not a problem with the ISP as digging on the ISP's DNS returns a
> > good
> > result.
> >
> > If I restart bind it works again.
> >
> > How can I analyse what is happening?
>
>You can use "dig" with a "+trace" option to give more complete DNS
>resolution information.
>
> > options {
> >            forward first;
> >            forwarders {
> >                195.68.0.1;
> >                195.68.0.2;
> >            };
> > };
> >
>
>Are you sure that your "forwarders" statement is correct.  You have
>identified 192.68.0.1 and 192.68.0.2 as the servers that you are
>forwarding to.  Just guessing, are you sure that you don't want
>192.168.0.1 and 192.168.0.2 as your forwarders?  (The 192.68.0.0
>network belongs to a German organization.  These addresses don't
>respond to DNS queries so I suspect that they aren't functioning DNS
>servers.)

No, they identified 195.68.0.1 and 195.68.0.2 as their ISP's resolvers. 
They do respond to DNS queries.


Vinny Abello
Network Engineer
Server Management
vinny at tellurian.com
(973)300-9211 x 125
(973)940-6125 (Direct)
PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0  E935 5325 FBCB 0100 977A

Tellurian Networks - The Ultimate Internet Connection
http://www.tellurian.com (888)TELLURIAN

There are 10 kinds of people in the world. Those who understand binary and 
those that don't.