-
Notifications
You must be signed in to change notification settings - Fork 322
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
DNSExit: Updater breaks when provided with a zone and a non-identical hostname (bug) #673
Comments
So the documentation at https://dnsexit.com/dns/dns-api/ is wrong? Their documentation explicitly says that it is OK to either include or exclude the domain (zone). If their documentation is wrong, please also file a bug report with them to fix their documentation or their service.
#674 uses the full host name for |
This only works for updating the top-level ddns domain ie. myroot.publicvm.com. Its better explained here, incl. response from DNSexit themselves. |
These are the cases (JSON to DNSExit) I need to understand:
@DiSHTiX Can you confirm that the above is complete and correct? |
Description
When a configuration is provided with a zone and a hostname that is not identical to the zone, the updater fails. This issue was introduced with the implementation of the dnsexit provider, due to a misunderstanding of how the dnsexit API expects updates for 'subdomains'. This bug has been confirmed via the report here: opnsense/plugins
Steps to reproduce
Expected behavior
The updater should produce the following JSON call for host
host1.myroot.publicvm.com
on zonemyroot.publicvm.com
:Actual behavior
Currently, the name field is identical to the full hostname, which does not work.
Note that for calls with identical
name
andzone
, this does work, as does an emptyname
with azone
that contains a root hostname (i.e. myroot.publicvm.com)Proposed solution
The issue can be fixed by:
I will propose a solution shortly.
The text was updated successfully, but these errors were encountered: