-
Notifications
You must be signed in to change notification settings - Fork 4
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
Various issues updating Dynamic DNS entry for a subdomain of a wildcard #9
Comments
At the very minimum there is a bug where the 0.0.0.0 record had its TTL updated and a new record was also created with the correct IP, so it looks like the update-vs-create logic in the Gandi module (and perhaps others if that code is reused) is buggy. |
I'm aware it is buggy but do not have time to fix it yet. I'll check it once I get some free time but I welcome pull requests and will gladly review them if someone is willing to work on it. |
Hello,
With a wildcard domain and two subdomains as configured here, I wish to have Dynamic DNS update only one of the subdomains,
fw.DOMAIN.TLD
, which is anA
record. (The other subdomain is aCNAME
pointing tofw
, and therefore Dynamic DNS is only enabled forfw
.)Caddy is able to fetch a certificate using a DNS-01 challenge, so I know the Gandi token is good. However, the
A
record is not being updated.Expected behavior
No error message and a single
A
record reflecting the tracked interface's IP.Actual behavior
There was already an
A
record forfw
in theDOMAIN.TLD
zone with TTL 300 (the shortest TTL supported by Gandi). When the IP of the tracked interface matched what was already in DNS, the log output below was generated and no changes were made in Gandi DNS.Most recent output at the top, with the first line being the error in question:
However, while troubleshooting this issue I manually set the IP of the
A
record to0.0.0.0
, restarted Caddy, and:0.0.0.0
record was changed from 300 to 3600 (matching the configured 1-hour TTL), but the IP was not changed; andA
record (yes, duplicate label offw
) was created with TTL 3600 and the correct IP, resulting in both records being returned in queries. This is broken.Here's the log output in that case, throwing the same
domain not found in DNS
error as above, but with two extra records above it which themselves seem correct:Environment
OPNsense Business 24.4_8 (amd64)
caddy-custom 2.7.6.5.0.3.5.5_16
os-caddy 1.5.4_1
Downstream
The downstream maintainer of the Caddy plugin for.OPNsense has recommended I open the issue here.
The text was updated successfully, but these errors were encountered: