Hi,
Our company's DNS is split with an internal 'fake' view set up with
allow-recursion-override, as detailed in
http://doc.powerdns.com/recursion.html .
Before now, out of ignorance, I'd left the allow-recursion-override out
of the configuration. Questions with no answers in pdns's local
Greetings,
I am experiencing this same issue with the Postgres back-end and the latest
version of PDNS.
Going to try and downgrade in order to correct this problem.
- Original Message -
From: Pascal
To: pdns-users@mailman.powerdns.com
Sent: Friday, September 12, 2008 9:44 PM
Hello all,
I've gotten an emergency shutdown of powerdns recursor running in
production.
There are only one record in logs about this incident:
Sep 22 23:34:07 kit pdns_recursor[77218]: STL Exception: St9bad_alloc
System information:
# uname -sr
FreeBSD 6.2-STABLE
# pdns_recursor --version
v
Hello all,
I've got an emergency shutdown of powerdns recursor running in production.
There are only one record in logs about this incident:
Sep 22 23:34:07 kit pdns_recursor[77218]: STL Exception: St9bad_alloc
System information:
# uname -sr
FreeBSD 6.2-STABLE
# pdns_recursor --version
version
Hi all,
I am testing PDNS on Deb. Lenny using the default packages. My PDNS
version is 2.9.21.1
I created a dummy domain called foo.com and run the following dig command on it;
dig @localhost food.com SOA
I had enabled query logging and the following query raised my eyebrows;
Sep 22 15:10:45 Q