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

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

From	Mark Andrews <marka@isc.org>
Newsgroups	comp.protocols.dns.bind
Subject	Re: Cannot get nsupdate to work (for letsencrypt acme.sh client)
Date	2020-08-06 08:17 +1000
Message-ID	<mailman.793.1596665795.942.bind-users@lists.isc.org> (permalink)
References	(1 earlier) <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> <CACC6821-33C6-43A5-8429-91DC58242228@isc.org>

Show all headers | View raw

Unfortunately comments section on that page doesn’t work.  You press preview and you get a error response back.

> On 6 Aug 2020, at 02:21, Brett Delmage <Brett@BrettDelmage.ca> wrote:
> 
> 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
> 
> 

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org

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

Thread

Re: Cannot get nsupdate to work (for letsencrypt acme.sh client) Mark Andrews <marka@isc.org> - 2020-08-06 08:17 +1000

csiph-web