![]() The ingress is a to-do on my never ending to-do-list and it is wrong but does not affect the functionality. As reference for anyone who needs it (please note that the code below is a yaml and I hope that my copy/pasteing did not change the damn spaces necessary in a yaml file). Sorry for the confusion!įirst: Super thanks for your work! It works fine here. There was (is) a problem accessing it via hostname using Traefik, but when I go to IP:port it works fine. T11:49:48.785-0700 INFOğound single setting to update record Īn oopsie on my part - the webpage IS running. □ Email? Slack? Join from the Slack button on Github Running version dyn built on (commit 2dcbc3e) For now it forces the update on all DNS providers every 5 minutes no matter what, and this approach might lead you to being blocked with dyndns. ![]() However there is nothing in Reports to show that this is happening. I will first refactor the code such that it only updates DNS records once your public IP changes. From the updater logs its clear that and are inaccessible when Malwarebytes is running, are accessible when its not. If this is the case you will simply need to simplify. While it is not expected that the clients will prevent users from doing this, the client itself should strenuously avoid performing updates which would result in this return result. You may experience that your DDNS device does not support the separation of the group name and username. Users should not be allowed to repeatedly force updates. This can be used to verify the authentication credentials and the current IP address.Īs this is fairly infrequent, repeated instances of nochg updates will result in the host being blocked. Users may also be given the option to “force” an update. The only acceptable situation where this allowed is during client initialization when the host has already been set to the same IP address. ![]() nochg or good)Īnyway, there is a part worrying me from their documentation:Ī nochg indicates a successful update but the IP address or other settings have not changed. If you were using that other container you mentioned, do you get anything in the logs about it? (i. Running the Cloudflare dynamic DNS update script 4. Update the DNS record IP address in Cloudflare. ![]() Compare the DNS record IP address with the actual external or public IP address. Actually I found all the possible return codes although none of them correspond to these strange numbers. Find the domain containing the DNS record to update. ![]()
0 Comments
Leave a Reply. |