Specify IP to set for zoneedit #3261
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
netgate-git-updates
pushed a commit
that referenced
this pull request
Dec 8, 2016
|
@rbgarga Did you manage to test it? |
|
No, I don't have an account to validate it, what is a common situation when we deal to dyndns. But I've checked recommended clients source code and they all use this parameter. https://sourceforge.net/projects/zoneclient/files/ Now I've updated the ticket and submitter will be able to help us testing it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documentation of the zoneedit dynamic DNS change API:
https://support.zoneedit.com/Knowledgebase/Article/View/4/1/changes-to-dynamic-dns
Format is:
https://dynamic.zoneedit.com/auth/dynamic.html?host=<your_hostname>&dnsto=<your_ip>
The dyndns.class code for "zoneedit" does not specify "dnsto" at all. So I guess Zoneedit will be assuming the IP address that the request came from, which will be whatever is the current default gateway of pfSense - which probably works OK for ordinary failover of a primary to secondary, but not when the user wants the dynamic DNS name to point to something else.
This is a possible fix for Redmine 6992. It needs testing by someone with the relevant configuration and Zoneedit account, e.g. the OP of the issue.
https://redmine.pfsense.org/issues/6992