Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    ACME nsupdate supported DNS providers

    ACME
    3
    3
    2.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jeffhammett
      last edited by

      I've read through the documentation on the new ACME package for Lets Encrypt certs. Reading through the various methods for verification, it looks like nsupdate is probably the best in my case, at least upon initial review. I didn't see this covered in the documentation (maybe I missed it), but I assume that this only works with certain DNS providers? And some sort of API key or credentials needs to be entered in the package?

      If this is correct is there a list of supported providers anyone (outside of the package itself)?

      Or am I misunderstanding something about nsupdate?

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        nsupdate is generally for self-hosted DNS using BIND or a similar server that supports RFC2136 updates.

        Paid DNS providers generally have their own APIs or update methods, which is why there are many other choices for providers in the ACME package.

        Any of the DNS-based options should be fine, if you already have a domain or account with one of those providers.

        There might be some paid DNS providers out there that do RFC2136 but I'm not aware of any specifically.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • MikeV7896M
          MikeV7896
          last edited by

          @jimp:

          There might be some paid DNS providers out there that do RFC2136 but I'm not aware of any specifically.

          Dyn does… but it's not the easiest thing in the world to get working. At least it wasn't when I last tried it (which was before I started using pfSense, which might have been part of the problem).

          The S in IOT stands for Security

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.