This is not related to DNSSEC, but can still be done.
At A.dyndns.xxx.com you'd have a CNAME which points to an A record at
A.customers.dyndns.xxx.com, and the user's TSIG key would only allow
modifying the record(s) in that subzone. So you'd have one subzone
per customer, and the TSIG keys would
Hello everyone,
I would like to configure my own dyndns service. I managed to configure
and make it work.
I try now to secure this service.
I followed with success this doc :
https://doc.powerdns.com/authoritative/dnsupdate.html). However, as far
as I understand there is only one key for the
Am 22.06.2021 um 17:27 schrieb Brian Candler:
On 22/06/2021 16:16, Thomas via Pdns-users wrote:
Thanks for the clarification, but this scares me. How can I have
configured the server in a way it thinks it is authoritative for the
entire Internet?
It should be authoritative for zur-sonne.it and
On 22/06/2021 16:16, Thomas via Pdns-users wrote:
Thanks for the clarification, but this scares me. How can I have
configured the server in a way it thinks it is authoritative for the
entire Internet?
It should be authoritative for zur-sonne.it and the other 2500 domains
we have, sihosting.clou
Thanks for the clarification, but this scares me. How can I have
configured the server in a way it thinks it is authoritative for the
entire Internet?
It should be authoritative for zur-sonne.it and the other 2500 domains
we have, sihosting.cloud is not part of the domains we host
Am 22.06
On 22/06/2021 15:54, Thomas wrote:
Doing a "dig www.zur-sonne.it +nostats +nocomments +nocmd @localhost"
I (think) get correct result:
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.5 <<>> www.zur-sonne.it
+nostats +nocomments +nocmd @localhost
;; global options: +cmd
;www.zur-sonne.it.
Am 22.06.2021 um 16:16 schrieb Brian Candler:
On 22/06/2021 14:55, Thomas via Pdns-users wrote:
I have upgraded pdns authoritative server from version 4.3 to version
4.4.1 on CentOS 7, MySQL is the backend.
If I query a CNAME record on both servers I get the following error
(do not remember if
On 22/06/2021 14:55, Thomas via Pdns-users wrote:
I have upgraded pdns authoritative server from version 4.3 to version
4.4.1 on CentOS 7, MySQL is the backend.
If I query a CNAME record on both servers I get the following error
(do not remember if it worked before the upgrade):
[root@pdns1 lo
Hello,
I have upgraded pdns authoritative server from version 4.3 to version
4.4.1 on CentOS 7, MySQL is the backend.
If I query a CNAME record on both servers I get the following error (do
not remember if it worked before the upgrade):
[root@pdns1 log]# nslookup www.example.it localhost
Serv
On Tue, Jun 22, 2021 at 7:46 AM Brian Candler via Pdns-users
wrote:
> It doesn't actually matter what nameserver you use for acme-ns.example.net,
> because the data stored within it is completely transitory. Even something
> with a RAM backend would be fine. I happen to use bind9 because it w
On 22/06/2021 12:33, Jan-Piet Mens via Pdns-users wrote:
For Letsencrypt protocol to generate certificate I have to enable zone
transfer in my powerdns.
I think you mean "DNS Updates" for Let's Encrypt dns-01, but I don't
believe these are possible in PowerDNS with the LDAP backend.
Possibly
For Letsencrypt protocol to generate certificate I have to enable zone
transfer in my powerdns.
I think you mean "DNS Updates" for Let's Encrypt dns-01, but I don't
believe these are possible in PowerDNS with the LDAP backend.
-JP
___
Pdns-use
12 matches
Mail list logo
