Hi,
I can confirm this work around works:
It looks like there is a bug in the DNSSEC implementation. I can resolve this
name on the current master branch with the `dnssec=off` setting.
If it helps, I also came across the same issue when resolving names on
secureserver.net - specifically
Hi,
IIRC, mine is 64k.
Cheers,
Tom.
On 16 May 2016 16:23:27 CEST, Thorvald Hallvardsson
wrote:
>Hi,
>
>At the moment the content field in my database is varchar(255) so I
>will
>have to change that first and test it.
>
>Thank you for your response and help!
Hi,
At the moment the content field in my database is varchar(255) so I will
have to change that first and test it.
Thank you for your response and help!
Regards,
TH
On 16 May 2016 at 14:55, Thomas Hager wrote:
> On Mon, 2016-05-16 at 14:29 +0100, Thorvald Hallvardsson
On Mon, 2016-05-16 at 14:29 +0100, Thorvald Hallvardsson wrote:
> Hi guys,
Hi Thorvald,
> Can someone let me know correct way of configure entries in PowerDNS
> database to get them work for the domain keys which are quite long
> and exceeds 255 characters ?
Just store it in the database as a
Hi guys,
Can someone let me know correct way of configure entries in PowerDNS
database to get them work for the domain keys which are quite long and
exceeds 255 characters ?
In theory I should just be able to do something like:
seaparator._domainkey.domainame.com IN TXT "v=dkim1; k=rsa; p=long
On Mon, May 16, 2016 at 04:25:08AM -0700, geohei wrote:
> Yes, 3.3.
> But "prevent-self-notification=yes" still triggers self notifications.
> Why were they implemented at a first place?
It goes like this. A nameserver figures out who claims to be authoritative
for a domain, and then gathers the
Yes, 3.3.
But "prevent-self-notification=yes" still triggers self notifications.
Why were they implemented at a first place?
I don't see the usefullness.
--
View this message in context:
http://powerdns.13854.n7.nabble.com/why-self-notification-tp12287p12289.html
Sent from the PowerDNS mailing
Hi.
PowerDNS newbie question (sorry). syslog shows (anonymized):
May 15 19:51:46 gany pdns[30950]: 1 domain for which we are master needs
notifications
May 15 19:51:46 gany pdns[30950]: Queued notification of domain
'ddns.mydomain.com' to 185.3.195.46
May 15 19:51:46 gany pdns[30950]: Remote