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

Change 200 OK return string to good #10

Merged
merged 1 commit into from
May 23, 2022
Merged

Change 200 OK return string to good #10

merged 1 commit into from
May 23, 2022

Conversation

rotx
Copy link
Contributor

@rotx rotx commented May 22, 2022

inadyn parses the 200 return string for "good", "nochg", "dnserr", "911", "badauth", and "nohost". All other strings result in "NOTOK". This small change fixes this.

The UDM log before the change:
May 22 01:34:18 udm inadyn[10905]: Update forced for alias my.example.com, new IP# 1.2.3.4
May 22 01:34:18 udm inadyn[10905]: Fatal error in DDNS server response:
May 22 01:34:18 udm inadyn[10905]: [200 OK] DNS Record Update Successful!
May 22 01:34:18 udm inadyn[10905]: Error response from DDNS server, ignoring ...

After the change:
May 22 10:20:14 udm inadyn[18317]: Update forced for alias my.example.com, new IP# 1.2.3.4
May 22 10:20:14 udm inadyn[18317]: Updating cache for my.example.com

inadyn parses the 200 return string for "good", "nochg", "dnserr", "911", "badauth", and "nohost". All other strings result in "NOTOK". This small change fixes this.
@rotx rotx mentioned this pull request May 22, 2022
@avidrissman
Copy link

FYI can confirm this fixes #7. 👍 from me, thank you.

Copy link
Owner

@willswire willswire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good! I doubt this change will have breaking effects for folks running different configs - it's an HTTP status 200 OK either way. just seems that the folks at Synology are picky about the body of the response 😜

@willswire willswire merged commit 56141b0 into willswire:main May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants