Hi Guys
Has anyone else had this experience?
Every time I search for updates or a plugin, the search takes forever.
But as soon as the data is down, it goes much faster? What could be the cause of the behavior?
Regards
has to do with your DNS setup on the OPNsense.
Adguard?
The rest of the System works a charm and Adguard is since more or less one week on it.
How could i resolve it?
Enter a public DNS server, e.g. 1.1.1.1 in System > Settings > General, and try if that changes anything.
If it doesn't, try "Prefer IPv4 over IPv6" on the same page.
Hi pmhausen
It didnt help :(
Could be UFS the problem? Dont think so?!
from the shell/prompt of the OPNsense, can you ping 1.1.1.1 or 8.8.8.8 or 9.9.9.9?
Yes i can
Then try the command
host 1.1.1.1
1.1.1.1.in-addr.arpa domain name pointer one.one.one.one.
host 8.8.8.8
8.8.8.8.in-addr.arpa domain name pointer dns.google.
you should get something like that... if they work then you should try updating from console and see...
I have Adguard on OPNSense and also had this issue.
To fix this, I set the DNS to a public resolver (Cloudflare) on System-->Settings-->General as suggested. However, that doesn't actually work unless you also check the box on the same page "Do not use the local DNS service as a nameserver for this system".
You are my Hero @Embroider5378
Now it is like day and night.
Thanks for your post.
Quote from: Embroider5378 on March 22, 2023, 03:00:25 AM
I have Adguard on OPNSense and also had this issue.
To fix this, I set the DNS to a public resolver (Cloudflare) on System-->Settings-->General as suggested. However, that doesn't actually work unless you also check the box on the same page "Do not use the local DNS service as a nameserver for this system".
This solved the issue here too, but it is more of a workaround than a solution. The root cause for slow backups was an activated Unbound DNS service where no forwarding was enabled. I assume that this caused Unbound to use the root DNS servers, which explains the painfully slow update process.
So, a better solution would be to either disable Unbound DNS if not needed, or to check the box
Services / Unbound DNS / Query Forwarding / "Use System Nameservers"
Sorry for reviving a dead post.
I also agree that this is a workaround. For my current setup I require Adguardhome+Unbound So I have it set up so that AGH uses Unbound as upstream dns. I have DoT setup on Unbound so I can't use query forwarding to system nameservers in unbound.
Is there another way to get this setup to work without checking "Do not use the local DNS service as a nameserver for this system"?
The strange thing is that I had it working just fine, but had to change the boot drive. So I restored from backup and suddenly it doesn't work.
Nevermind, I figured it out.
On the new install I had AGH listening only to LAN traffic. Reinstalled and let it listen to all interfaces, now it works like a charm.