Add Functionality to Check Current IP #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.