Groups > comp.protocols.dns.bind > #16040

Re: Cannot get nsupdate to work (for letsencrypt acme.sh client)

From	Brett Delmage <Brett@BrettDelmage.ca>
Newsgroups	comp.protocols.dns.bind
Subject	Re: Cannot get nsupdate to work (for letsencrypt acme.sh client)
Date	2020-08-05 12:21 -0400
Message-ID	<mailman.792.1596644428.942.bind-users@lists.isc.org> (permalink)
References	<alpine.DEB.2.21.2008041629380.11138@pannier.local> <26AFF3C2-B56B-48C7-9DEB-EA1341E02A48@isc.org> <alpine.DEB.2.21.2008042119110.11138@pannier.local> <D852B3BC-1478-4A85-80B5-9C5D7678BF0B@isc.org> <alpine.DEB.2.21.2008051154450.15647@pannier.local>

Show all headers | View raw

On Wed, 5 Aug 2020, Mark Andrews wrote:

> If I use the example zone on that page *no* errors are reported.
> If I modify restarchitect.com to have a A record at _acme-challenge.restarchitect.com then errors will be reported.

I certainly did get an error originally. I would not have found this 
page if I didn't have the error message to search for.

After reviewing my command history I have concluded that it is possible 
that I originally tested with an A, not TXT record, thusa causing the 
error. Then I switched it, unaware of the difference to check-names.

Thanks for the in-depth 'proof'. I have removed check-names now and it
works as it should.

Brett

Back to comp.protocols.dns.bind | Previous | Next | Find similar

Thread

Re: Cannot get nsupdate to work (for letsencrypt acme.sh client) Brett Delmage <Brett@BrettDelmage.ca> - 2020-08-05 12:21 -0400

csiph-web