hecker, as it cannot determine that the second
> row is a continuation of the pub key with the row proceeding it. I'm still
> struggling with appending the pubkey to the previous record.
>
>> On Wed, Mar 20, 2019 at 2:14 PM Steve Atkins wrote:
>>
>>
>> > On M
> On Mar 20, 2019, at 5:49 PM, Jonathan Reed wrote:
>
> Hi,
>
> I'm running an old version of pdns where my backend record length for
> "records.name" is still varchar(255). I've read it's been extended to 64k.
> However I'm trying to insert a 400 character dkim value in it by adding
> mult
> On Jun 29, 2018, at 2:23 PM, Anthony Eden wrote:
>
> Hello everyone,
>
> I am considering moving some or all of DNSimple's authoritative DNS service
> back over to PowerDNS within the next 6 months, but before I do so, I'm
> hoping to get in touch with one or more folks from the PowerDNS co
> On Feb 6, 2018, at 12:29 AM, Sander Smeenk via Pdns-users
> wrote:
>
> Quoting Sander Smeenk via Pdns-users (pdns-users@mailman.powerdns.com):
>
>> Could this not be handled by some logic that compares the serial
>> to the last-rectified serial and rectifies it on the fly when needed?
>> Thi
> On Nov 23, 2017, at 12:27 PM, Eric Beck wrote:
>
> Greetings,
>
> Issue: When using the API, and gmysql backend, the change_date column is
> not updated.
>
> Ok, I know this subject as come up before, and from what I read there
> seemed to be a consensus at PowerDNS development to leave it a
> On Aug 13, 2017, at 11:10 AM, Brian Candler wrote:
>
> On 13/08/2017 18:40, Curtis Maurand wrote:
>> I have a ton of websites running letsencrypt. That's great, I like it, but
>> starting in April they started requiring CAA records.
>
> Citation needed?
>
> https://letsencrypt.org/docs/caa
> On Aug 13, 2017, at 10:40 AM, Curtis Maurand wrote:
>
> Hello,
> I have a ton of websites running letsencrypt. That's great, I like it, but
> starting in April they started requiring CAA records. A new record to be
> sure and, according to the docs, it is supported. There is nothing in th
> On Apr 3, 2017, at 8:44 AM, j...@archer.net wrote:
>
> Hi All…
>
> I’m in the process of deploying a pdns cluster and am going to have 4 dns
> servers, each with their own installation of Postgres. These will be standby
> servers from a master version of Postgres, and on the master is where
> On Mar 5, 2017, at 9:22 AM, NoBloat wrote:
>
> Wow, only a few days into trying pdns and I'm getting hounded about buying
> support and being given a hard time about wanting to remain anonymous which
> most anyone should want to anyhow.
>
> Yes, DNS records are public but I don't have to s
> On Aug 18, 2016, at 8:11 AM, David wrote:
>
> On 2016-08-18 8:37 AM, Pieter Lexis wrote:
>> Hi Michael,
>>
>> On Thu, 18 Aug 2016 14:20:25 +
>> Michael wrote:
>>
>>> Last week I updated to Ubuntu 16.04. So I have a new Postfix version
>>> (3.1.0) as well as a new pdns_recursor version (
7;m planning on building a
test server and loading them up to see if I can replicate the problem. If I get
a test case I'll share.
Cheers,
Steve
>
> Kind regards,
> --
> Peter van Dijk
> PowerDNS.COM BV - https://www.powerdns.com/
>
> On 25 Mar 2016, at 4:07, Stev
pdnssec rectify-zone makes the problem go away, which fixes it for me.
It feels like there's still an underlying bug somewhere in the dnssec sql or
surrounding code, though.
Cheers,
Steve
> On Mar 24, 2016, at 7:54 PM, Steve Atkins wrote:
>
> I'm using a postgresql
I'm using a postgresql backend, and I have several zones configured to use
dnssec.
Queries for resource records that exist work perfectly. The verisign online
checker says my dnssec is good.
If I query for a resource record that doesn't exist without using dnssec -
either one where there are n
13 matches
Mail list logo
