it seems, the dynamic update protocol does not
allow things like _acme-challenge.some-host.some.domain
because there is no zone some-host.some.domain
pretty sure that is not correct, but we can't help unless
you show your
work. If you need to specify the zone to update, you can and
should. BIND's nsupdate(8) and other dynamic DNS clients
allow you to do
[RESOLVED] Re: TXT with dot in NAME for ACME via dynamic update (Axel Rau)
> Am 14.03.2020 um 19:21 schrieb Timothe Litt <[hidden email]>:
> dig _acme-challenge.imap.lrau.net.
> is missing a record type. The default is A.
> dig _acme-challenge.imap.lrau.net. txt
> will likely give you better results
It seems to work:
;; ANSWER SECTION:
_acme-challenge.imap.lrau.net. 3600 IN TXT "mAtCUMOhsZiajcz5v0ae37-8VRlXFZEyd9csm6ARJYQ"
_acme-challenge.imap.lrau.net. 3600 IN TXT "tR0VhMRfb4v5WsctEgoD3aWNRJ73n2wqn9hlTPE9pA0"
Here, I see, what me prevented to run my challenge successfully.
LEs boulder server didn’t like more than 1 RR in the RRSET.
Using 'replace‘ instead of 'add‘ in dnspython update.Update solves my problem.