I figured out what the problem was. I had put in my bind9 option area the
statement: (numbers missing to protect the innocent.)
allow-recursion {
209.102.xxx.xx;
209.102.xxx.xx;
};
To allow 2 mail servers to do recursion to this name server. This seem to
cause the problem. When I removed the 2 mail servers and put in this
statement:
allow-recursion {
any;
};
It started working again.
Then the name server when queried on the name server machine, ie. dig
bozo.com 127.0.0.1, could query it self and get a reply even though the
URL was not cached on that machine. Before this change all I could query
was what was in the name server cache. Maybe you need to put in the
127.0.0.1 address in the allow-recursion statement as well?
This seems like a bug to me.
Ken Rea
On Mon, 7 Nov 2005, Account for Debian group mail wrote:
>
> I'm getting a strange behavior (for me anyway...) on Bind9. I just set up
> a new Debian Sarge server with bind9. Anyway, I can do a dig lookup on a
> domain name from this new server using 127.0.0.1 (# dig bozo.com 127.0.0.1)
> and it will not find the address. Then I can go to another server and
> direct the dig at the new server and it will find this address. Then I go
> back to the new server where I could not resolve that same address in the
> first place and now it will resolve it.
>
> I can resolve any address from the new server as long as another server
> has already looked it up from this new server.
>
> Any Ideas? BTW there is no firewall involved.
>
> Thanks,
>
> Ken Rea
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
