 using nsupdate to create ...
 using nsupdate to create ...
                 using nsupdate to create TXT records for letsencrypt and DKIM
  using nsupdate to create TXT records for letsencrypt and DKIM
                - Accueil
- Espace Client
- Community Forum
- General Discussion
- Developer Discussion
- using nsupdate to create TXT records for letsencrypt and DKIM
- Community Forum
- using nsupdate to create TXT records for letsencrypt and DKIM
Topic: using nsupdate to create TXT records for letsencrypt and DKIM
                                Hello.I'm trying to automate letsencrypt cert creation via dnsThis is what I'm sending to nsupdate:  server api.dynu.com  zone example.com  update add _acme-challenge.example.com 30 IN TXT "blahblahblah"  key hmac-md5:example.com ==SomeRandomTokenValue==  send  quitit is returning success. My TSIG token is recent and valid.  rc=0My problem is that when I query dns via dig/nslookup/web-site the record is not there. I also don't see any updates in any of the logs that I've found at dynu.com.Does anybody have any experience with this? Is something missing from somewhere?
                                
                            
                            
                            
                        Reply with quote | Report
| Author | Topic: using nsupdate to create TXT records for letsencrypt and DKIM | 
|---|---|
| joseadias Joined: 17/05/2018 |  using nsupdate to create TXT records for letsencrypt and DKIM mercredi 16 mars 2022 08:06 
                                    Hello.I'm trying to automate letsencrypt cert creation via dnsThis is what I'm sending to nsupdate:  server api.dynu.com  zone example.com  update add _acme-challenge.example.com 30 IN TXT "blahblahblah"  key hmac-md5:example.com ==SomeRandomTokenValue==  send  quitit is returning success. My TSIG token is recent and valid.  rc=0My problem is that when I query dns via dig/nslookup/web-site the record is not there. I also don't see any updates in any of the logs that I've found at dynu.com.Does anybody have any experience with this? Is something missing from somewhere?
                                    
                                 | 
 It is currently jeudi 30 octobre 2025 21:11 US Mountain Standard Time
 It is currently jeudi 30 octobre 2025 21:11 US Mountain Standard Time
        
            jeudi 30 octobre 2025 21:11
        
    
 
  
  
 