Re: [Pdns-users] package build instructions (was: Re: PDNS repos request)

[Alex Pavlov via Pdns-users]

Thank you Peter,

This helps in building PDNS binaries from sources  

Meanwhile have one question about DoH & DoT implementation in DNSDIST 1.5 and 
higher.
Is written in documentation "...like CertBot, set permissions assuming that 
services are started as root, which is no longer true for dnsdist as of 1.5.0. 
For that particular case, making a copy of the necessary files in the 
/etc/dnsdist directory is advised, using for example CertBot’s --deploy-hook 
feature to copy the files with the right permissions after a renewal."

So I set my CertBot with --deploy-hook which copy certs in to /etc/dnsdist and 
than do proper chmod and chown for files so dnsdist be able to read it. That is 
done and works fine... however rising one more question: When certs expired 
(after each 90 days period) and my CertBot do "certbot renew" it replaces the 
certs files in /etc/dnsdist and changes permissions. 
Does DNSDIST process detects that files changed and serves DoH|DoT from new 
cert files ? 
Or need to add one more command in  --deploy-hook  to restart DNSDIST if certs 
changed (like: "systemctl restart dnsdist") ?

If somebody knows the answers please reply.

Regards,
Alex.
-Original Message-
From: Pdns-users  On Behalf Of Peter 
van Dijk via Pdns-users
Sent: Monday, October 09, 2023 1:23 PM
To: pdns-users@mailman.powerdns.com
Cc: Peter van Dijk 
Subject: [Pdns-users] package build instructions (was: Re: PDNS repos request)

On Thu, 2023-10-05 at 17:45 +0200, Peter van Dijk via Pdns-users wrote:
> On Tue, 2023-10-03 at 20:38 +0300, Alex Pavlov via Pdns-users wrote:
> > Hello To all PDNS admins,
> >  
> > Recently the  older PDNS repos were deleted from official PDNS Repo 
> > website.
> > The distros for Ubuntu 16.x (Xenial) and 18.x (Bionic) were wiped 
> > out without any link to “archives” or “old releases”.
> 
> As indicated by another reply in this thread, yes, those releases are 
> EOL, and thus we do not publish packages for them.
> 
> It's easy to rebuild these packages for yourself if you really need them:

We now have more extensive documentation at 
https://github.com/PowerDNS/pdns/blob/master/BUILDING-PACKAGES.md - with this, 
it should be easy to build the packages you need, without running into 
dependency troubles.

Kind regards,
--
Peter van Dijk
PowerDNS.com B.V. - https://www.powerdns.com/ 
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] PDNS repos request

[Alex Pavlov via Pdns-users]

Hi Frank,

 

On top of that, it seems you're blaming others for issues which you are 
responsible for.. If you feel recompiling from the repo is too much of a 
hassle, you can either upgrade your OS, or ask Ubuntu to provide up to date 
PowerDNS packages.

*   I’m writing about 10 seconds install from .deb package, so it is mostly 
question of time which I’m trying to save of my work.   Also wrote below that 
recompiling is doable and even seen library/dependency errors I solved it and 
cooked 1.5.2 DNSDIST. So jumped one version 1.4->1.5.2. 
*   The Ubuntu 18.x is providing by default one package of DNSDIST 1.2, 
which is too old. Also required DoH support starts from 1.4 version.

 

DNSDist 1.5 is End Of Life.

For DoH, if you need to support multiple hostnames on the same dnsdist 
instance, I would try with a single cert with multiple SANs. DNSdist should 
serve it well, the clients should accept it. If it's still an issue in a recent 
and support dnsdist version, please show us your config, the full cert to help 
debugging.

*   Ok, I’m still doing my upgrade jumps to latest 1.8 DNSDIST and then 
test with this version.  Having multiple SANs in single cert looks like good 
advice for me , will try it ! but is it supported with CertBot to issue such 
combo cert ?

 

There is no MySQL in dnsdist, so not sure what you try to do there?

*   I wrote in message below: “Every version jump requires sometimes adjust 
the conf file or MySQL tables (backend for PDNS-AUTH), as per Documented guides 
(version upgrade guides).”  

That means I have on server full pack of DNS: dnsdist + pdns-auth with mysql 
backend and also pdns-recursor and pdns-tools, on top of it pdns-admin Web UI 
and MariaDB. So all those packages need to upgrade step by step to latest 
stable releases.

 

If you want to update your dnsservers, which should be running only the dns 
infra and nothing else, and thus should be easily upgradeable, I would 
recommend:

- provision new hosts

- install Ubuntu 22.04 LTS on them

- install dnsdist 1.8 on them

>  Frank, yes it was the first option I wanted to follow… but it takes even 
> more time to build the full system from the scratch.

Also the current server needs to keep workin as it have other services running, 
not only the DNS package.

 

Regards,

Alex.

 

 

From: Frank @ kiwazo.be  
Sent: Thursday, October 05, 2023 9:45 PM
To: pdns-users-ml 
Cc: Alex Pavlov 
Subject: Re: [Pdns-users] PDNS repos request

 

 

On 5 Oct 2023, at 20:36, Alex Pavlov via Pdns-users 
mailto:pdns-users@mailman.powerdns.com> > 
wrote:

 

Thanks Peter,

As the ready for deployment DEB files all deleted, I have now only one way of 
recompiling binaries from sources.
I'm not telling that it is not doable, but 10 seconds install process with 
"dpkg -i..." now turns in to much longer process for me.

 

Alex, 

 

I am really sorry for your loss, but you'll have to consider the amount of time 
you'll need to manually patch every CVE which might pop up in the future, as 
your 5+ years old distribution is no longer supported.

 

On top of that, it seems you're blaming others for issues which you are 
responsible for.. If you feel recompiling from the repo is too much of a 
hassle, you can either upgrade your OS, or ask Ubuntu to provide up to date 
PowerDNS packages.






As the compiling already thrown some dependency libraries errors of mismatching 
versions... one of them h2o with libssl for enabling DoH and DoT in DNSDIST (in 
the builder.sh that you described below, as I need to add DoH & DoT). I don't 
know why those errors there and why libraries were replaced some years ago.
In genera need to say that the idea is not to have old Ubuntu and old PDNS 
releases in production, but rather use it as step-by-step version updating 
DNSDIST 1.4->1.5->1.6->1.7->1.8 and same with PDNS from 4.2.3->4.3.2->up to 
latest stable.
Every version jump requires sometimes adjust the conf file or MySQL tables 
(backend for PDNS-AUTH), as per Documented guides (version upgrade guides).

 

Please keep one thread to one subject. You're now mixing 2, sorry 3 issues. 

 

DNSDist 1.5 is End Of Life.

 

For DoH, if you need to support multiple hostnames on the same dnsdist 
instance, I would try with a single cert with multiple SANs. DNSdist should 
serve it well, the clients should accept it. If it's still an issue in a recent 
and support dnsdist version, please show us your config, the full cert to help 
debugging.

 

There is no MySQL in dnsdist, so not sure what you try to do there?

 

If you want to update your dnsservers, which should be running only the dns 
infra and nothing else, and thus should be easily upgradeable, I would 
recommend:

 

- provision new hosts

- install Ubuntu 22.04 LTS on them

- install dnsdist 1.8 on them

 

Frank

 

 

Frank Louwers
PowerDNS Certified Consultant @ Kiwazo.be

___

Re: [Pdns-users] PDNS repos request

[Alex Pavlov via Pdns-users]

Thanks Peter,

As the ready for deployment DEB files all deleted, I have now only one way of 
recompiling binaries from sources.
I'm not telling that it is not doable, but 10 seconds install process with 
"dpkg -i..." now turns in to much longer process for me.
As the compiling already thrown some dependency libraries errors of mismatching 
versions... one of them h2o with libssl for enabling DoH and DoT in DNSDIST (in 
the builder.sh that you described below, as I need to add DoH & DoT). I don't 
know why those errors there and why libraries were replaced some years ago.
In genera need to say that the idea is not to have old Ubuntu and old PDNS 
releases in production, but rather use it as step-by-step version updating 
DNSDIST 1.4->1.5->1.6->1.7->1.8 and same with PDNS from 4.2.3->4.3.2->up to 
latest stable.
Every version jump requires sometimes adjust the conf file or MySQL tables 
(backend for PDNS-AUTH), as per Documented guides (version upgrade guides).

And here is one update I already moved to DNSDIST 1.5.2 with DoH and DoT 
enabled.
Noted one strange behavior.
After generated certs and keys with CertBot , added the line in dnsdist.conf 
like this:
addDOHLocal('IPaddress x.x.x.x, {'/etc/ssl/certs/site1.com.pem', 
'/etc/ssl/certs/site2.com.pem'}, {'/etc/ssl/private/site1.com.key', 
'/etc/ssl/private/site2.com.key'})

As seen on config I have more than one domains on one DNS server IP: site1.com 
and site2.com
So generated pairs of cert+key for ns.site1.com and for ns.site2.com.
All seems working and answering on https requests, but sometimes wrong...
So when checking for example https://ns.site1.com it gives me cert with 
ns.site2.com name.
But sometimes gives a correct cert for ns.site1 or ns.site2...

Is it fixed on newer DNSDIST versions after 1.5.2 ? Or maybe my config is wrong 
?

Regards,
Alex.

-Original Message-
From: Pdns-users  On Behalf Of Peter 
van Dijk via Pdns-users
Sent: Thursday, October 05, 2023 6:46 PM
To: All about using and deploying powerdns 
Cc: Peter van Dijk 
Subject: Re: [Pdns-users] PDNS repos request

On Tue, 2023-10-03 at 20:38 +0300, Alex Pavlov via Pdns-users wrote:
> Hello To all PDNS admins,
>  
> Recently the  older PDNS repos were deleted from official PDNS Repo 
> website.
> The distros for Ubuntu 16.x (Xenial) and 18.x (Bionic) were wiped out 
> without any link to “archives” or “old releases”.

As indicated by another reply in this thread, yes, those releases are EOL, and 
thus we do not publish packages for them.

It's easy to rebuild these packages for yourself if you really need them:

1. clone our git repo (https://github.com/PowerDNS/pdns)
2. check out the version you want
3. update submodules (git submodule update --init --recursive) 4. run 
builder/build.sh to see what arguments it supports 5. then run builder/build.sh 
with the arguments you want (for example, builder/build.sh -m recursor 
ubuntu-bionic)

Kind regards,
--
Peter van Dijk
PowerDNS.com B.V. - https://www.powerdns.com/ 
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] PDNS repos request

[Alex Pavlov via Pdns-users]

So realistically the "Expanded Security Maintenance" is free for up to 5 
machines (on one ubuntu account) ! 

For more you need to pay…. or open another account.

I have seen even Ubuntu 12.x is still installed and working on some servers, 
some companies.

A lot of reasons why it happens, starting from “this old machine never touched 
for 10 years” to “the old administrator did it, and it still works”.

Please also keep in mind that one of the method of updating is rising versions 
on current server than migrate to newer kernel/server. You cut that way with 
deleting all files (not only the repo), just because your personal opinion 
tells you what is “realistic”… it is sad. 

Also is bad that you don’t have the “archives” for old files ☹ 

So you can delete from PDNS REPO server for disable automatic installation via 
“apt” for example, but you should leave the .deb packages for manual 
installation via dpkg ! 

 

Please, need help with files. Not the discussion of personal opinions.

BTW, just a  week ago the files and Repo for Ubuntu 16.x and 18.x were on your 
server ! 

If I know you delete all on weekend up to Ubuntu 20.x , I should download all 
files immediately 

 

Hope for understanding,

If somebody have the files, please share.

Alex.

 

From: Pdns-users  On Behalf Of Laura 
Smith via Pdns-users
Sent: Wednesday, October 04, 2023 5:44 PM
To: All about using and deploying powerdns 
Cc: Laura Smith 
Subject: Re: [Pdns-users] PDNS repos request

 

