You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using dynamic_dns module in Go Caddy and got this error repeatedly: unable to find Google managaged zone for domain what-the-heck-is-wrong-with-libdns.com
All my configurations were correct, I even ran the API call using an access token from the service account being used by Go Caddy and ran the domain listing call to be sure.
After scratching my head for about an hour, I finally realized the issue:
The API call returns dnsName as <domain>. (note the . at the end). In turn, this means I had to update my Caddy config to include . at the end of all domains.
It would be nice to have this normalized at the module level here, as I assume for other libdns providers, this is a non-issue (based on the config examples I've seen for dynamic_dns, none of them included a trailing ., hence the assumption)
This also seemingly breaks dynamic_dns now because it won't match subdomains to the domain with the . at the end.
I believe this PR would fix it (I have never written Go before, but its a 3 line change) #7
The text was updated successfully, but these errors were encountered:
This issue was specifically for fixing the Caddy dynamic_dns module's use of clouddns. As of now, it appears fixed on my PR branch:
normalize trailing . in GCD zone lookup
deduplicate prepValuesForCloudDNS array (probably some Caddy configuration error on my part, but the duplicate was causing the POST to fail with Already Exists error code 409, and the subsequent PATCH would fail because the POST failed to create the record, but not for the expected reason; anyway by deduplicating this array, we can be sure 409 truly means the record already exists, and this isn't simply a rrsValue duplication issue
Using
dynamic_dns
module in Go Caddy and got this error repeatedly:unable to find Google managaged zone for domain what-the-heck-is-wrong-with-libdns.com
All my configurations were correct, I even ran the API call using an access token from the service account being used by Go Caddy and ran the domain listing call to be sure.
After scratching my head for about an hour, I finally realized the issue:
The API call returns
dnsName
as<domain>.
(note the.
at the end). In turn, this means I had to update my Caddy config to include.
at the end of all domains.It would be nice to have this normalized at the module level here, as I assume for other
libdns
providers, this is a non-issue (based on the config examples I've seen fordynamic_dns
, none of them included a trailing.
, hence the assumption)This also seemingly breaks
dynamic_dns
now because it won't match subdomains to the domain with the.
at the end.I believe this PR would fix it (I have never written Go before, but its a 3 line change)
#7
The text was updated successfully, but these errors were encountered: