-
-
Notifications
You must be signed in to change notification settings - Fork 145
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.com present for updating DDNS no longer functions as of sometime after November 20th 2023. #465
Comments
this particular issue could likely be resolved if you use the latest API https://dnsexit.com/dns/dns-api/ and update the A and AAAA instead of the |
Can confirm the above ^
{
"apikey": "myapikey",
"domain": "domainaddress",
"update": [
{
"type": "A",
"name": "",
"content": "ipv4address",
"ttl": 60
},
{
"type": "AAAA",
"name": "",
"content": "ipv6address",
"ttl": 60
}
]
} |
Great, a solution is available. Contributions are welcome, as usual. |
This is an SSL error |
the DNSExit.com present for updating DDNS no longer functions as of sometime after November 20th 2023.
The current error output is
inadyn/plugins/dnsexit.c
Line 45 in c62d719
Checking DNSExit.com documentation the current api use is as follows:
Additionally, before this DNSExit.com preset stopped working, the enable IPV6 function did not work correctly. Two requests were made to DNSExit.com, the first being the IPV4 address and then the IPV6 address afterwards which would overwrite the previously set IPV4 address
inadyn/plugins/dnsexit.c
Lines 98 to 102 in c62d719
The text was updated successfully, but these errors were encountered: