On Mon, Dec 11, 2006 at 04:54:58PM +, matt farey wrote:
> Hi,
> I have half a million entries in a hosts file on my gateway, a
> workaround to prevent access to these sites while dns is loading.
Matt,
Sorry for not getting back to you earlier!
> Can anyone please suggest a way I can persiste
On Wed, Dec 13, 2006 at 05:13:30PM -0500, Shawn Moore wrote:
> can't seem to get MX and NS working for just the domain test.com.
> A/PTR/CNAME all work. MX works if you query x.test.com, but not
> test.com. NS does not seem to work at all. I'm wondering if it has
> something to do with not havin
On 12/13/06, Augie Schwer <[EMAIL PROTECTED]> wrote:
Is there a reason why TCP queries are always getting sent to the
recursor (if available) for answers instead of checking for an
authoritative answer first and then recursing if no authoritative
answer was found?
I couldn't find anything in th
Is there a reason why TCP queries are always getting sent to the
recursor (if available) for answers instead of checking for an
authoritative answer first and then recursing if no authoritative
answer was found?
I am able to reproduce this by setting up a bogus zone in our
authoritative data (MyS
I am having an issue with the pipe backend, below you will find a
snippet of the perl script. The problem that I am having is that I
can't seem to get MX and NS working for just the domain test.com.
A/PTR/CNAME all work. MX works if you query x.test.com, but not
test.com. NS does not seem to wo
> I'm just implementing PowerDNS and am very impressed by how straightforward
> it has been. I'm about to replace our old Bind servers with powerdns, and
> was testing a few things and noticed that PowerDNS tells other server's
> it's version number. More specifically it says:
>
> Served by POWE
I'm just implementing PowerDNS and am very impressed by how straightforward it
has been. I'm about to replace our old Bind servers with powerdns, and was
testing a few things and noticed that PowerDNS tells other server's it's version
number. More specifically it says:
Served by POWERDNS 2.9.20
Reading through the mail list, monitor reports from pdns_server, and
documentation PowerDNS will cancel an AXFR transaction when it
encounters an unknown/unsupport mail type. Instead of canceling the
transaction, I would prefer to drop the record and continue with the
rest of the transfer. Sugg