Hi all.
* What PowerDNS version you are using
# pdns_control version
3.1 (on both servers)
* What backends you use (gMySQL, BIND etc)
gmysql is used
* If you are using DNSSEC
DNSSEC is not used.
* Operating system it is running on
Debian 7 on both
* Where you got the binary from,
Hello,
On 11 May 2015, at 9:14, Mislav | sys admin wrote:
* What is going wrong
I'm having problem with updating slaves after making changes on
master. Slaves are not getting updated at all. After I type manually
on the master server:
# pdns_control notify-host domain host
then of
On Mon, May 11, 2015 at 09:14:51AM +0200, Mislav | sys admin wrote:
I'm having problem with updating slaves after making changes on
master. Slaves are not getting updated at all. After I type manually
on the master server:
Did you remember to update your SOA record serial to larger number as
On Mon, May 11, 2015 at 03:29:34PM +1000, Dean Hamstead wrote:
Dear Pdns-Users
I am hoping for feedback on a proof of concept (aka quick hack) that
has powerdns serve forward and reverse DNS records from a template
and a list of cidr's - implemented via gpgsql. Let's call it a
Hello,
On 10 May 2015, at 7:05, ggiesen+power...@giesen.me wrote:
However I've run into a snag. I can't find any way to have PowerDNS
answer
recursion queries on only the IP #1 (I can only limit what IPs the
queries
come from, but not to). Am I missing something, is there a way to do
what
No, I didn't update any SOA records.
I've just tried that and it seems like this is not working for me, but
I've figure it out if I change last_check to NULL, powerdns not only
synchronize all DNS records, but it also update SOA record.
Thanks
@Peter
On master server, every domain is set to
The README file describes motivations behind design choices.
Dean
On 11/05/15 21:55, Aki Tuomi wrote:
On Mon, May 11, 2015 at 03:29:34PM +1000, Dean Hamstead wrote:
Dear Pdns-Users
I am hoping for feedback on a proof of concept (aka quick hack) that
has powerdns serve forward and reverse
Since the PowerDNS Recursor and PowerDNS Authoritative server are two different
products, you’ll need to run both anyway.
Run the recursor listening only on IP#1 (using the local-address setting) and
the authoritative server listening only on IP#2 (using the local address
setting).
During
That solution would actually work quite well. Only downside is that I’ll have
to provide our staff CLI access to the PowerDNS servers to be able to be able
to remove the forward-zones setting for each domain as they are migrated (or we
can have someone do them in bulk afterwards as I don’t
And really this is the last of it, but the presentation can be viewed on
https://www.youtube.com/watch?feature=player_embeddedv=PX3YYmBER7E#t=6403
and also contains various other potentially interesting powerdns things.
A full writeup of the meeting has been published on our blog,
10 matches
Mail list logo
