We use Amazon Elastic Beanstalk which provides a load balancer and also changes EC2 instances on each code update. This was resulting in IP changes and because the controller is caching the DNS result indefinitely this was leading to all the issues we were experiencing with values not updated. We added an indirect fix to microcontroller version which would reboot it when the weather query was not updated in 24 hours (we didn’t know the issue but knew the “fix”). We didn’t add this to the Pi as it may be doing other tasks or might need user intervention to reboot.
Next version will do a DNS lookup per weather query (1 hour) and let the local router cache the DNS (as it normally does).
Thanks!