<div dir="ltr">Hello,<div><br></div><div>Could your kindly provide suggestion, if PowerDNS can be used with NGINX reverse proxy. If yes, what are the benefits or any limitations.</div><div><br></div><div>Thank You, kindly advice. </div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Regards,<div>Satya Prakash Sharma</div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 18, 2018 at 5:30 PM <<a href="mailto:pdns-users-request@mailman.powerdns.com">pdns-users-request@mailman.powerdns.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Pdns-users mailing list submissions to<br>
<a href="mailto:pdns-users@mailman.powerdns.com" target="_blank">pdns-users@mailman.powerdns.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mailman.powerdns.com/mailman/listinfo/pdns-users" rel="noreferrer" target="_blank">https://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:pdns-users-request@mailman.powerdns.com" target="_blank">pdns-users-request@mailman.powerdns.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:pdns-users-owner@mailman.powerdns.com" target="_blank">pdns-users-owner@mailman.powerdns.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Pdns-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. PowerDNS Authoritative Server v4.2.0-alpha1 Available!<br>
(Erik Winkels)<br>
2. Re: PDNS and Isilon Smartconnect Delegation (Ian Easter)<br>
3. Re: PDNS and Isilon Smartconnect Delegation (bert hubert)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 17 Dec 2018 14:49:24 +0100 (CET)<br>
From: Erik Winkels <<a href="mailto:erik.winkels@open-xchange.com" target="_blank">erik.winkels@open-xchange.com</a>><br>
To: <a href="mailto:pdns-announce@mailman.powerdns.com" target="_blank">pdns-announce@mailman.powerdns.com</a>, <a href="mailto:pdns-dev@mailman.powerdns.com" target="_blank">pdns-dev@mailman.powerdns.com</a>,<br>
<a href="mailto:pdns-users@mailman.powerdns.com" target="_blank">pdns-users@mailman.powerdns.com</a><br>
Subject: [Pdns-users] PowerDNS Authoritative Server v4.2.0-alpha1<br>
Available!<br>
Message-ID:<br>
<<a href="mailto:401849309.2020.1545054564633@appsuite-guard.open-xchange.com" target="_blank">401849309.2020.1545054564633@appsuite-guard.open-xchange.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
(From: <a href="https://blog.powerdns.com/2018/12/14/powerdns-authoritative-server-4-2-0-alpha1-lua-records-ixfrdist-swagger/" rel="noreferrer" target="_blank">https://blog.powerdns.com/2018/12/14/powerdns-authoritative-server-4-2-0-alpha1-lua-records-ixfrdist-swagger/</a> )<br>
<br>
We’re proud to release the first alpha version of the PowerDNS Authoritative Server 4.2 series. While some users have already deployed this version straight from our package builders[1] or master repositories[2], this is still a very fresh release.<br>
<br>
4.2 represents almost a year of development over 4.1 and contains some major new features and improvements, while deprecating some functionality you may have been relying on (autoserial, for example).<br>
<br>
LUA RECORDS<br>
<br>
An important new feature is the support for Lua Records[3], which make the following possible, from any backend (even BIND!):<br>
<br>
@ IN LUA A "ifportup(443, {'52.48.64.3', '45.55.10.200'})"<br>
<br>
This will poll the named IP addresses (in the background) and only serve up hosts that are available. Far more powerful constructs are possible, for example to pick servers from regional pools close to the user, except if all servers in that pool are down. It is also possible to do traffic engineering based on subnets or AS numbers. A simple example:<br>
<br>
@ IN LUA A ( "ifportup(443, {'52.48.64.3', '45.55.10.200'}, "<br>
"{selector='closest'})<br>
<br>
For more about this feature, please head to the documentation: <a href="https://doc.powerdns.com/authoritative/lua-records/index.html" rel="noreferrer" target="_blank">https://doc.powerdns.com/authoritative/lua-records/index.html</a><br>
<br>
DEPRECATIONS<br>
<br>
4.2 will see the removal of the poorly documented ‘autoserial’ feature. This removal decision was not taken lightly but as noted[4], its removal allows us to fix other bugs. Autoserial was holding us back. We realise it is no fun when a feature disappears, but since Authoritative Server 4.1 is still around, you can still use that if you require ‘autoserial’.<br>
<br>
Following RFC6986 and anticipating the publication of Algorithm Implementation Requirements and Usage Guidance for DNSSEC, support for both ECC-GOST signing and GOST DS digests have been removed.<br>
<br>
IXFRDIST<br>
<br>
A new tool ixfrdist[5] transfers zones from an authoritative server and re-serves these zones over AXFR and IXFR. It checks the SOA serial for all configured domains and downloads new versions to disk. This makes it possible for hundreds of PowerDNS Recursors (or authoritative servers) to slave an (RPZ) zone from a single server, without overwhelming providers like our friends over at Spamhaus/Deteque[6] and Farsight[7].<br>
<br>
Inspired by our Open-Xchange[8] colleagues our API is now described by a Swagger[9] spec!<br>
<br>
LOG-LOG HISTOGRAMS<br>
<br>
Over at PowerDNS, we love statistics. Making sense of DNS performance is not that easy however – most queries get answered very quickly, but it is the outliers that determine how users “experience the internet”. It turns out that log-log histograms make it possible to fully capture the quality of a DNS service. As explained in this blog post[10], PowerDNS now comes with tooling to make such histograms: <a href="https://powerdnsblog.files.wordpress.com/2017/11/log-full-avg.png" rel="noreferrer" target="_blank">https://powerdnsblog.files.wordpress.com/2017/11/log-full-avg.png</a><br>
<br>
Note that this tooling is not specific to PowerDNS Authoritative or even PowerDNS: it will analyse any PCAP file with DNS in there.<br>
<br>
IMPROVEMENTS, FIXES<br>
<br>
- Threads now set their name[11]<br>
- Massive speedup in record deduplication code, which was causing problems when serving very large responses[12]<br>
- Support for OpenSSL 1.1.1’s ed25519 and ed448[13]<br>
- Enhance query-logging with timing for MySQL, PostgreSQL and SQLite. Slow databases are a frequent cause for bad PowerDNS performance. This logging delivers detail on how slow/fast your backend is for specific queries[14].<br>
<br>
MUCH MORE<br>
<br>
The changelog lists many more improvements and bug fixes: <a href="https://doc.powerdns.com/authoritative/changelog/4.2.html" rel="noreferrer" target="_blank">https://doc.powerdns.com/authoritative/changelog/4.2.html</a><br>
<br>
Please also see the recent "Important Changes in PowerDNS Authoritative Server 4.2.0"[15] and "Enabling continuous fuzzing of PowerDNS products"[16] blog posts.<br>
<br>
The tarball is available on <a href="http://downloads.powerdns.com" rel="noreferrer" target="_blank">downloads.powerdns.com</a>[17] (signature[18]) and packages for CentOS 6 and 7, Debian Jessie and Stretch, Ubuntu Bionic, Trusty and Xenial are available from <a href="https://repo.powerdns.com" rel="noreferrer" target="_blank">https://repo.powerdns.com</a><br>
<br>
Please send us all feedback and issues you might have via the mailing list, or in case of a bug, via GitHub[19].<br>
<br>
1 - <a href="https://builder.powerdns.com/" rel="noreferrer" target="_blank">https://builder.powerdns.com/</a><br>
2 - <a href="https://repo.powerdns.com/" rel="noreferrer" target="_blank">https://repo.powerdns.com/</a><br>
3 - <a href="https://blog.powerdns.com/2017/12/15/powerdns-authoritative-lua-records/" rel="noreferrer" target="_blank">https://blog.powerdns.com/2017/12/15/powerdns-authoritative-lua-records/</a><br>
4 - <a href="https://blog.powerdns.com/2018/12/07/important-changes-in-powerdns-authoritative-server-4-2-0/" rel="noreferrer" target="_blank">https://blog.powerdns.com/2018/12/07/important-changes-in-powerdns-authoritative-server-4-2-0/</a><br>
5 - <a href="https://doc.powerdns.com/authoritative/manpages/ixfrdist.1.html" rel="noreferrer" target="_blank">https://doc.powerdns.com/authoritative/manpages/ixfrdist.1.html</a><br>
6 - <a href="https://www.deteque.com/" rel="noreferrer" target="_blank">https://www.deteque.com/</a><br>
7 - <a href="https://www.farsightsecurity.com/" rel="noreferrer" target="_blank">https://www.farsightsecurity.com/</a><br>
8 - <a href="https://www.open-xchange.com/" rel="noreferrer" target="_blank">https://www.open-xchange.com/</a><br>
9 - <a href="https://swagger.io/" rel="noreferrer" target="_blank">https://swagger.io/</a><br>
10 - <a href="https://blog.powerdns.com/2017/11/02/dns-performance-metrics-the-logarithmic-percentile-histogram/" rel="noreferrer" target="_blank">https://blog.powerdns.com/2017/11/02/dns-performance-metrics-the-logarithmic-percentile-histogram/</a><br>
11 - <a href="https://github.com/PowerDNS/pdns/pull/6997" rel="noreferrer" target="_blank">https://github.com/PowerDNS/pdns/pull/6997</a><br>
12 - <a href="https://github.com/PowerDNS/pdns/pull/6730" rel="noreferrer" target="_blank">https://github.com/PowerDNS/pdns/pull/6730</a><br>
13 - <a href="https://github.com/PowerDNS/pdns/pull/6910" rel="noreferrer" target="_blank">https://github.com/PowerDNS/pdns/pull/6910</a><br>
14 - <a href="https://github.com/PowerDNS/pdns/pull/6975" rel="noreferrer" target="_blank">https://github.com/PowerDNS/pdns/pull/6975</a><br>
15 - <a href="https://blog.powerdns.com/2018/12/07/important-changes-in-powerdns-authoritative-server-4-2-0/" rel="noreferrer" target="_blank">https://blog.powerdns.com/2018/12/07/important-changes-in-powerdns-authoritative-server-4-2-0/</a><br>
16 - <a href="https://blog.powerdns.com/2018/12/12/enabling-continuous-fuzzing-of-powerdns-products/" rel="noreferrer" target="_blank">https://blog.powerdns.com/2018/12/12/enabling-continuous-fuzzing-of-powerdns-products/</a><br>
17 - <a href="https://downloads.powerdns.com/releases/pdns-4.2.0-alpha1.tar.bz2" rel="noreferrer" target="_blank">https://downloads.powerdns.com/releases/pdns-4.2.0-alpha1.tar.bz2</a><br>
18 - <a href="https://downloads.powerdns.com/releases/pdns-4.2.0-alpha1.tar.bz2.sig" rel="noreferrer" target="_blank">https://downloads.powerdns.com/releases/pdns-4.2.0-alpha1.tar.bz2.sig</a><br>
19 - <a href="https://github.com/PowerDNS/pdns/issues/new" rel="noreferrer" target="_blank">https://github.com/PowerDNS/pdns/issues/new</a><br>
-- <br>
Erik Winkels<br>
PowerDNS.COM BV -- <a href="https://www.powerdns.com" rel="noreferrer" target="_blank">https://www.powerdns.com</a><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 475 bytes<br>
Desc: not available<br>
URL: <<a href="http://mailman.powerdns.com/pipermail/pdns-users/attachments/20181217/4826ed56/attachment-0001.sig" rel="noreferrer" target="_blank">http://mailman.powerdns.com/pipermail/pdns-users/attachments/20181217/4826ed56/attachment-0001.sig</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 17 Dec 2018 10:51:17 -0500<br>
From: Ian Easter <<a href="mailto:ieaster@telvue.com" target="_blank">ieaster@telvue.com</a>><br>
To: <a href="mailto:bert.hubert@powerdns.com" target="_blank">bert.hubert@powerdns.com</a><br>
Cc: <a href="mailto:pdns-users@mailman.powerdns.com" target="_blank">pdns-users@mailman.powerdns.com</a><br>
Subject: Re: [Pdns-users] PDNS and Isilon Smartconnect Delegation<br>
Message-ID:<br>
<<a href="mailto:CANrihcJs9KswD_SqDvOF%2BQnPP5b5n-UNDBJ1U8XfN58fKO1GGQ@mail.gmail.com" target="_blank">CANrihcJs9KswD_SqDvOF+QnPP5b5n-UNDBJ1U8XfN58fKO1GGQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Morning Bert<br>
<br>
Thank you for your help last week with my Isilon issue. As well as thank<br>
you to ph1.<br>
<br>
Isilon round robin issue ended up being related to network configuration<br>
for the guest machines. Once I cleared that up, the PDNS Recursor Forward<br>
Zone configuration worked without a hitch.<br>
<br>
For closure, and anyone else that happens across this thread that is<br>
migrating from BIND, I figured I would follow up to maybe be a source of<br>
assistance.<br>
<br>
Your SmartConnect Zone(Domain) name will be added in the PDNS Recursor<br>
configuration file and point to your SmartConnect service IP.<br>
<br>
As an example:<br>
* forward-zones=isilon-mgmt.teve.inc=10.1.1.100,<br>
isilon-nfs.teve.inc=192.168.100.100*<br>
<br>
*Thank you,*<br>
*Ian Easter*<br>
<br>
<br>
<br>
<br>
On Thu, Dec 13, 2018 at 2:42 PM bert hubert <<a href="mailto:bert.hubert@powerdns.com" target="_blank">bert.hubert@powerdns.com</a>><br>
wrote:<br>
<br>
> On Thu, Dec 13, 2018 at 02:17:23PM -0500, Ian Easter wrote:<br>
> > Recently switched from BIND9.7.3 to PowerDNS and working through some<br>
> > adjustments.<br>
> ><br>
> > We previously followed the guidelines for DNS based on the documentation:<br>
> ><br>
> <a href="https://www.emc.com/collateral/hardware/white-papers/h8316-wp-smartconnect.pdf" rel="noreferrer" target="_blank">https://www.emc.com/collateral/hardware/white-papers/h8316-wp-smartconnect.pdf</a><br>
> > and everything worked without issue.<br>
><br>
> Hi Ian,<br>
><br>
> We happen to have a quorum of people with Isilon expertise present on our<br>
> IRC channel right now. Could you drop by?<br>
> <a href="https://www.powerdns.com/opensource.html" rel="noreferrer" target="_blank">https://www.powerdns.com/opensource.html</a><br>
> has a link to a web client.<br>
><br>
> Thanks!<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mailman.powerdns.com/pipermail/pdns-users/attachments/20181217/0e8d33ad/attachment-0001.html" rel="noreferrer" target="_blank">http://mailman.powerdns.com/pipermail/pdns-users/attachments/20181217/0e8d33ad/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 17 Dec 2018 17:14:21 +0100<br>
From: bert hubert <<a href="mailto:bert.hubert@powerdns.com" target="_blank">bert.hubert@powerdns.com</a>><br>
To: Ian Easter <<a href="mailto:ieaster@telvue.com" target="_blank">ieaster@telvue.com</a>><br>
Cc: <a href="mailto:pdns-users@mailman.powerdns.com" target="_blank">pdns-users@mailman.powerdns.com</a><br>
Subject: Re: [Pdns-users] PDNS and Isilon Smartconnect Delegation<br>
Message-ID: <<a href="mailto:20181217161421.GA24011@server.ds9a.nl" target="_blank">20181217161421.GA24011@server.ds9a.nl</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On Mon, Dec 17, 2018 at 10:51:17AM -0500, Ian Easter wrote:<br>
> Isilon round robin issue ended up being related to network configuration<br>
> for the guest machines. Once I cleared that up, the PDNS Recursor Forward<br>
> Zone configuration worked without a hitch.<br>
<br>
Thank you so much for reporting back on the resolution of this issue,<br>
most appreciated!<br>
<br>
Bert<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Pdns-users mailing list<br>
<a href="mailto:Pdns-users@mailman.powerdns.com" target="_blank">Pdns-users@mailman.powerdns.com</a><br>
<a href="https://mailman.powerdns.com/mailman/listinfo/pdns-users" rel="noreferrer" target="_blank">https://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Pdns-users Digest, Vol 191, Issue 14<br>
*******************************************<br>
</blockquote></div>