Setting Up AdGuard: DNS Redirect doesn’t work Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

hmm strange, your windows box 192.168.1.2 is sending quite a lot of DNS request to your RPi but it seems nothing happen with these request. There is no answer to the client nor AGH is not trying to resolve them. Looks like the request are blocked somewhere. Do you use an firewall software on the RPi?

Can you go to AGH web ui and try to change DNS server from https://dns10.quad9.net/dns-query to 9.9.9.9. There should be a button Test Upstream. Does this work?
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

Yes, I'm using GUFW on the Dietpi. I will disable.

Before doing this, in the AG web UI "DNS settings" page, I wasn't sure where to change the server address. The "Upstream servers" are edited in Dietpi, so instead I did it in the "Bootstrap DNS servers" section which is editable in the web UI. Is this the correct place to change the server?

Changed the first entry from 9.9.9.10 to 9.9.9.9 then clicked "Test upstreams" and got the message "Specified servers are working correctly."

I then disabled UFW and clicked "Test upstreams" again. Got the msg "Specified servers are working correctly." Also worked correctly with 9.9.9.10.
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

so instead I did it in the "Bootstrap DNS servers" section
That's the wrong place. Upstream DNS you would need to adjust on the first box on top of the page. Usually the first box should be editable as we disabled Unbound. But it doesn't matter. I don't think Upstream DNS is the issue. I guess it is your UFW firewall blocking incoming DNS traffic. Pls disabled UFW and perfrom the test again we did before viewtopic.php?p=36008#p36008

It's enough to capture 100 lines instead of 500

Code: Select all

tcpdump -i any -c100 -nn port 853 or port 53 or port 443
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

Hi Joulinard,
UFW is inactive, results below. Still unable to edit the first box in "DNS settings" however.
Also, redirecting my PC DNS to the Rpi gives me internet access! So that's progress :)
AND, AdGuard is showing Dashboard results for the first time (for the PC only) !

Code: Select all

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
23:29:04.168031 IP 192.168.1.100.38696 > 35.186.227.140.443: Flags [P.], seq 2492623951:2492623990, ack 4067559866, win 501, options [nop,nop,TS val 2747981122 ecr 1000936368], length 39
23:29:04.168719 IP 192.168.1.100.38696 > 35.186.227.140.443: Flags [P.], seq 39:63, ack 1, win 501, options [nop,nop,TS val 2747981123 ecr 1000936368], length 24
23:29:04.168848 IP 192.168.1.100.38696 > 35.186.227.140.443: Flags [F.], seq 63, ack 1, win 501, options [nop,nop,TS val 2747981123 ecr 1000936368], length 0
23:29:04.185992 IP 35.186.227.140.443 > 192.168.1.100.38696: Flags [.], ack 63, win 332, options [nop,nop,TS val 1000989396 ecr 2747981122], length 0
23:29:04.186096 IP 35.186.227.140.443 > 192.168.1.100.38696: Flags [F.], seq 1, ack 63, win 332, options [nop,nop,TS val 1000989396 ecr 2747981122], length 0
23:29:04.186169 IP 192.168.1.100.38696 > 35.186.227.140.443: Flags [.], ack 2, win 501, options [nop,nop,TS val 2747981140 ecr 1000989396], length 0
23:29:04.186706 IP 35.186.227.140.443 > 192.168.1.100.38696: Flags [.], ack 64, win 332, options [nop,nop,TS val 1000989396 ecr 2747981123], length 0
ip 23:31:01.926780 IP 192.168.1.2.58750 > 192.168.1.100.53: 43059+ A? secure20.sync.com. (35)
23:31:01.928565 IP 192.168.1.100.16245 > 205.251.198.27.53: 12762% [1au] A? SecuRe20.SYnC.COm. (46)
23:31:01.929035 IP 192.168.1.100.53 > 192.168.1.2.58750: 43059 4/0/0 A 34.202.86.107, A 50.17.80.65, A 52.21.182.194, A 50.17.142.229 (99)
23:31:01.957406 IP 205.251.198.27.53 > 192.168.1.100.16245: 12762*-$ 4/4/1 A 52.21.182.194, A 34.202.86.107, A 50.17.80.65, A 50.17.142.229 (247)
23:31:01.959148 IP 192.168.1.100.7578 > 192.52.178.30.53: 49614% [1au] DS? Sync.cOm. (37)
23:31:02.031842 IP 192.52.178.30.53 > 192.168.1.100.7578: 49614*- 0/6/1 (854)
23:31:02.032522 IP 192.168.1.100.8582 > 192.35.51.30.53: 23743% [1au] DS? Sync.com. (37)
23:31:02.073393 IP 192.35.51.30.53 > 192.168.1.100.8582: 23743*- 0/6/1 (854)
23:31:02.075219 IP 192.168.1.100.21741 > 192.12.94.30.53: 37775% [1au] DS? sYNC.com. (37)
23:31:02.153389 IP 192.12.94.30.53 > 192.168.1.100.21741: 37775*- 0/6/1 (854)
23:31:02.153866 IP 192.168.1.100.47516 > 192.54.112.30.53: 45435% [1au] DS? SyNC.COm. (37)
23:31:02.199359 IP 192.54.112.30.53 > 192.168.1.100.47516: 45435*- 0/6/1 (854)
23:31:02.199727 IP 192.168.1.100.38003 > 192.31.80.30.53: 18309% [1au] DS? sYnc.coM. (37)
23:31:02.278098 IP 192.31.80.30.53 > 192.168.1.100.38003: 18309*- 0/6/1 (854)
23:31:15.126916 IP 54.186.29.180.443 > 192.168.1.100.59752: Flags [P.], seq 1210272252:1210272283, ack 1782112776, win 118, options [nop,nop,TS val 3216363493 ecr 3497249902], length 31
23:31:15.127179 IP 192.168.1.100.59752 > 54.186.29.180.443: Flags [P.], seq 1:36, ack 31, win 501, options [nop,nop,TS val 3497549986 ecr 3216363493], length 35
23:31:15.205712 IP 54.186.29.180.443 > 192.168.1.100.59752: Flags [.], ack 36, win 118, options [nop,nop,TS val 3216363572 ecr 3497549986], length 0
23:32:36.387886 IP 192.168.1.2.51058 > 192.168.1.100.53: 18540+ A? d.dropbox.com. (31)
23:32:36.390000 IP 192.168.1.100.18396 > 192.31.80.30.53: 50304% [1au] A? DrOPBox.com. (40)
23:32:36.463441 IP 192.31.80.30.53 > 192.168.1.100.18396: 50304- 0/8/2 (742)
23:32:36.464018 IP 192.168.1.100.27864 > 205.251.193.59.53: 23669% [1au] A? d.drOpBoX.Com. (42)
23:32:36.464228 IP 192.168.1.100.51828 > 199.249.120.1.53: 47176% [1au] A? AwsDNs-17.oRg. (42)
23:32:36.464442 IP 192.168.1.100.16570 > 156.154.101.3.53: 4969% [1au] A? AwsDNs-51.co.uk. (44)
23:32:36.465172 IP 192.168.1.100.59760 > 192.42.93.30.53: 55999% [1au] A? AWsDNS-06.Net. (42)
23:32:36.465615 IP 192.168.1.100.14763 > 199.249.112.1.53: 42940% [1au] A? AWsDns-17.orG. (42)
23:32:36.465853 IP 192.168.1.100.23109 > 213.248.216.1.53: 36940% [1au] A? aWSdnS-51.Co.uK. (44)
23:32:36.466085 IP 192.168.1.100.51343 > 192.26.92.30.53: 56472% [1au] A? AWSDNs-06.net. (42)
23:32:36.481746 IP 199.249.120.1.53 > 192.168.1.100.51828: 47176- 0/8/9 (813)
23:32:36.482364 IP 192.168.1.100.12755 > 205.251.192.145.53: 56712% [1au] A? nS-1162.AwSDns-17.oRg. (50)
23:32:36.482408 IP 199.249.112.1.53 > 192.168.1.100.14763: 42940- 0/8/9 (813)
23:32:36.482812 IP 192.168.1.100.44549 > 205.251.198.81.53: 9274% [1au] A? nS-1162.awsDns-17.oRG. (50)
23:32:36.491903 IP 205.251.193.59.53 > 192.168.1.100.27864: 23669*-$ 1/4/1 CNAME d.v.drOpBoX.Com. (197)
23:32:36.492389 IP 156.154.101.3.53 > 192.168.1.100.16570: 4969- 0/8/9 (847)
23:32:36.492405 IP 192.168.1.100.61627 > 205.251.193.59.53: 29566% [1au] A? V.DRoPBOx.CoM. (42)
23:32:36.493271 IP 192.168.1.100.36746 > 192.31.80.30.53: 59140% [1au] A? AWsdNs-39.com. (42)
23:32:36.494477 IP 192.168.1.100.15273 > 205.251.195.179.53: 20606% [1au] A? nS-1949.AWSDNS-51.Co.Uk. (52)
23:32:36.502751 IP 213.248.216.1.53 > 192.168.1.100.23109: 36940- 0/8/9 (837)
23:32:36.503953 IP 192.168.1.100.28608 > 205.251.197.246.53: 42405% [1au] A? ns-1949.AwsDNs-51.cO.Uk. (52)
23:32:36.506448 IP 192.42.93.30.53 > 192.168.1.100.59760: 55999- 0/8/9 (861)
23:32:36.507385 IP 192.168.1.100.6680 > 205.251.199.134.53: 31950% [1au] A? nS-564.aWSDNs-06.net. (49)
23:32:36.509699 IP 205.251.192.145.53 > 192.168.1.100.12755: 56712*-$ 1/4/9 A 205.251.196.138 (336)
23:32:36.510037 IP 192.168.1.100.55443 > 205.251.192.145.53: 39380% [1au] AAAA? nS-1162.AWSdns-17.orG. (50)
23:32:36.510172 IP 205.251.198.81.53 > 192.168.1.100.44549: 9274*-$ 1/4/9 A 205.251.196.138 (336)
23:32:36.519680 IP 205.251.193.59.53 > 192.168.1.100.61627: 29566-$ 0/4/1 (178)
23:32:36.520251 IP 192.168.1.100.11122 > 205.251.199.160.53: 28468% [1au] A? NS-773.AwSdns-32.Net. (49)
23:32:36.520448 IP 192.168.1.100.59465 > 199.249.112.1.53: 48590% [1au] A? AwSDNs-31.ORg. (42)
23:32:36.520743 IP 192.168.1.100.16921 > 199.249.120.1.53: 62786% [1au] A? AwsDNs-31.Org. (42)
23:32:36.520953 IP 192.168.1.100.23504 > 156.154.101.3.53: 7949% [1au] A? awSdNS-48.Co.UK. (44)
23:32:36.521161 IP 192.168.1.100.45345 > 156.154.102.3.53: 29589% [1au] A? AWSDnS-48.CO.Uk. (44)
23:32:36.521322 IP 192.168.1.100.39618 > 205.251.195.34.53: 5672% [1au] A? ns-773.AWSdns-32.net. (49)
23:32:36.535193 IP 205.251.199.134.53 > 192.168.1.100.6680: 31950*-$ 1/4/9 A 205.251.194.52 (335)
23:32:36.535706 IP 192.168.1.100.18491 > 205.251.193.199.53: 25447% [1au] AAAA? NS-564.aWSdNs-06.nEt. (49)
23:32:36.535939 IP 205.251.195.179.53 > 192.168.1.100.15273: 20606*-$ 1/4/9 A 205.251.199.157 (338)
23:32:36.536966 IP 192.168.1.100.10916 > 205.251.199.55.53: 51224% [1au] A? Ns-1949.aWsDns-51.Co.UK. (52)
23:32:36.537152 IP 199.249.112.1.53 > 192.168.1.100.59465: 48590- 0/8/9 (813)
23:32:36.537487 IP 192.168.1.100.9660 > 205.251.198.95.53: 28231% [1au] A? ns-1276.awsdNS-31.ORG. (50)
23:32:36.537979 IP 199.249.120.1.53 > 192.168.1.100.16921: 62786- 0/8/9 (813)
23:32:36.538078 IP 205.251.192.145.53 > 192.168.1.100.55443: 39380*-$ 1/4/9 AAAA 2600:9000:5304:8a00::1 (348)
23:32:36.538292 IP 192.168.1.100.46154 > 205.251.192.159.53: 28859% [1au] A? Ns-1276.AWSdNS-31.ORG. (50)
23:32:36.539887 IP 192.26.92.30.53 > 192.168.1.100.51343: 56472- 0/8/9 (861)
23:32:36.540192 IP 192.168.1.100.40347 > 205.251.199.134.53: 24524% [1au] A? NS-564.aWsdns-06.net. (49)
23:32:36.547651 IP 205.251.199.160.53 > 192.168.1.100.11122: 28468*-$ 1/4/9 A 205.251.195.5 (335)
23:32:36.548079 IP 192.168.1.100.59201 > 205.251.193.225.53: 16234% [1au] AAAA? ns-773.AwsDNS-32.NET. (49)
23:32:36.548560 IP 156.154.101.3.53 > 192.168.1.100.23504: 7949- 0/8/9 (852)
23:32:36.549441 IP 192.168.1.100.62503 > 205.251.195.176.53: 57498% [1au] A? Ns-1926.AWsdnS-48.co.uK. (52)
23:32:36.553890 IP 156.154.102.3.53 > 192.168.1.100.45345: 29589- 0/8/9 (852)
23:32:36.554483 IP 192.168.1.100.48277 > 205.251.197.243.53: 61287% [1au] A? ns-1926.awsDns-48.Co.Uk. (52)
23:32:36.555710 IP 205.251.197.246.53 > 192.168.1.100.28608: 42405*-$ 1/4/9 A 205.251.199.157 (338)
23:32:36.556930 IP 192.168.1.100.40769 > 205.251.197.246.53: 27349% [1au] AAAA? NS-1949.awSDns-51.co.uk. (52)
23:32:36.561701 IP 205.251.195.34.53 > 192.168.1.100.39618: 5672*-$ 1/4/9 A 205.251.195.5 (335)
23:32:36.562198 IP 192.168.1.100.11269 > 205.251.195.5.53: 4430% [1au] A? D.V.dROPbOx.COM. (44)
23:32:36.563509 IP 205.251.193.199.53 > 192.168.1.100.18491: 25447*-$ 1/4/9 AAAA 2600:9000:5302:3400::1 (347)
23:32:36.564422 IP 205.251.199.55.53 > 192.168.1.100.10916: 51224*-$ 1/4/9 A 205.251.199.157 (338)
23:32:36.564555 IP 205.251.198.95.53 > 192.168.1.100.9660: 28231*-$ 1/4/9 A 205.251.196.252 (336)
23:32:36.564859 IP 192.168.1.100.47203 > 205.251.195.179.53: 47813% [1au] A? nS-1949.awSdns-51.Co.UK. (52)
23:32:36.565603 IP 192.168.1.100.18061 > 205.251.194.225.53: 63207% [1au] AAAA? nS-1276.AWSDNs-31.oRG. (50)
23:32:36.565731 IP 205.251.192.159.53 > 192.168.1.100.46154: 28859*-$ 1/4/9 A 205.251.196.252 (336)
23:32:36.567885 IP 205.251.199.134.53 > 192.168.1.100.40347: 24524*-$ 1/4/9 A 205.251.194.52 (335)
23:32:36.569632 IP 192.31.80.30.53 > 192.168.1.100.36746: 59140- 0/8/9 (860)
23:32:36.570030 IP 192.168.1.100.30141 > 205.251.196.167.53: 37288% [1au] A? NS-315.aWsdNs-39.cOm. (49)
23:32:36.575900 IP 205.251.193.225.53 > 192.168.1.100.59201: 16234*-$ 1/4/9 AAAA 2600:9000:5303:500::1 (347)
23:32:36.576179 IP 192.168.1.100.25615 > 205.251.195.34.53: 64086% [1au] AAAA? ns-773.AwsDnS-32.nEt. (49)
23:32:36.589695 IP 205.251.195.176.53 > 192.168.1.100.62503: 57498*-$ 1/4/9 A 205.251.199.134 (338)
23:32:36.590380 IP 192.168.1.100.17744 > 205.251.193.112.53: 18937% [1au] A? Ns-1926.AWsDNs-48.co.Uk. (52)
23:32:36.602502 IP 205.251.195.5.53 > 192.168.1.100.11269: 4430*-$ 2/4/1 CNAME d-edge.V.dROPbOx.COM., A 162.125.6.20 (217)
23:32:36.603032 IP 192.168.1.100.22424 > 205.251.199.134.53: 38086% [1au] A? d-EDge.v.Dropbox.CoM. (49)
23:32:36.603736 IP 192.168.1.100.25993 > 192.54.112.30.53: 2085% [1au] A? awsdns-07.cOM. (42)
23:32:36.603962 IP 192.168.1.100.46211 > 192.48.79.30.53: 10639% [1au] A? awsdnS-07.coM. (42)
23:32:36.606398 IP 205.251.195.179.53 > 192.168.1.100.47203: 47813*-$ 1/4/9 A 205.251.199.157 (338)
23:32:36.606551 IP 205.251.197.243.53 > 192.168.1.100.48277: 61287*-$ 1/4/9 A 205.251.199.134 (338)
23:32:36.607011 IP 192.168.1.100.45623 > 205.251.195.176.53: 10997% [1au] AAAA? NS-1926.AwsDns-48.Co.uK. (52)
23:32:36.607138 IP 205.251.194.225.53 > 192.168.1.100.18061: 63207*-$ 1/4/9 AAAA 2600:9000:5304:fc00::1 (348)
23:32:36.607971 IP 192.168.1.100.26479 > 205.251.198.95.53: 14575% [1au] AAAA? nS-1276.aWSDnS-31.orG. (50)
100 packets captured
100 packets received by filter
0 packets dropped by kernel
User avatar
trendy
Posts: 340
Joined: Tue Feb 25, 2020 2:54 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by trendy »