Well, it does clearly say  "Once a distribution version reaches end of its 
support (5 years for Ubuntu LTS releases, ~3 years for Debian releases, etc.) 
we will stop providing packages for it"

 

Ubuntu 18.04 is not current anymore.   LTS updates stopped earlier this year.  
The only people getting updates are those on "Expanded Security Maintenance" 
(i.e. paying Ubuntu on a contract, so realistically not many people).

 

I can totally understand 

 

Sent with Proton Mail <https://proton.me/>  secure email. 

 

--- Original Message ---
On Tuesday, October 3rd, 2023 at 18:38, Alex Pavlov via Pdns-users 
mailto:pdns-users@mailman.powerdns.com> > 
wrote:




Hello To all PDNS admins,

 

Recently the  older PDNS repos were deleted from official PDNS Repo website. 

The distros for Ubuntu 16.x (Xenial) and 18.x (Bionic) were wiped out without 
any link to “archives” or “old releases”.

I can understand that releses like Ubuntu 16.x and older might be really 
outdated…. But for 18.x Ubuntu it is still so many people using it in 
production !

The options for compiling the required build or upgrade to newer Ubuntu kernel 
not always working in real world, where we have other packages/software running 

on same server or required libraries sometimes in conflict with other versions. 
– this is explanation to those who have “smart advices” install everyrthing on 
newer/supported server version.

 

Asking for help all PDNS society to share the deleted Ubuntu 18.x Bionic 
packages with me  (need all versions of pdns, pdns-backend, pdns-recursor, 
dnsdist, pdns-tools)

If somebody have it in files saved, share it please in any reasonable way like: 
FTP, MEGA downloads, or any other file sharing service.

 

Thank you,

Alex.

Contact to: ad...@livas.lv <mailto:ad...@livas.lv> 

 

 

 

 

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] PDNS repos request

[Alex Pavlov via Pdns-users]

Hello to everybody !

 

Does anybody can help me on the files below ?

Please, Ubuntu users or PDNS site administrator should have those file left on 
disk for Bionic 18.x.

 

Thank you, and hope for help…

Alex.

 

From: Alex  
Sent: Tuesday, October 03, 2023 8:38 PM
To: 'pdns-users@mailman.powerdns.com' 
Subject: PDNS repos request

 

Hello To all PDNS admins,

 

Recently the  older PDNS repos were deleted from official PDNS Repo website. 

The distros for Ubuntu 16.x (Xenial) and 18.x (Bionic) were wiped out without 
any link to “archives” or “old releases”.

I can understand that releses like Ubuntu 16.x and older might be really 
outdated…. But for 18.x Ubuntu it is still so many people using it in 
production !

The options for compiling the required build or upgrade to newer Ubuntu kernel 
not always working in real world, where we have other packages/software running 

on same server or required libraries sometimes in conflict with other versions. 
– this is explanation to those who have “smart advices” install everyrthing on 
newer/supported server version.

 

Asking for help all PDNS society to share the deleted Ubuntu 18.x Bionic 
packages with me  (need all versions of pdns, pdns-backend, pdns-recursor, 
dnsdist, pdns-tools)

If somebody have it in files saved, share it please in any reasonable way like: 
FTP, MEGA downloads, or any other file sharing service.

 

Thank you,

Alex.

Contact to: ad...@livas.lv  

 

 

 

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

[Pdns-users] PDNS repos request

[Alex Pavlov via Pdns-users]

Hello To all PDNS admins,

 

Recently the  older PDNS repos were deleted from official PDNS Repo website. 

The distros for Ubuntu 16.x (Xenial) and 18.x (Bionic) were wiped out without 
any link to “archives” or “old releases”.

I can understand that releses like Ubuntu 16.x and older might be really 
outdated…. But for 18.x Ubuntu it is still so many people using it in 
production !

The options for compiling the required build or upgrade to newer Ubuntu kernel 
not always working in real world, where we have other packages/software running 

on same server or required libraries sometimes in conflict with other versions. 
– this is explanation to those who have “smart advices” install everyrthing on 
newer/supported server version.

 

Asking for help all PDNS society to share the deleted Ubuntu 18.x Bionic 
packages with me  (need all versions of pdns, pdns-backend, pdns-recursor, 
dnsdist, pdns-tools)

If somebody have it in files saved, share it please in any reasonable way like: 
FTP, MEGA downloads, or any other file sharing service.

 

Thank you,

Alex.

Contact to: ad...@livas.lv  

 

 

 

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] Master slave replication

[Alex Pavlov]

Hi Donald!

 

This is how it works on my setup. I run MariaDB as Generic-MySQL mode
"gmysql" in PowerDNS.

In pdns.conf should add:

launch=gmysql

gmysql-host=localhost

gmysql-dbname=powerdns

gmysql-user=powerdns_user

gmysql-password=powerdns_password

gmysql-dnssec=yes

 

Now go to MySQL settings on MASTER 192.168.0.1 (where slave will be
192.168.0.2):

#Binlog should be in ROW or MIXED format.

# Login to MySQL and set in mysql line:

mysql -u root -p

mysql> SET GLOBAL binlog_format = 'ROW';

# OR

mysql> SET GLOBAL binlog_format = 'MIXED'

mysql>quit

#

# Edit your  /etc/mysql/my.cnf  file

nano /etc/mysql/my.cnf

#

[mariadb]

log-bin = mysql-bin

bind-address=0.0.0.0  /this allows to listen from any IP, ETH ports and
Loopback

server_id=1

log-basename=master1

skip-networking=0

 

# at mysql prompt enter:

mysql> GRANT REPLICATION SLAVE ON *.* TO 'replication_user'@'slave_host'
IDENTIFIED BY 'password'; 

FLUSH PRIVILEGES;

#

# or enter alternative commands

GRANT REPLICATION SLAVE ON *.* TO replication_user;

GRANT ALL PRIVILEGES ON *.* TO 'replication_user'@'192.168.0.2' IDENTIFIED
BY 'password' WITH GRANT OPTION;

#

#To check replication status:

SHOW SLAVE STATUS \G

#

### Now, allow 127.0.0.1, and slave SQL 192.168.0.2 ###

iptables -A INPUT -p tcp -s 127.0.0.1 --dport 3306 -j ACCEPT

iptables -A INPUT -p tcp -s 192.168.0.2 --dport 3306 -j ACCEPT

## Block all other connections to 3306 ##

iptables -A INPUT -p tcp --dport 3306 -j DROP

#Save iptables

sudo iptables-save > /etc/iptables/rules.v4

#

service mysql restart

 

###The Slave settings 192.168.0.2 where maters is 192.168.0.1

#

#Now we head over to the Slave. Open the /etc/mysql/my.cnf file and add the
following at the bottom:

[mariadb]

server-id = 2

bind-address=0.0.0.0

#issue sql restart

service mysql restart

#

# Login MySQL

mysql -u root -p

 

mysql > CHANGE MASTER TO master_host="192.168.0.1",
master_user="replication_user", master_password="password"
master_use_gtid=slave_pos;

#Start slave replication:

START SLAVE;

#To check replication status:

SHOW SLAVE STATUS;

 

# alternatively you can start replication with the following command from
client (192.168.0.2) to connect to 192.168.0.1:3306, enter:

>mysql -u replication_user -h 192.168.0.1 -P 3306 -p pasword

#

 

Regards

Alex.

From: Pdns-users [mailto:pdns-users-boun...@mailman.powerdns.com] On Behalf
Of Donald Jayawardena
Sent: Monday, December 18, 2017 8:52 AM
To: pdns-users@mailman.powerdns.com
Subject: [Pdns-users] Master slave replication

 

Hi,

 

I have an issue replicating data through powerdns on two mysql databases.

 

I could replicate data when I update data manually on the master. But data
does not get thorugh to slave if I use powerdns (using curl) to update slave
data records from the master.

 

The error says:

 

Could not execute Delete_rows event on table powerdns.records; Can't find
record in 'records', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND;
the event's master log mysql-bin.01, end_log_pos 1655

 

Please let me know if any solution for this.

 

Donald Jayawardena

 

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] PowerDNS Recursor 4.0.8 Available!

[Alex Pavlov]

Hello Erik

I have installed 2-3 weeks ago version 4.1.0-rc3. Which seems higher than 4.0.8.
Does it require any actions from my side ? 

Regards
Alex.
-Original Message-
From: Pdns-users [mailto:pdns-users-boun...@mailman.powerdns.com] On Behalf Of 
Erik Winkels
Sent: Monday, December 11, 2017 2:34 PM
To: pdns-annou...@mailman.powerdns.com; pdns-...@mailman.powerdns.com; 
pdns-users@mailman.powerdns.com
Subject: [Pdns-users] PowerDNS Recursor 4.0.8 Available!

Hello everyone,

Today we release PowerDNS Recursor 4.0.8.

This release contains a fix for the following security advisory:

- PowerDNS Security Advisory 2017-08: Crafted CNAME answer can cause a denial 
of service (CVE-2017-15120)[5]

The full changelog is here[1].

The tarball is available on downloads.powerdns.com[2] (signature[3]) and 
packages for CentOS 6 and 7, Debian Jessie and Stretch, Ubuntu Artful, Trusty, 
Xenial and Zesty are available from https://repo.powerdns.com.

Please send us all feedback and issues you might have via the mailinglist, or 
in case of a bug, via GitHub[4].

1 - https://doc.powerdns.com/recursor/changelog/4.0.html#powerdns-recursor-4-0-8
2 - https://downloads.powerdns.com/releases/pdns-recursor-4.0.8.tar.bz2
3 - https://downloads.powerdns.com/releases/pdns-recursor-4.0.8.tar.bz2.sig
4 - https://github.com/PowerDNS/pdns/issues/new
5 - 
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2017-08.html

--
Erik Winkels
PowerDNS.COM BV -- https://www.powerdns.com

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] API functionality with ldap backend in 4.1.0

[Alex Pavlov]

Hello !

If you really need LDAP as backend, I can't advice anything but don't see 
benefits of using LDAP over GMYSQL.
In my case I use Generic-MySQL type of backend with MariaDB SQL 10.2. 
Authoritative servers (Primary, Secondary) synchronized with SQL "native" 
replication.
Install apache2+php5+PEAR and PowerAdmin from there 
http://www.poweradmin.org/index.html

This will 100% work (tested on ESXi6.0, with Ubuntu 14.04LTS) and you can 
add/delete/edit zones and records in web interface.
It also supports DNSSEC.

BR,
Alex.
-Original Message-
From: Pdns-users [mailto:pdns-users-boun...@mailman.powerdns.com] On Behalf Of 
Dirk Bartley
Sent: Monday, December 04, 2017 6:47 PM
To: pdns-users@mailman.powerdns.com
Subject: [Pdns-users] API functionality with ldap backend in 4.1.0

Greetings

I have a testing vm installed and functional and answering dns queries.  pdns-
4.1.0   I installed PowerDNS-Admin as a possible add on interface and it 
appears the API calls for stats and configuration are working, but not the 
other api calls for zones and hosts.

The ldap data is the output of pdns-zone2ldap.  I did get the schema into 
openldap with the additional pdns-domaininfo schema.  For one zone for testing 
purpose I added data for PdnsDomain to see if I could get it to work.

curl -v -H 'X-API-Key: abc' http://127.0.0.1:8081/api/v1/servers/localhost/zones

returns an empty set of zones.  I have watched the slapd logs and noticed that 
when the above curl command is run, powerdns connects to slapd, but performs no 
searches.

So my question is should the api functionality correctly function with ldap 
backend, or is this still a work in process.  Is there something more I need to 
do.


Thank you very kindly in advance for your assistance.


Dirk





Aside:  It took a bit of effort to create the ldif files to load the schemas in 
the openldap.  I could provide the ones I created for inclusion if desired.



--
This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users