Hi everybody,
Yesterday we worked with various providers to debug a problem between
Microsoft Exchange, PowerDNS Recursor and the Microsoft Azure nameservers.
If you or your users employ Microsoft Exchange on IPv6 and see email
delivery problems to domain names hosted on Azure, this message is fo
Hello all,
Hopefully this is not too far off topic…
I’m going to start implementing DNSSEC soon as it’s past due. Most of the
online guides I’m finding deal almost exclusively with BIND as that does seem
to be the reference implementation. Are there any preferred guides for
PowerDNS? I also
Pipe backend does not support DNSSEC. Please see remotebackend if you want
to support DNSSEC using external software.
Aki
On Wed, Dec 03, 2014 at 10:57:22AM -0600, k...@rice.edu wrote:
> Have you tried the latest release 3.4.1? It does have some bug
> fixes.
>
> Regards,
> Ken
> On Wed, Dec 03
Have you tried the latest release 3.4.1? It does have some bug
fixes.
Regards,
Ken
On Wed, Dec 03, 2014 at 11:49:33AM -0500, Craig Despeaux wrote:
> ...
>
> I'm at my wit's end as to how to resolve this problem. Any suggestions as
> to things I can look at? Like I said, it works flawlessly with
I am trying to use PowerDNS for test purposes. I have the 3.3-2 versions
of pdns-server-backend-pipe and pdns-server rpms installed on el6.
I created and signed three zone files with Bind 9.10 representing the root
zone, net zone, and the domain kitchensink.net. I am using the pipe
backend for E