There is a successful resolution here:

Code: Select all

23:31:01.926780 IP 192.168.1.2.58750 > 192.168.1.100.53: 43059+ A? secure20.sync.com. (35)
23:31:01.928565 IP 192.168.1.100.16245 > 205.251.198.27.53: 12762% [1au] A? SecuRe20.SYnC.COm. (46)
23:31:01.929035 IP 192.168.1.100.53 > 192.168.1.2.58750: 43059 4/0/0 A 34.202.86.107, A 50.17.80.65, A 52.21.182.194, A 50.17.142.229 (99)
23:31:01.957406 IP 205.251.198.27.53 > 192.168.1.100.16245: 12762*-$ 4/4/1 A 52.21.182.194, A 34.202.86.107, A 50.17.80.65, A 50.17.142.229 (247)
Another one later for dropbox just got ignored. Are you certain that you have not miconfigured the Adguard?
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

@trendy
What is missing in the tcpdump capture is the communication between AGH and Unbound. I thought we disabled Unbound before but it's seems still active. Therefore you are not able to edit the Upstream DNS @Rhizome

Let's verify. can you post content of your AGH config file AdGuardHome.yaml

Code: Select all

cat /mnt/dietpi_userdata/adguardhome/AdGuardHome.yaml
Anyway, your issue was caused by your UFW. You would need to allow DNS traffic on UFW
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

