Skip to content
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

DynDNS: add deSEC IPv4&v6 simultaneos update #4543

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

9Lukas5
Copy link
Contributor

@9Lukas5 9Lukas5 commented Oct 31, 2021

Leaves the yet included services deSEC and deSEC-v6 untouched.
These are using the automatic ip-recognition from the dns service for
both record types.
This new service to create/update an entry for the same dns name with
both record types requires the IPs for both records simultaneously,
for which this new service is, leaving the distinct record services in
place for people only want to update a dedicated record.

Depends on #4542

The `_checkIP()` method is only obtaining either the legacyIP as default
or the IP if the flag is set for it.
For services that would override one entry with the newest on each
update it would not be possible to create entries with both, as this
requires them to be sent in the same request.

For this purpose this adds a new flag to signal a service needs both,
legacyIP and IP, available at the same time and a new field
`_dnsLegacyIP`.
If the new flag isn't set (which is the default) the `_checkIP()` works
like before. If the new flag is set, the `_dnsIP` field will hold the IP
and the `_dnsLegacyIP` the legacyIP.

To not break the cached-IP handling/having to fool around there as well,
the return of the `_checkIP()` is the legacyIP as default and if both
formats are needed and only IP if the `_useIPv6` is set.
Leaves the yet included services `deSEC` and `deSEC-v6` untouched.
These are using the automatic ip-recognition from the dns service for
both record types.
This new service to create/update an entry for the same dns name with
both record types requires the IPs for both records simultaneously,
for which this new service is, leaving the distinct record services in
place for people only want to update a dedicated record.
@9Lukas5 9Lukas5 force-pushed the desec-A-and-AAAA-simultaneous-update branch from a47f1c4 to 2a06e39 Compare April 24, 2022 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant