The “name” field must be the full hostname that ends with the domain name to be
valid.
Here’s an example from a working zone:
MariaDB [powerdns]> select * from domains limit 1;
++++++-+-+-+
| id | name | master | last_
The backend is going to determine what can be done and I am not seeing that
below. There are many option depending on how complex the changes are in that
zone in the DR site. If you have a similar IP subnet scheme in a /23 or /24
with the same 4th octet and the backend is a database, then a sc
FYI, there are many ways to transfer the data from one DNS auth server into
pdns. This method should work with any type of DNS master and is pretty simple
to do without having to do direct database inserts that are tough to understand
when first learning PowerDNS. Later on when PowerDNS has be
27;in.ena.net' to 96.4.0.36:53 (was acknowledged)
Jan 06 05:06:04 pdns01 pdns_server[26930]: Removed from notification
list: 'in.ena.net' to [2610:128:1200:ad::36]:53 (was acknowledged)
Note that if you have IPv6 enabled on your servers, some of the
communications will happen over IPv6 even if yo
I have PowerDNS hidden masters (MASTER) managed by PowerAdmin/PowerDNS API
using MySQL replication with PowerDNS public slaves that use NOTIFY/AXFR
(SLAVE). Every day or two I get this in my hidden master logs when they have
just sent a NOTIFY and the public slave tries to do the AXFR:
May 17
>From: Pdns-users
>on behalf of Pieter Lexis
>This smells like a bug in the API (as `pdnsutil check-zone` will complain
>about it). Can one of you open a bug report on github about this[1]?
Done. https://github.com/PowerDNS/pdns/issues/5305
Dave
___
>From: Pdns-users
>on behalf of Diego Bellini
>Morning!
>Does anyone have any suggestion for me?
I have noticed the same thing. We have some developers writing an
internal interface to manage our PowerDNS via the API and I also
noticed that the API allows this when it shouldn't.
Dave
>Cheer
>From: Pdns-users
>on behalf of Roberto Quiñones
>Hi, I'm sorry for the inconvenience, I've tried to install powerdns
>in centos 7 following a document, but this does not help me with
>the part of if I want to replicate the zones to a secondary (slave)
>server. Given this I do not know if in cen
From: Pdns-users on behalf of Fabian
A. Santiago
>On May 4, 2017 6:15:35 AM EDT, Remi Gacogne wrote:
>>On 05/04/2017 12:09 PM, Fabian A. Santiago wrote:
'allow-notify-from' defaults to '0.0.0.0/0,::/0', which allows
everything. Of course additional checks are performed afterward
I have a PowerDNS server setup as a slave and see this in my logs constantly:
Received NOTIFY for example.com from 1.2.3.4 but remote is not permitted by
TSIG or allow-notify-from
I was hoping to not have to maintain a long list of master IPs in the
allow-notify-from. One would think that the
>Hi,
>I am trying to use zone2sql to migrate from BIND 9.6 to PowerDNS
>3.4.11. My named.conf looks like this:
I recommend setting up the pdns server as a slave to the BIND
master to do the migration. Put the pdns server IP in the global
also-notify. Setup the pdns server as a superslave to the
>From: Brian Candler
>Sent: Thursday, April 13, 2017 10:42 AM
>To: David Jones; Fabian A. Santiago; pdns-users@mailman.powerdns.com
>Subject: Re: [Pdns-users] Zone transfer from previous DNS (Google domains)
>On 13/04/2017 16:22, David Jones wrote:
>> It would be nice
>From: Pdns-users on behalf of Fabian
>A. Santiago >
>Sent: Thursday, April 13, 2017 9:47 AM
>To: pdns-users@mailman.powerdns.com
>Subject: [Pdns-users] Zone transfer from previous DNS (Google domains)
>Would anyone here have any idea on how to zone transfer all records for
>a particular domain
>From: Pdns-users on behalf of Bill
>Yuan
>Sent: Monday, February 13, 2017 8:57 AM
>To: pdns-users@mailman.powerdns.com
>Subject: [Pdns-users] how to ignore the warning
>Hi,
>I using an old version of pdns recursor, and I got below message in
>var/log/message
>pdns_recursor[1308]: PowerDNS S
PowerDNS-Admin is pretty nice but it doesn't have some features we need. It
should be the first one you try out and should be fine for most.
We are currently using a locally patched version of PowerAdmin that is pretty
old but does the job. The project is dead.
We are working on our own DNS M
I use Python to update the pdns database from other sources and it has to
calculate and update the serial. We use PowerAdmin as well which does the same
thing. It would be better if this were internal to pdns to centralize it for
consistency. We may end up writing our own web administration f
Recently our pdns-recursor servers updated from 3.5.3 to 3.6.0 from the EPEL
repo. The daemon would not start due to the existing
/etc/pdns-recursor/recursor.conf having these two settings:
-additional-processing=on
additional-processing=on
I found this in the release notes:
https://git
?Normally you should compare your active pdns.conf to the pdns.conf.rpmnew to
see if there are any new features/options added. Use "diff pdns.conf
pdns.conf.rpmnew" to get the differences then ignore the same options that
merely have your specific settings on the right side of the equals sign.
18 matches
Mail list logo
