I have deleted the Accuweather integration after the API was changed from free to paid access, however Home Assistant is still trying to connect to dataservice.accuweather.com every 80 seconds.
No automations or dashboards have anything left related to Accuweather, and there are no entities associated with Accuweather.
Any idea what might be going on or how I can track down why this is happening?
I also had and deleted AccuWeather. I just checked my AdGuard logs and do not see any reference to it. I know that doesn’t help you solve anything, but at least I can confirm that it should stop calling home. I’d try a full reboot, as others have suggested.
Unfortunately that didn’t find anything either. It’s not a big deal I guess, just something that bugs me now that I noticed it happening.
Thanks for the suggestion though.
Thanks.
I’m using Adguard Home, and seeing this in the Adguard Query log. I disabled the DNS cache and rebooted Adguard Home, however the issue is still there.
I did look at both of those, the first link is not relevant since I am not using AdGuard DNS, but instead Adguard Home.
Adguard Home stores DNS cache in memory. The second post in your second link, explains that: Upon restarting AdGuardHome, the cache is completely cleared. Also, cached entries cannot be manipulated outside of the AdGuardHome memory space since AdGuardHome manages the storing of cached entries in its memory.
There is an option to clear cache and I have done that multiple times as well as rebooting Adgd Home, and the box that Home Assistance is running on:
These are the cache settings in Adguard Home
Since this is RPI5 it is time to move up the chain. The next thing is the DNS on the RPI5.
That is because you have both Home Assistant and AdGuard Home on the RPI5. Something is in conflict between them
Some more suggestions:
For DNS cache issues on a Raspberry Pi 5, ensure that your DNS settings are correctly configured in the network settings. You may need to check the /etc/resolv.conf file and ensure it includes valid DNS servers, or use commands like sudo nmcli c modify <connection-name> ipv4.dns 8.8.8.8 to set a reliable DNS server. forums.raspberrypi.com xavier.arnaus.net
Common DNS Cache Issues on Raspberry Pi 5
Symptoms of DNS Issues
Temporary Failure in Name Resolution: Users may encounter errors when trying to access websites, such as “Temporary failure in name resolution.”
Successful Pings to IP Addresses: While domain names fail to resolve, direct pings to IP addresses (e.g., 8.8.8.8) may succeed, indicating a DNS problem rather than a network issue.
Possible Causes
Static IP Configuration: Setting a static IP address without proper DNS settings can lead to resolution failures. Ensure that the DNS server addresses are correctly configured.
Incorrect resolv.conf Entries: The /etc/resolv.conf file may not reflect all DNS servers. It might only show one entry (e.g., nameserver 127.0.0.1), which can prevent proper DNS resolution.
Network Manager Configuration: If using Network Manager, ensure that the DNS settings are correctly applied. Use commands like sudo nmcli c show to check the connection name and modify DNS settings accordingly.
Troubleshooting Steps
Check Current DNS Settings:
Run cat /etc/resolv.conf to view current DNS entries.
If necessary, manually add additional DNS servers (e.g., 1.1.1.1, 8.8.8.8) to this file.
Modify Network Configuration:
For static IP setups, edit /etc/dhcpcd.conf to include proper DNS entries:
Code
static domain_name_servers=1.1.1.1 8.8.8.8
2. **Restart Network Services**:
* After making changes, restart the network service or reboot the Raspberry Pi to apply the new settings.
3. **Use Alternative DNS Servers**:
* If issues persist, consider using public DNS servers like Google (8.8.8.8) or Cloudflare (1.1.1.1) for better reliability.
By following these steps, you can resolve common DNS cache issues on your Raspberry Pi 5.
[ forums.raspberrypi.com](https://forums.raspberrypi.com/viewtopic.php?t=377383)[ xavier.arnaus.net](https://xavier.arnaus.net/blog/quick-dns-server-on-a-raspberry-pi)
OK, lets clarify a couple of things, since I think we are at cross purposes here.
To clarify, the RPi 5 is running the HA OS, AGH is running in an LXC container in Proxmox.
Secondly, I’m actually not sure what DNS has to do with my original question, which is not why AGH is blocking Accuweather, but since Accuweather has been removed from HA, all automations, and all dashboards, why is it still trying to contact back to dataservice.accuweather.com every 80 secs as showing up in the logs. Surely its not going to show up in the DNS Query log unless something associated with Accuweather still remains in HA.
However to rule out anything to do with AGH DNS I have another instance of AGH running on a TrueNas and HA is now using that instance for DNS. The AGH logs on the TrueNas instance are still showing that HA is still reaching out to dataservice.accuweather.com.