Here's the AdGuardHome.yaml config file contents (didn't include the pswd or ids for the PC named "DESKTOP"):

Code: Select all

bind_host: 0.0.0.0
bind_port: 8083
beta_bind_port: 0
users:
- name: admin
  password: xxxx
auth_attempts: 5
block_auth_min: 15
http_proxy: ""
language: ""
rlimit_nofile: 0
debug_pprof: false
web_session_ttl: 720
dns:
  bind_hosts:
  - 0.0.0.0
  port: 53
  statistics_interval: 1
  querylog_enabled: true
  querylog_file_enabled: true
  querylog_interval: 7
  querylog_size_memory: 1000
  anonymize_client_ip: false
  protection_enabled: true
  blocking_mode: default
  blocking_ipv4: ""
  blocking_ipv6: ""
  blocked_response_ttl: 10
  parental_block_host: family-block.dns.adguard.com
  safebrowsing_block_host: standard-block.dns.adguard.com
  ratelimit: 20
  ratelimit_whitelist: []
  refuse_any: true
  upstream_dns:
  - https://dns10.quad9.net/dns-query
  upstream_dns_file: /mnt/dietpi_userdata/adguardhome/dietpi-unbound.conf
  bootstrap_dns:
  - 9.9.9.10
  - 149.112.112.10
  - 2620:fe::10
  - 2620:fe::fe:10
  all_servers: false
  fastest_addr: false
  allowed_clients: []
  disallowed_clients: []
  blocked_hosts:
  - version.bind
  - id.server
  - hostname.bind
  cache_size: 4194304
  cache_ttl_min: 0
  cache_ttl_max: 0
  bogus_nxdomain: []
  aaaa_disabled: false
  enable_dnssec: false
  edns_client_subnet: false
  max_goroutines: 300
  ipset: []
  filtering_enabled: true
  filters_update_interval: 24
  parental_enabled: false
  safesearch_enabled: false
  safebrowsing_enabled: false
  safebrowsing_cache_size: 1048576
  safesearch_cache_size: 1048576
  parental_cache_size: 1048576
  cache_time: 30
  rewrites: []
  blocked_services: []
  local_domain_name: lan
  resolve_clients: true
  local_ptr_upstreams: []
