Hi Andrey,
On Fri, 2023-12-15 at 18:47 +0300, Andrey Sedletsky via Pdns-users
wrote:
> Good day!
> Andrey Sedletsky, PJSC MGTS (Moscow City Telephone Network)
> One of our clients contacted us with a problem about the inability to
> resolve the resources of their zone through the DNS servers (pdns
Hello DNS enthusiasts and other developers,
After four earlier successful and packed DNS devrooms, we are happy to
announce a half-day DNS devroom at FOSDEM 2024.
As with the previous events, we hope to host talks anywhere from
hardcore protocol stuff, to practical sessions for programmers that a
Hi,
On Mon, 2022-11-28 at 19:12 +0100, Andrea Biancalani via Pdns-users
wrote:
> is there a way to be noticed on master's GUI (or slave) of
> zombie/dead
> zones in superslave server?
There is no option like that, as noted in the docs[1]:
=== Quote ===
Removal of zones provisioned using the aut
ver.
Cheers,
Pieter
1 - https://doc.powerdns.com/authoritative/http-api/cryptokey.html
2 - https://doc.powerdns.com/authoritative/http-api/metadata.html
3 -
https://doc.powerdns.com/authoritative/domainmetadata.html#extra-metadata
--
Pieter Lexis
E: pie...@plexis.eu
42AC5720-484A-11EC-843D-F8C6064ABEF7._domainkey.kartaak.com [DATA]
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
about DNSSEC validation or the second if you don't
care about it.
Cheers,
Pieter
1 - https://doc.powerdns.com/recursor/dnssec.html#negative-trust-anchors
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing
en do a dig
that fails and check the recursors' log. It will hint as to what is
happening.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
in ALIAS server2.somedomain
Like a CNAME, only one ALIAS per name is allowed. It looks like the
documentation[1] does not make this clear. Can you file a ticket for
this[2]?
Cheers,
Pieter
1 - https://doc.powerdns.com/authoritative/guides/alias.html
2 - https://github.com/PowerDNS/pdns/issues
gt; name='testdomain.eu'
> 14 Reset stmt
This looks good!
> After restaring pdns the errors have gone away, but seems strange to me.
> Where could this errors come from? MySQL connection timeouts maybe? But
> timeouts would result in the logs of mys
0:19 localhost pdns_recursor: Unable to load Lua script from
> '/etc/pdns-recursor/lua.conf': [string "chunk"]:1: ')' expected near '='
did you try
protobufServer('192.0.2.1:3444')
with the correct IPs and port?
If you need to config more, it c
ery-local-address`, never realizing this side-effect.
I can recommend reading the upgrade guide[1] every upgrade, things like
this are mentioned there.
Cheers,
Pieter
1 - https://docs.powerdns.com/recursor/upgrade.html
--
Pieter Lexis
PowerDNS.COM BV -- https:/
t (although we try to get the records, but there simply are
none).
I can **highly** recommend turning on IPv4 outgoing in addition to IPv6
with query-local-address=::,0.0.0.0. IPv6-only resolving simply does not
work on the current internet.
> Would
8e59547a8779f7>
I can't replicate this on master. What version of PowerDNS Recursor are
you using and what is the full configuration?
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users
January
2013, is out of support for several years(!) and suffers from from
several know security vulnerabilities. Please upgrade ASAP.
If you mis-typed and are using 4.2, ALLOW-AXFR-FROM metadata is
supported PowerDNS Authoritative Server 3.4.2 onward.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS
'IXFR' metadata is set to '1'.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
rdns.com/
3 - https://doc.powerdns.com/authoritative/upgrading.html
4 - https://dnsviz.net/d/opensourceserver.io/YJTycg/dnssec/
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
is not published as
> DNSKEY.
Correct!
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
Rset).
>> I've deleted the necessary A records, yet keep running into the same issue.
Please show us _how_ you did the removal, any messages or responses, the
zone contents and any other relevant information. Without this, offering
any suggestions is shooting in the dark.
Cheers,
re using the BIND backend, you'll need to edit the bind config
file and run
pdns_control rediscover
1 -
https://docs.powerdns.com/authoritative/modes-of-operation.html#native-replication
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- ht
version of
PowerDNS. This is on our wish-list, but no work has been done there, as
all known ALIAS installations use the AXFR method.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mai
l.
Cheers,
Pieter
1 - https://github.com/PowerDNS/pdns/issues/3838
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
> Error resolving for crazyforprint.nl ALIAS 81159.bodis.com over UDP, A-record
> query returned Query Refused, returning SERVFAIL
Your upstream resolver (in the 'resolver' setting) sends REFUSED for
some reason. when it is queried for 81159.bodis.com. You'll have to find
out why t
Hi Steffen,
On 3/9/21 1:35 PM, Steffan via Pdns-users wrote:
> This domain is not using a A record
>
> But a ALIAS and CNAME
>
> Is that why dnssec failes?
Yes, see
https://doc.powerdns.com/authoritative/guides/alias.html#alias-and-dnssec
Cheers,
Pieter
--
Pieter Lexis
describe your set up, including the full configuration of PowerDNS
(without passwords). Can you also check what `pdnsutil check-zone
crazyforprint.nl` and `pdnsutil show-zone crazyforprint.nl` reports?
The SOA and DNSKEY responses do carry RRSIGs, which is weird though. Is
there a cache or middle box i
ll remove all Xenial repositories once it goes EOL.
There will be an announcement about this coming within a week.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
> I have one question:
>
> pdnsutil check-all-zones
>
> As we have thousands over zones, can someone advise how can we use the
> command above just to list those errors only?
No, we check all the zones and dump both warnings and errors, but
`pdnsutil check-all-zones | grep -i error` shoul
es. Hence the suggestion of cloning the
database and trying the upgrade first.
> Is that correct?
So "yes"
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
,
Pieter
1 - https://doc.powerdns.com/authoritative/appendices/EOL.html
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
sion to the version you're upgrading to. It
is mostly checking the new or changed settings, applying any schema
changes, and running `pdnsutil check-all-zones` to see if any zones have
errors.
Here's the guide: https://doc.powerdns.com/authoritative/upgrading.html
Hope this helps,
Pie
gives attackers time to spoof
answers. The auth will answer with REFUSED if the zone is not in the
database, or with an NXDOMAIN (or NODATA) when the zone exists but no
such record/type.
If this is not the answer you're looking for, please explain your
usecase in a bit more detail.
Cheers,
Pieter
in a future release? It would definitely be useful for us.
There are no plans for this. All PowerDNS daemons expect to be run under
a system supervisor like systemd or daemon(8).
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
and 4.1.
I hope this clears up the confusion.
Best regards,
Pieter
1 -
https://github.com/PowerDNS/pdns/commit/f613d2420ab805c2bc6295d1a544e278a047ee0e
2 - https://github.com/PowerDNS/pdns/pull/4547
3 - https://github.com/PowerDNS/pdns/issues/2377
--
Pieter Lexis
PowerDNS.COM
tween the different
instances? A difference might explain this, as the SOA serials in the
database and (unrelated) metadata match.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.pow
the
zone on the slave.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
pecified in
> local-address?
This is intended behaviour. The local-port setting is used for
local-address or local-ipv6 addresses without ports.
It looks like this is indeed is not documented. If you can open a GH
issue about this (or a PR with amended documentation), we'd be
grateful.
Chee
ope this clarifies it for you. If not, don't hesitate to reply to the
mailinglist.
Best regards,
Pieter
1 - https://doc.powerdns.com/authoritative/http-api/index.html
2 - https://doc.powerdns.com/authoritative/http-api/zone.html#zone
--
Pieter
re it does not lie to the
clients, the AD bit is never set [1].
I hope this clears up the confusion.
Best regards,
Pieter
1 -
https://github.com/PowerDNS/pdns/blob/dbcbb6820eab29a5da2ae51ae2321b8691fce938/pdns/pdns_recursor.cc#L1461-L1462
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdn
schema
2. Upgrade instances one by one
Best regards,
Piter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
to upgrade the
> database schema first and every server then?
The schema upgrade adds a field to the cryptokeys table and all queries
from PowerDNS ask for specific field, not all fields. So it _should_ be
safe. We do recommend testing it just to be sure :).
Best regards,
Pieter
--
Pieter Lex
Hi Vyentis,
On 3/5/20 4:45 PM, Vytenis A via Pdns-users wrote:
> Can pDNS skip those records completely? Otherwise we'd flood the logs
> with 404 errors
No it can't, but you can just send an HTTP 200 with this JSON to make
pdns not log things:
{ "result": [] }
Best re
ch address that sends more than 5 QPS.
Best regards,
Pieter
1 - https://dnsdist.org
2 - https://dnsdist.org/rules-actions.html?highlight=maxqps#MaxQPSIPRule
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing
an upcoming
version, where some tools will be available to fix the database.
In the meantime, I've fixed the help output of pdnsutil[1].
Best regards,
Pieter
1 - https://github.com/PowerDNS/pdns/pull/8420
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
signature.asc
Descript
. Can you
try to create the new key like this:
pdnsutil add-zone-key parsemail.org zsk 1024 active rsasha1-nsec3-sha1
and test if you indeed see a good KSK/ZSK split? If so, there might be
some logic missing in handling the 'automatic' upgrade from algo 5 to 7
in NSEC3 zones.
Best regard
ocs.powerdns.com/authoritative/settings.html#setting-slave-cycle-interval
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
On 9/18/19 1:55 PM, Pieter Lexis wrote:
> This is a bug, there is a PR to fix this[1], but this PR has to be
> un-conflicted and re-reviewed.
Forot the link:
1 - https://github.com/PowerDNS/pdns/pull/5595
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerd
worked around it by setting the SOA RETRY value to 1 minute, so it
> checks for a newer serial quickly after the update, just in case it was
> missed.
This is a bug, there is a PR to fix this[1], but this PR has to be
un-conflicted and re-reviewed.
Cheers,
Pieter
--
ent,ttl,prio,type,domain_id,disabled,name,auth FROM records WHERE
> disabled=0 and type=? and name=? LIMIT=5
Should be
# pdns_server --gmysql-basic-query="SELECT
content,ttl,prio,type,domain_id,disabled,name,auth FROM records WHERE
disabled=0 and type=? and name=? LIMIT=5"
Best re
any number of reasons.
If you still have this issue, I suggest checking the recursor why this
lookup failed.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
Hi Øystein,
On 5/8/19 9:50 AM, Pieter Lexis wrote:
> I can resolve p4.no without issue on 4.2.0. Can you start the recursor
> with the `trace` option set and provide the logs if it still fails?
I tested the wrong domain. p4.no indeed breaks because the auths respond
with a FORMERR plus
Hi Øystein,
On 5/8/19 9:42 AM, Øystein Viggen wrote:
> I initially discovered this when running the 4.1.x recursor release that
> had the dns flag day changes. P4 is a popular Norwegian radio station,
> so with some 50k users there were some complaints..
>
> The thing that makes me think this is
Hello Gert and Bart,
On 5/6/19 10:49 AM, Gert van Dijk wrote:
> (just wanted to comment on this, slightly unrelated part)
>
> On Mon, May 6, 2019 at 10:02 AM Bart Mortelmans wrote:
>> I actually found out because systemd was restarting the service every
>> couple of minutes. Turns out that I sho
PowerDNS Authoritative Server on an Ubuntu VM in
Azure to test the ODBC backend with MSSQL before moving that to docker
and another CI-environment.
So yes, PowerDNS runs on Azure VMs.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.pow
is sounds like your recursor is not compiled with protobuf support.
Can you show the output of `pdns_recursor --version`? Follow-up
question: what OS are you running on and did you build the recursor
yourself or did it came from a package (and if so, where did the package
come from)?
Best regards,
serve out all matching RRSIGs
regardless of algorithm.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
ovide us
your pdns.conf and the traces with non-RD forwards.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
ns the recursor will expect the upstream to do the
recursorsion, which it shouldn't do. Can you remove the '+' from the
lines and retry?
You only want to retrieve the delegations from the auth, not have the
auth do the rest of the lookups.
Cheers,
Pieter
--
Pieter Lex
tative/backends/generic-sql.html#handling-dnssec-signed-zones
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
//doc.powerdns.com/authoritative/settings.html#setting-default-soa-edit-signed
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
s.com/authoritative/guides/kskroll.html
5 - https://doc.powerdns.com/authoritative/guides/zskroll.html
6 - https://github.com/PowerDNS/pdns/issues/new
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
?
When the '+' is set in a forward-zones-file, the _outgoing_ query to the
specified server has the RD-bit set.
Is there a reason your internal clients *need* the AA-bit set in the
response, or was this merely curiosity? As long as the clients are
stub-resolvers, your set-up looks
/15/powerdns-authoritative-lua-records/
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
r.bz2
5 - https://downloads.powerdns.com/releases/pdns-recursor-4.1.7.tar.bz2.sig
6 - https://repo.powerdns.com/
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.power
/PowerDNS/pdns/issues/7158
2 - https://doc.powerdns.com/recursor/changelog/4.1.html#change-4.1.6
3 - https://downloads.powerdns.com/releases/pdns-recursor-4.1.6.tar.bz2
4 - https://downloads.powerdns.com/releases/pdns-recursor-4.1.6.tar.bz2.sig
5 - https://github.com/PowerDNS/pdns/issues/new
--
Pieter
regards,
Pieter
1 - https://doc.powerdns.com/recursor/settings.html#auth-zones
2 - https://doc.powerdns.com/recursor/settings.html#forward-zones
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-user
ied compiling (./configure make make install) from Git source
> (always on the master branch) and it works !
Good to hear that it does work for you once you've compiled it yourself.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
2 - https://repo.powerdns.com
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
ursor/changelog/4.1.html#4-1-4
2 - https://downloads.powerdns.com/releases/pdns-recursor-4.1.4.tar.bz2
3 - https://downloads.powerdns.com/releases/pdns-recursor-4.1.4.tar.bz2.sig
4 - https://repo.powerdns.com/
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
signature.asc
Description: Op
d the PowerDNS team
1 - https://doc.powerdns.com/authoritative/changelog/4.1.html#4-1-4
2 - https://downloads.powerdns.com/releases/pdns-4.1.4.tar.bz2
3 - https://downloads.powerdns.com/releases/pdns-4.1.4.tar.bz2.sig
4 - https://repo.powerdns.com/
--
Pieter Lexis
PowerDNS.COM BV --
packet cache. Why not?
Mostly because ALIAS is special. But your resolver's cache will hold the
answer so there will be little delay in answering.
Cheers,
Pieter
1 - https://github.com/PowerDNS/pdns/pull/6727
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
s.com/releases/pdns-recursor-4.1.3.tar.bz2
3 - https://downloads.powerdns.com/releases/pdns-recursor-4.1.3.tar.bz2.sig
4 - https://repo.powerdns.com/
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-
should always be insecure, so please
answer the first question).
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
Hi Radosław,
Pushing this back to the mailing-list, please send further replies there
as well.
On Mon, 12 Feb 2018 18:00:43 +0100
Radosław Ejsmont wrote:
> > On 12 Feb 2018, at 17:43, Pieter Lexis wrote:
> >
> > On Mon, 12 Feb 2018 11:32:11 +0100
> > Rados
continue on this path, I recommend getting a Lua
DNS library and doing an A query and see if you like the answer
before returning something to the client. In the current Lua
infrastructure in the Recursor, there is no way to re-inject a query
into the recursor from Lua.
Best regards,
ing again in X minutes?
Looking at the code, we indeed do not start an update thread after an
initial failure. Can you file a ticket about this[1]?
Thanks in advance!
Pieter
1 - https://github.com/PowerDNS/pdns/issues/new
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
__
ting functionality in the Recursor[2] to block queries based on a
loaded list.
Best regards,
Pieter
1 - https://doc.powerdns.com/recursor/lua-config/rpz.html
2 - https://doc.powerdns.com/recursor/lua-scripting/index.html
--
Pieter Lexis
PowerDNS.COM BV -- htt
e, the docs[2] do show that you need to PUT to
/servers/{server_id}/zones/{zone_id}/axfr-retrieve.
Best regards,
Pieter
1 - https://doc.powerdns.com/authoritative/http-api/zone.html#zone
2 -
https://doc.powerdns.com/authoritative/http-api/zone.html#put--servers-se
rely on database-replication instead of DNS-based replication of
the data.
Best regards,
Pieter
1 -
https://doc.powerdns.com/authoritative/modes-of-operation.html#native-replication
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdn
ZDdcDwBlnXYlhGD7Xnxu4pYvyZ/0vzMBDtaewMEuX5QkbjZTvyiu84YIeCVQxG2zjK5vkBJJjcHTcM6NltxYjnTzeEXPYJxvBT5yU114zEn9hC8x85UfUYW9O1U8Lo439A5KLP8zTPtHehXj5hNHaTz3Or5Vx8wIDAQAB"'
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
__
Hi Nikolaos,
On Thu, 14 Dec 2017 22:11:52 +0200
Nikolaos Milas wrote:
> [Error] No NS record at zone apex in zone 'noa.gr'
That is pretty damning. Can you check your data in LDAP to see if this data is
indeed (not) there?
--
Pieter Lexis
PowerDNS.COM BV -- https://www
real way to fix this issue is to do this migration or
move your clients to a full recursor (seperating the auth services from the
recursor).
I hope this helps,
Best regards,
Pieter
1 -
https://doc.powerdns.com/authoritative/guides/recursion.html#scenario-2-authoritative-server-as-recursor-fo
ow is your set up? Please share your pdns.conf and recursor.conf.
Also, can you show the output of `pdnsutil check-zone noa.gr`?
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-u
ation for the .se registry to see what they
expect and allow.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
open-source-support-out-in-the-open/
2 - http://dnsviz.net/d/egenblog.se/WiAqKw/dnssec/
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
Hello Donald,
On Tue, 28 Nov 2017 01:54:12 +
Donald Jayawardena wrote:
> May I know how to compile powerdns in windows?
Compiling on Windows has not been possible since a long time (almost a decade).
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.
ke yum pull in the 'old'
(master) versions.
And ensure that you only have the master repo configured.
Cheers,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
ht
g to a
timeout/hang.
If you want to test if this fixes the issue for you, grab a master package from
our repos[2] and retry these steps.
Best regards,
Pieter
1 - https://github.com/PowerDNS/pdns/pull/5968
2 - https://repo.powerdns.com
--
Pieter Lexis
PowerDNS.COM BV --
to NARROW.
Can you check that the zone actually has keys as well?
> Sorry I didn't put this in as a bug. I should have really. If you want
> I can do that, but I'm thinking you have all the info now from my
> testing, so it seems redundant at this point.
If this really is
Hi Eric,
On Sat, 11 Nov 2017 11:59:48 -0500
Eric Beck wrote:
> Any ideas on this?
Are you using 4.1.0-rc2 or master? API rectification was added only recently.
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing l
ps://github.com/PowerDNS/pdns/blob/master/docs/dnssec/modes-of-operation.rst
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
I hope this clarifies it some more.
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
ssec/modes-of-operation.html#signatures
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
ease read the whole page.
Good luck!
Pieter
1 - https://doc.powerdns.com/authoritative/settings.html#default-soa-edit-signed
2 -
https://doc.powerdns.com/authoritative/dnssec/operational.html#soa-edit-ensure-signature-freshness-on-slaves
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns
gmysql-dnssec=yes` enables DNSSEC for the mysql backend.
Can you tell us why this was unclear so we can amend the documentaion?
Best regards,
Pieter
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns
elp, please provide the steps you took to migrate the zones.
Best regards,
Pieter
1 - https://doc.powerdns.com/authoritative/domainmetadata.html#presigned
2 - https://doc.powerdns.com/authoritative/dnssec/migration.html
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
_
sting!
1 - https://doc.powerdns.com/recursor/changelog/4.1.html#change-4.1.0-alpha1
2 - https://downloads.powerdns.com/releases/pdns-recursor-4.1.0-alpha1.tar.bz2
3 -
https://downloads.powerdns.com/releases/pdns-recursor-4.1.0-alpha1.tar.bz2.sig
4 - https://github.com/PowerDNS/pdns/issues/new
--
P
ns-4.0.4.tar.bz2.sig
4 - https://repo.powerdns.com
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
pgph9pF171rw_.pgp
Description: OpenPGP digital signature
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
3 - https://downloads.powerdns.com/releases/pdns-recursor-4.0.5.tar.bz2.sig
4 - https://repo.powerdns.com
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
- https://downloads.powerdns.com/releases/pdns-recursor-4.0.5-rc2.tar.bz2.sig
5 - https://downloads.powerdns.com/releases/packages/pdns-recursor-4.0.5-rc2/
6 - https://repo.powerdns.com
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
pgpRoTZNbYJ5B.pgp
Description: OpenPGP digital
rsor-4.0.5-rc1.tar.bz2.sig
5 - https://downloads.powerdns.com/releases/packages/pdns-recursor-4.0.5-rc1/
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
pgpBjHXDlSCwC.pgp
Description: OpenPGP digital signature
___
Pdns-users mailing list
Hi David and Diego,
This smells like a bug in the API (as `pdnsutil check-zone` will complain about
it). Can one of you open a bug report on github about this[1]?
Thanks,
Pieter
1 - https://github.com/PowerDNS/pdns/issues/new
--
Pieter Lexis
PowerDNS.COM BV -- https://www.powerdns.com
1 - 100 of 199 matches
Mail list logo