OK, I’m currently using DHCP in AGH with my ISP’s DNS set in my router. This method is definitely better (at least on my network…) than using your router for DHCP with the Pi’s address as the router’s DNS. My slow resolving issues have disappeared.
Thanks so much for your help!
good to hear - have a nice day!
Hi Phixion,
I am having problem with extremely slow adguard home too.
I am trying to implement your setting but I am not quite sure what is local domain.
Could you shed some light into where I can have that info?
My setup:
router: 10.0.0.1
DHCP server: its adguardhome
DNS: its adguard home
DHCP range: 10.0.0.2-10.0.0.100
So I figure it will be like below, but what about the local domain part?
[/0.0.10.in-addr.arpa/]10.0.0.1
1.1.1.1:53
1.0.0.1:53
8.8.8.8
8.8.4.4
Thanks in advance
I am trying to implement your setting but I am not quite sure what is local domain.
If you don’t use a local domain and AGH is your DHCP, you can safely ignore this settings, just use regular upstream DNS servers:
1.1.1.1
8.8.8.8
1.0.0.1
8.8.4.4
mix em a bit and enable parallel requests. My settings only make sense if your DHCP server is not AGH.
Please upload logs if the problem persists. Here’s a few commands to test dns responsetime:
Linux:
external host:
$ time dig reddit.com
internal host (multicast):
$ time dig hassio.local
$ host 10.0.0.1
Windows:
ipconfig /all
powershell "Measure-Command { nslookup reddit.com 2> $null }" | FINDSTR "^Milliseconds"
Latest UPDATE:
Oct 27 - The issue resurface again… super slowwww
Oct 25:
I managed to fix the issue, turned out it has nothing to do with AGH,
The root cause was my windows have docker and it modified my hosts file.
Somehow screwed up DNS request of chrome Chrome on its IPv6,
All I have to do is add ::1 behind docker’s 127.0.0.1 entries in hosts file.
The link that helped me with this issue can be found here.
Hi Phixion,
Thanks for your haste response.
Here is the weird thing, when I use CLI to check the DNS time, the response time seems normal
For example, Netflix:
Ubuntu hosting adguard home
xxx@xxx:~$ time dig netflix.com
; <<>> DiG 9.11.3-1ubuntu1.13-Ubuntu <<>> netflix.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58140
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;netflix.com. IN A
;; ANSWER SECTION:
netflix.com. 9 IN A 34.248.165.48
netflix.com. 9 IN A 52.18.82.167
netflix.com. 9 IN A 52.17.27.129
netflix.com. 9 IN A 52.212.172.106
netflix.com. 9 IN A 52.214.223.236
netflix.com. 9 IN A 54.154.81.103
netflix.com. 9 IN A 54.76.159.18
netflix.com. 9 IN A 34.248.179.192
;; Query time: 7 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Oct 23 14:21:12 +08 2020
;; MSG SIZE rcvd: 168
real 0m0.035s
user 0m0.017s
sys 0m0.008s
My personal Windows
powershell "Measure-Command { nslookup netflix.com 2> $null }" | FINDSTR "^Milliseconds"
Milliseconds : 58
My personal windows Google Chrome
On the browser > inspect element > Network it is extremely slow.
I tried on other browsers too some websites are fast and some are slow.
Explanation that I captured from another attempt, it seems like DNS lookup took quite some time:
But in AGH query log, it still show normal timing:
Hardware info:
CPU: Intel® Quad-Core Processor J1900 (2 GHz)
MEM: 8GB DDR3
AGH: on Hassio docker
glad you could fix it
How did you manage to get the processing time so low?
I have 30ms on average (my starting internet ping is 10ms, I can’t go lower than that, but 30ms seems a bit too much for a RPi4 B).
This is my configuration:
I only have the adblocker enabled
I have enabled the DHCP server
I set up one DNS rewrite
The problem reoccur… taking forever to load again… sigh!
UGH, I wonder the same too!
from CLI, it seems normal for the hostname to resolve, but on my chrome everything just end up very ugly. Deleting cookie, and cache, refreshing DNS nothing helps.
I even removed all entries in hosts file but same slowness.
This is using firefox to access gmail instead of using chrome
but from CLI still showing normal response time
powershell "Measure-Command { nslookup gmail.com 2> $null }" | FINDSTR "^Milliseconds"
Milliseconds : 38
and your configuration is the same with mine too.
I have plenty of block lists though,
also a list of like 20-30 Custom filtering rules.
General Settings:
DNS same as yours
Encryption Setting: all unticked
Clients: all my 50+ devices
DHCP: Enabled with Static leases
Yours may be slow because it has to search through so many DNS blocklists, but I only have AdGuard DNS filer enabled.
That makes me wonder if using Adguard DNS filter only is sufficient?
Anyway… I tried to untick all of them… the speed seems more decent now!
Lets hope this will last…
With the latest update (of AGH) it started to go down, maybe I will finally get close to the average.