tls:
  enabled: false
  server_name: ""
  force_https: false
  port_https: 443
  port_dns_over_tls: 853
  port_dns_over_quic: 784
  port_dnscrypt: 0
  dnscrypt_config_file: ""
  allow_unencrypted_doh: false
  strict_sni_check: false
  certificate_chain: ""
  private_key: ""
  certificate_path: ""
  private_key_path: ""
filters:
- enabled: true
  url: https://adguardteam.github.io/AdGuardSDNSFilter/Filters/filter.txt
  name: AdGuard DNS filter
  id: 1
- enabled: true
  url: https://adaway.org/hosts.txt
  name: AdAway Default Blocklist
  id: 1625143630
whitelist_filters: []
user_rules: []
dhcp:
  enabled: false
  interface_name: eth0
  dhcpv4:
    gateway_ip: 192.168.1.1
    subnet_mask: 255.255.255.0
    range_start: 192.168.1.110
    range_end: 192.168.1.254
    lease_duration: 86400
    icmp_timeout_msec: 1000
    options: []
  dhcpv6:
    range_start: ""
    lease_duration: 86400
    ra_slaac_only: false
    ra_allow_slaac: false
clients:
- name: DESKTOP
  tags:
  - device_pc
  ids:
  - xxxx
  use_global_settings: true
  filtering_enabled: false
  parental_enabled: false
  safesearch_enabled: false
  safebrowsing_enabled: false
  use_global_blocked_services: true
  blocked_services: []
  upstreams: []
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

indeed Unbound is still active.

Code: Select all

upstream_dns_file: /mnt/dietpi_userdata/adguardhome/dietpi-unbound.conf
That's totally fine as this was your intention anyway.

Only thing left is to configure your UFW firewall to allow DNS traffic. 8)
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Rhizome
Posts: 27
Joined: Sun Jun 27, 2021 5:22 pm

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Rhizome »

Thanks Joulinar,
For UFW is the DNS to allow, the one found in the unbound.conf file?
User avatar
Joulinar
Posts: 5090
Joined: Sat Nov 16, 2019 12:49 am

Re: Setting Up AdGuard: DNS Redirect doesn’t work

Post by Joulinar »

Not sure what you mean but setting UFW has nothing to do with AGH or unbound directly. You simply need to allow income traffic from local network on port 53.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply