Thanks to everyone for the many replies.
It appears it was dnscache. The fix for me was to set FORWARDONLY
option ON and set the ISP dns server addresses (for use in FORWARDONLY).
I hope this helps others. Thanks,
On Tue, 2008-08-26 at 12:21 +, Erich Titl wrote:
> Hi Trev
>
> Trev Peterso
I encountered the same problem about a year+ ago but for different
websites, though I'm only running Dachstein. I got tired of dealing
with it and put my ISP's dns as the dhcpd distribution.
Trev Peterson wrote:
>Hello,
>
>I'm having a bit of a problem with dnscache. If anyone has run into
>
Hi
on 26.8.2008 04:17 Trev Peterson wrote:
> I'm having a bit of a problem with dnscache. If anyone has run into
> this problem and/or has a suggested solution it would be greatly
> appreciated.
> Firewall Version: Leaf Bering 2.4.32
> Package Name: dnscache.lrp
> Description: Some hosts are no
Hi Trev
Trev Peterson wrote:
> Hello,
>
> I'm having a bit of a problem with dnscache. If anyone has run into
> this problem and/or has a suggested solution it would be greatly
> appreciated. I should note we are not interested in changing to another
> package (we use tinydns extensively and ar
Hello,
I'm having a bit of a problem with dnscache. If anyone has run into
this problem and/or has a suggested solution it would be greatly
appreciated. I should note we are not interested in changing to another
package (we use tinydns extensively and are otherwise happy with
dnscache). Below a
