# Godaddy DNS cerbot dns-challenge renewal? **URL:** \ **Category:** Help\ **Created:** [December 28, 2022, 12:29pm UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176 "2022-12-28T12:29:35Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![gctwnl](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/gctwnl/32/26687_2.png) [@gctwnl](https://community.letsencrypt.org/u/gctwnl)\ **Post date:** [December 28, 2022, 12:29pm UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/1 "2022-12-28T12:29:35Z")
I have been running autorenewal with `certbot --webroot`. I moved my domains over to GoDaddy because (a) I already had a few there and (b) I read in various places that GoDaddy DNS supports Letsencrypt DNS challenge. I've found [https://pypi.org/project/certbot-dns-godaddy/](https://pypi.org/project/certbot-dns-godaddy/). Is that indeed the way to go? ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [December 28, 2022, 2:18pm UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/2 "2022-12-28T14:18:44Z")
Never change a winning team. Is your team not winning currently? ---
**Author:** ![gctwnl](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/gctwnl/32/26687_2.png) [@gctwnl](https://community.letsencrypt.org/u/gctwnl)\ **Post date:** [December 28, 2022, 11:07pm UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/3 "2022-12-28T23:07:43Z")
Uncertain what you meant. Maybe something along the lines of "if it ain't broken, don't fix it", but I do want to fix something: using a wildcard cert and that is not possible with webroot. Anyway, I went ahead and it works. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [December 29, 2022, 7:01am UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/4 "2022-12-29T07:01:18Z")
> [@gctwnl](#): > > Maybe something along the lines of "if it ain't broken, don't fix it" Correct. > [@gctwnl](#): > > but I do want to fix something: using a wildcard cert and that is not possible with webroot. Ah, you might want to have mentioned that earlier. > [@gctwnl](#): > > Anyway, I went ahead and it works. Nice 🙂 If you wanted to have a wildcard certificate then yes, I'd also would recommend the `certbot-dns-godaddy` plugin to get it, as it enabled automatic renewal. ---
**Author:** ![gctwnl](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/gctwnl/32/26687_2.png) [@gctwnl](https://community.letsencrypt.org/u/gctwnl)\ **Post date:** [December 29, 2022, 11:19am UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/5 "2022-12-29T11:19:48Z")
Actually, I am running into an issue (solvable, just have to think about how). I already had `certbot` installed but without this plugin. Getting the plugin on my server means installing `pip` and that means having to add the whole compiler setup to the system. So, instead, I used the docker container. That container is self-sufficient, and it installs the stuff in the docker host (which is intentional) via docker mounts. But there, the previously installed `certbot` `apt` package on the docker host has setup a `systemd` timer and a `crontab` entry, which is run by the docker host `certbot` which does not have the plugin... I can uninstall the `apt` `certbot` package (the container can handle everything, data remains on the docker host), but that means I have to create my own 'renewal-hook/timing/etc' setup. So, I can either just swallow `pip` and everything that comes with it, or I have a bit of self-maintained stuff to build automatic renewal/install using the container only. The container gives me a cleaner system at the expense of a dependency (will the container be updated in the future?) and some basic manual work. Hmm. Decisions, decisions... ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [December 29, 2022, 12:04pm UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/6 "2022-12-29T12:04:37Z")
I was not aware using `pip` would require a compiler? Or maybe Rust for `cryptography`? If you do start using `pip`, it's highly recommended to run it in a virtual environment. You could also ask the maintainer of the `certbot-dns-godaddy` plugin if they can make their plugin available using `snap`, which is the recommended method of installing Certbot. ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [December 29, 2022, 12:47pm UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/7 "2022-12-29T12:47:20Z")
And, the acme.sh ACME client ([link here](https://github.com/acmesh-official/acme.sh)) has a GoDaddy DNS plug-in Being all shell script might avoid some packaging issues ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [December 29, 2022, 12:48pm UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/8 "2022-12-29T12:48:15Z")
Or repurpose the plugin script from `acme.sh` so it'll work with Certbot as an auth hook 😛 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [January 28, 2023, 12:49pm UTC](https://community.letsencrypt.org/t/godaddy-dns-cerbot-dns-challenge-renewal/190176/9 "2023-01-28T12:49:12Z")
Closed on January 28, 2023, 12:49pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.