Skip to content

Conversation

@coxfuture
Copy link

Per Google's doc page on their dynamic DNS API:

https://support.google.com/domains/answer/6147083?hl=en#zippy=%2Cuse-the-api-to-update-your-dynamic-dns-record

"Make sure you interpret the response correctly, or you risk blocking your client from our system."
nochg {user’s IP address} | Success | The supplied IP address is already set for this host. You should not attempt another update until your IP address changes.
abuse | Error | Dynamic DNS access for the hostname has been blocked due to failure to interpret previous responses correctly.

Not sure what the rate limit is, but it seems like they really don't want you bothering them unless it needs to be changed.

Added functionality to the do_main() function that will check if the current registered IP differs from the server's current public IP. If the two IPs are the same, it will exit and put a note in the log.

coxfuture added 4 commits July 8, 2022 10:12
reason for fork
maybe instead of storing the IP in a file, I could have pinged the dyndns fqdn and compared it that way. 

eh, next time if I circle back on this.
changed from logging the IP to a file to just asking google what the registered IP is for the dyndns
switched comments back
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.

1 participant