Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update fails for subdomain without zones.txt #36

Open
sporkman opened this issue Dec 13, 2024 · 1 comment
Open

Update fails for subdomain without zones.txt #36

sporkman opened this issue Dec 13, 2024 · 1 comment

Comments

@sporkman
Copy link

I keep getting a "exit_hook returned with non-zero exit code!" if I try to use a subdomain (eg: "foo.i.example.com").

The last bit of output, with or without debug, is a full json-encoded list of all zones.

If I create "zones.txt" and add "i.example.com", everything works fine.

This is FreeBSD 13.3, PowerDNS 4.9.1, bash 5.2.37.

What else can I give you to assist with troubleshooting this? Or is this expected behavior (I'm not totally clear on what the zones.txt file is used for)?

@alainwolf
Copy link

alainwolf commented Dec 13, 2024

The way I understand it, its hard for the script to guess what zone (on the PowerDNS server) a domain name (for which a cert has been requested) belongs to.

foo.i.example.com could be managed by any of the foo.i.example.com, i.example.com or example.com zones.

The zones.txt file gives the script a hint, that foo.i.example.com is managed by the i.example.com zone.

With sudo pdnsutil list-all-zones | sudo tee /etc/dehydrated/zones.txt > /dev/null you should be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants