filter for domains that use the fqdn (Zone) in the submit #63
Comments
gmkey
added a commit
to gmkey/docker-ddns-old
that referenced
this issue
Feb 16, 2021
This pull requests removes the "ZONE" string from the "hostname" or "domain" fields of the request, as this is used by AVM fritz!box routers to check if the update is actually executed, but would recursively lead to updates in the form of: ZONE=example.com request url: https://ddns.example.com/v3/update?hostname=hostname.example.com&myip=<ipaddr>&password=<passwd> Resulting entry in the zone file: hostname.example.com.example.com Solves dstapp#63
christophknuth
pushed a commit
to christophknuth/docker-ddns
that referenced
this issue
Sep 2, 2022
This pull requests removes the "ZONE" string from the "hostname" or "domain" fields of the request, as this is used by AVM fritz!box routers to check if the update is actually executed, but would recursively lead to updates in the form of: ZONE=example.com request url: https://ddns.example.com/v3/update?hostname=hostname.example.com&myip=<ipaddr>&password=<passwd> Resulting entry in the zone file: hostname.example.com.example.com Solves dstapp#63
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The newer versions of the AVM fritz!box routers, now require the DDNS domain to be a FQDN, including the zone. This leads to entries in the zone file that are like this:
ZONE=example.comrequest url:
https://ddns.example.com/v3/update?hostname=hostname.example.com&myip=<ipaddr>&password=<passwd>Resulting entry in the zone file:
hostname.example.com.example.comThe obvious solution of not using the FQDN but only the hostname results in tons of error messages.
Request: would it be possible to add a filter to the go scripts that checks if the hostname string contains a substring that is equal to the zone string and remove .zone from the hostname? (or any other solution that would yield the same result).
PS: this seems like a little patch, but unfortunately I have very limited go skills.
The text was updated successfully, but these errors were encountered: