(Go: >> BACK << -|- >> HOME <<)
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.

Sign up for GitHub

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

Jump to bottom

Issue 'Update fail for dynv6 #235' seems to be back again in latest. #277

Closed
richardpowellus opened this issue Dec 8, 2019 · 3 comments
Closed

Issue 'Update fail for dynv6 #235' seems to be back again in latest. #277

richardpowellus opened this issue Dec 8, 2019 · 3 comments

Comments

@richardpowellus
Copy link
Contributor
richardpowellus commented Dec 8, 2019 •
edited
Loading

This issue seems to be back again. I'm seeing the exact same issue now with the latest 2.6-dev:

inadyn | inadyn[1]: In-a-dyn version 2.6-dev -- Dynamic DNS update client.
inadyn | inadyn[1]: Update forced for alias router.home.my.domain, new IP# x.x.x.x
inadyn | inadyn[1]: Update forced for alias server.home.my.domain, new IP# x.x.x.x
inadyn | inadyn[1]: Update forced for alias login.home.my.domain, new IP# x.x.x.x
inadyn | inadyn[1]: Fatal error in DDNS server response:
inadyn | inadyn[1]: [200 OK] addresses unchanged
inadyn | inadyn[1]: Error response from DDNS server, exiting!
inadyn | inadyn[1]: Error code 48: DDNS server response not OK

Originally posted by @dprus in #235 (comment)
@troglobit
Copy link
Owner

Are you by any chance using the ipv4.dynv6.com service instead of the default dynv6.com? The ipv4 has a different plugin that, I just noticed, doesn't check for unchanged.

@richardpowellus
Copy link
Contributor Author

I'm not explicitly using it but it looks like it's falling back to it - maybe because it can't access the ipv6 server? (which is strange since ipv6 is configured correctly from what I can tell).

@troglobit
Copy link
Owner

OK, that explains it. I'll apply the same patch to the ipv4 plugin, and close this issue. The IPv6 problem we'll have to address in a separate issue methinks

@troglobit troglobit mentioned this issue Dec 10, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@troglobit @richardpowellus