AdGuardHome Asuswrt-Merlin-AdGuardHome-Installer (AMAGHI) cont.

[saison2023]

You should try changing your upstream to:

Spoiler: Upstream DNS servers

[/router.asus.com/][::]:553
[/www.asusnetwork.net/][::]:553
[/www.asusrouter.com/][::]:553
[/use-application-dns.net/][::]:553
[/dns.resolver.arpa/][::]:553
[/lan/][::]:553
[/ad.localdomain/][::]:553
[//][::]:553

should solve your issue.

And your Private reverse DNS servers section should be :

Spoiler: Private reverse DNS servers

[::]:553
[/10.in-addr.arpa/][::]:553
[/16.172.in-addr.arpa/][::]:553

Thanks a lot, it seems this did the trick.
I was aware for Reverse DNS and doble entry but was totally unable to see how to configure Upstream DNS Servers.

Thank you very much

 

[SomeWhereOverTheRainBow]

Thanks a lot, it seems this did the trick.
I was aware for Reverse DNS and doble entry but was totally unable to see how to configure Upstream DNS Servers.

Thank you very much

Not a problem. I am glad I was able to review your settings and determine the root cause for you. For any one referencing this in the future with similar scenario, it is important to remember (or know) that dnsmasq has been moved to port :553. All local service requests have to communicate back to dnsmasq. It is "okay" to use the routers lan IP but it is critical to put the port number with it. With that being said, this goes along with any dns service that answers from a port other than port 53.

 

[Kyjiep]

Not a problem. I am glad I was able to review your settings and determine the root cause for you. For any one referencing this in the future with similar scenario, it is important to remember (or know) that dnsmasq has been moved to port :553. All local service requests have to communicate back to dnsmasq. It is "okay" to use the routers lan IP but it is critical to put the port number with it. With that being said, this goes along with any dns service that answers from a port other than port 53.

Hello. Can you help me with one problem related to Adguard Home and dnsmasq? In general, when i enable the dnsmasq log, Adguard Home stops working. I don’t really understand this, but judging by the system log, Adguard Home cannot start after rebooting the router. Also, DDNS and all the addons I have installed do not work. At the same time, the load on all processor cores begins to jump from 0 to 100%. To make it clearer why I need this, I will leave here a link to the topic in this forum that led me to you https://www.snbforums.com/threads/domain-based-vpn-routing-script.79264/page-23#post-871403 (posts 452-457).

 

[SomeWhereOverTheRainBow]

Hello. Can you help me with one problem related to Adguard Home and dnsmasq? In general, when you enable the dnsmasq log, Adguard Home stops working. I don’t really understand this, but judging by the system log, Adguard Home cannot start after rebooting the router. Also, DDNS and all the addons I have installed do not work. At the same time, the load on all processor cores begins to jump from 0 to 100%. To make it clearer why I need this, I will leave here a link to the topic in this forum that led me to you https://www.snbforums.com/threads/domain-based-vpn-routing-script.79264/page-23#post-871403 (posts 452-457).

One thing I have noticed in these forums when using "dnsmasq" lately is you have to be careful with when you enable the "dnsmasq log" . I have no solution for dnsmasq log acting buggy. From how the script is coded all your upstream DNS resolution should be done by AdGuardHome which has its own query log. The only thing you could possibly see in DNSMASQ log is DHCP stuff and "local" requests for network clients.

 

[Kyjiep]

One thing I have noticed in these forums when using "dnsmasq" lately is you have to be careful with when you enable the "dnsmasq log" . I have no solution for dnsmasq log acting buggy. From how the script is coded all your upstream DNS resolution should be done by AdGuardHome which has its own query log. The only thing you could possibly see in DNSMASQ log is DHCP stuff and "local" requests for network clients.

OK. Thank you.

 

[SomeWhereOverTheRainBow]

OK. Thank you.

I have pushed a minor update that should solve the problem.

Minor update includes:

• Default Schema change from 24 to 27.
• Improvement/Additions for better switching between DNSMASQ, (any other service on port :53), and AdGuardHome. Now AdGuardHome will no longer have a hard time claiming port :53 on startup.
• Improvement/Additions for stopping AdGuardHome services.

 

[muffintastic]

I have pushed a minor update that should solve the problem.

Minor update includes:

• Default Schema change from 24 to 27.
• Improvement/Additions for better switching between DNSMASQ, (any other service on port :53), and AdGuardHome. Now AdGuardHome will no longer have a hard time claiming port :53 on startup.
• Improvement/Additions for stopping AdGuardHome services.

Whatever you've change on Adguard no longer works. I've uninstalled it completely re-installed each version and just hangs on Starting Adguard.... dead and nothing else. I've also done installed it on a fresh clean wipe of my router still won't start, this is on RT-AX86U and the Pro. Anyone else having this issue? Do not update if you want it to still work.

 

[Kyjiep]

I have pushed a minor update that should solve the problem.

Minor update includes:

• Default Schema change from 24 to 27.
• Improvement/Additions for better switching between DNSMASQ, (any other service on port :53), and AdGuardHome. Now AdGuardHome will no longer have a hard time claiming port :53 on startup.
• Improvement/Additions for stopping AdGuardHome services.

Unfortunately, nothing has changed for me.

 

[SomeWhereOverTheRainBow]

Whatever you've change on Adguard no longer works. I've uninstalled it completely re-installed each version and just hangs on Starting Adguard.... dead and nothing else. I've also done installed it on a fresh clean wipe of my router still won't start, this is on RT-AX86U and the Pro. Anyone else having this issue? Do not update if you want it to still work.

Unfortunately, nothing has changed for me.

Works fine each time for me on fresh install right out the box. Idk what yall do differently on your setups. I will post screenshots shortly.

FWI, Adguardhome just change its Schema in the .yaml. If this is your first time updating AdGuardHome in a long time, you may need a new .yaml file, or otherwise you will have to manually edit the schema from whatever it is to 27. If you are restoring from backups, this could be whats causing the problem for you. Otherwise, Idk what else could be causing the issue.

AdGuardHome is working for me straight on first install though. Please share similar screenshots so I can see where your installation process may be breaking.

 

[saison2023]

Spoiler: Initial message

Works fine each time for me on fresh install right out the box. Idk what yall do differently on your setups. I will post screenshots shortly.

View attachment 53833
View attachment 53835
View attachment 53839

FWI, Adguardhome just change its Schema in the .yaml. If this is your first time updating AdGuardHome in a long time, you may need a new .yaml file, or otherwise you will have to manually edit the schema from whatever it is to 27. If you are restoring from backups, this could be whats causing the problem for you. Otherwise, Idk what else could be causing the issue.

View attachment 53838

AdGuardHome is working for me straight on first install though. Please share similar screenshots so I can see where your installation process may be breaking.

If we exclude the fact it was very difficult to get the update (took me 5 attempts, don't know why).
Otherwise, I was able to get the minor update applied, AdGuardHome service restarted correctly and I went to check "schema_version" at the end of my yaml file and it shows "27".
I didn't reinstall, only updated my running version (which was the previous one, I am keeping it the most "up-to-date" as possible)
Seems alright, will report if any issue

 

[Tomo]

I have pushed a minor update that should solve the problem.

Minor update includes:

• Default Schema change from 24 to 27.
• Improvement/Additions for better switching between DNSMASQ, (any other service on port :53), and AdGuardHome. Now AdGuardHome will no longer have a hard time claiming port :53 on startup.
• Improvement/Additions for stopping AdGuardHome services.

upgraded from previous version, no problem as always !!

 

[Terrabytes]

Before I use to get ip addresses of clients on my primary subnet in Adguard. Now I am just getting localhost.localdomain (127.0.0.1). I believe I might have some setting that is misconfigured.

RT-AX86U Pro - 3004.388.4 | Adguard v0.107.40
LAN > DHCP > DNS - 208.67.222.222 | 208.67.220.220
Advertise router IP in addition to user-specified = Yes
DNS Director = Enabled | Router Redirection = Router | DNS[1-3] 8.8.8.8

I might have miss something, Please let me know if there is anything else you would like for me to provide. Your help and insight is appreciated. Thanks

 

[SomeWhereOverTheRainBow]

Before I use to get ip addresses of clients on my primary subnet in Adguard. Now I am just getting localhost.localdomain (127.0.0.1). I believe I might have some setting that is misconfigured.

RT-AX86U Pro - 3004.388.4 | Adguard v0.107.40
LAN > DHCP > DNS - 208.67.222.222 | 208.67.220.220
Advertise router IP in addition to user-specified = Yes
DNS Director = Enabled | Router Redirection = Router | DNS[1-3] 8.8.8.8

I might have miss something, Please let me know if there is anything else you would like for me to provide. Your help and insight is appreciated. Thanks

What has changed recently on your setup compared to before when you were able to see client ip and names?

 

[Terrabytes]

What has changed recently on your setup compared to before when you were able to see client ip and names?

Every time I do a version upgrade I always reset and redo everything. So it is difficult to tell you what recently changed. I can't say I deviate much as I like to keep things consistent. It has been working this way [localhost.localdomain (127.0.0.1)] for the following versions.

RT-AX86U_PRO_3004_388.4_0
RT-AX86U_PRO_388.2_0

What I would like to know is what could cause it to use localhost.localdomain (127.0.0.1) for the primary subnet ips.

 

[SomeWhereOverTheRainBow]

Every time I do a version upgrade I always reset and redo everything. So it is difficult to tell you what recently changed. I can't say I deviate much as I like to keep things consistent. It has been working this way [localhost.localdomain (127.0.0.1)] for the following versions.

RT-AX86U_PRO_3004_388.4_0
RT-AX86U_PRO_388.2_0

What I would like to know is what could cause it to use localhost.localdomain (127.0.0.1) for the primary subnet ips.

I was thinking possibly local router traffic, or maybe vpn, or redirected dns traffic. I am not sure because I am not able to reproduce the issue. Typically the 127.0.0.1 client traffic would be traffic from the router himself, or traffic that has been "redirected" to the router himself (think dns director redirecting hard coded dns clients.)

You would basically need to give us a full break down of your DNS configuration. Obviously redacted anything personal.

 

[Terrabytes]

I was thinking possibly local router traffic, or maybe vpn, or redirected dns traffic. I am not sure because I am not able to reproduce the issue. Typically the 127.0.0.1 client traffic would be traffic from the router himself, or traffic that has been "redirected" to the router himself (think dns director redirecting hard coded dns clients.)

You would basically need to give us a full break down of your DNS configuration. Obviously redacted anything personal.

Thought I provided that information in my first post.

RT-AX86U Pro - 3004.388.4 | Adguard v0.107.40
LAN > DHCP > DNS - 208.67.222.222 | 208.67.220.220
Advertise router IP in addition to user-specified = Yes
DNS Director = Enabled | Router Redirection = Router | DNS[1-3] 8.8.8.8

What else do you require? I can clean slate it and reinstall and provide details. I believe it is something simple.

 

[SomeWhereOverTheRainBow]

LAN > DHCP > DNS - 208.67.222.222 | 208.67.220.220

For your userland case it is rather simple, LAN > DHCP > DNS should be blank. Otherwise you are forcing clients to use a different DNS other than the router VIA DHCP option, and they are being "redirected" by the firewall to use the router instead. That is why clients appear to be 127.0.0.1. Why you would put those DNS servers in your LAN-DHCP is beyond me, but that is why your client namespace resolution is broken. This is the consequences of making executive decisions.

 

[Tech9]

LAN > DHCP > DNS - 208.67.222.222 | 208.67.220.220
Advertise router IP in addition to user-specified = Yes

Yes - wrong setup.

Run it just because of you and it works as intended. As people say - RTFM.

Here is what's coming from the router itself:

WAN monitoring only. It's disabled in the GUI, but this is another topic.

 

[SomeWhereOverTheRainBow]

Yes - wrong setup.

View attachment 54584

View attachment 54585

Run it just because of you and it works as intended. As people say - RTFM.

Here is what's coming from the router itself:

View attachment 54586

WAN monitoring only. It's disabled in the GUI, but this is another topic.

@Tech9 mines been going for

No reboots so far.

I am even trying out the remote DoH, DoT, and DoQ services .

Filters and Regex I am using

filters:
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_1.txt
    name: AdGuard DNS filter
    id: 1701316907
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_2.txt
    name: AdAway Default Blocklist
    id: 1701316908
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_29.txt
    name: 'CHN: AdRules DNS List'
    id: 1701316909
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_50.txt
    name: uBlock₀ filters – Badware risks
    id: 1701316910
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_11.txt
    name: Malicious URL Blocklist (URLHaus)
    id: 1701316911
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_9.txt
    name: The Big List of Hacked Malware Web Sites
    id: 1701316912
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_42.txt
    name: ShadowWhisperer's Malware List
    id: 1701316913
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_10.txt
    name: Scam Blocklist by DurableNapkin
    id: 1701316914
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_18.txt
    name: Phishing Army
    id: 1701316915
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_8.txt
    name: NoCoin Filter List
    id: 1701316916
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_44.txt
    name: HaGeZi's Threat Intelligence Feeds
    id: 1701316917
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_21.txt
    name: 'CHN: anti-AD'
    id: 1701316918
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_12.txt
    name: Dandelion Sprout's Anti-Malware List
    id: 1701316919
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_35.txt
    name: 'HUN: Hufilter'
    id: 1701316920
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_30.txt
    name: Phishing URL Blocklist (PhishTank and OpenPhish)
    id: 1701316921
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_22.txt
    name: 'IDN: ABPindo'
    id: 1701316922
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_38.txt
    name: 1Hosts (mini)
    id: 1701316923
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_19.txt
    name: 'IRN: PersianBlocker list'
    id: 1701316924
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_4.txt
    name: Dan Pollock's List
    id: 1701316925
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_43.txt
    name: 'ISR: EasyList Hebrew'
    id: 1701316926
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_49.txt
    name: HaGeZi's Ultimate Blocklist
    id: 1701316927
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_25.txt
    name: 'KOR: List-KR DNS'
    id: 1701316928
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_27.txt
    name: OISD Blocklist Big
    id: 1701316929
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_3.txt
    name: Peter Lowe's Blocklist
    id: 1701316930
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_33.txt
    name: Steven Black's List
    id: 1701316931
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_45.txt
    name: HaGeZi's Allowlist Referral
    id: 1701316932
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_15.txt
    name: 'KOR: YousList'
    id: 1701316933
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_36.txt
    name: 'LIT: EasyList Lithuania'
    id: 1701316934
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_46.txt
    name: HaGeZi's Anti-Piracy Blocklist
    id: 1701316935
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_20.txt
    name: 'MKD: Macedonian Pi-hole Blocklist'
    id: 1701316936
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_47.txt
    name: HaGeZi's Gambling Blocklist
    id: 1701316937
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_23.txt
    name: WindowsSpyBlocker - Hosts spy rules
    id: 1701316938
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_13.txt
    name: 'NOR: Dandelion Sprouts nordiske filtre'
    id: 1701316939
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_7.txt
    name: Perflyst and Dandelion Sprout's Smart-TV Blocklist
    id: 1701316940
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_41.txt
    name: 'POL: CERT Polska List of malicious domains'
    id: 1701316941
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_16.txt
    name: 'VNM: ABPVN List'
    id: 1701316942
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_14.txt
    name: 'POL: Polish filters for Pi-hole'
    id: 1701316943
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_40.txt
    name: 'TUR: Turkish Ad Hosts'
    id: 1701316944
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_17.txt
    name: 'SWE: Frellwit''s Swedish Hosts File'
    id: 1701316945
  - enabled: true
    url: https://adguardteam.github.io/HostlistsRegistry/assets/filter_26.txt
    name: 'TUR: turk-adlist'
    id: 1701316946
whitelist_filters: []
user_rules:
  - /^(.+[_.-])?adse?rv(er?|ice)?s?[0-9]*[_.-]/
  - /^(.+[_.-])?telemetry[_.-]/
  - /^ad([sxv]?[0-9]*|system)[_.-]([^.[:space:]]+\.){1,}|[_.-]ad([sxv]?[0-9]*|system)[_.-]/
  - /^adim(age|g)s?[0-9]*[_.-]/
  - /^adtrack(er|ing)?[0-9]*[_.-]/
  - /^advert(s|is(ing|ements?))?[0-9]*[_.-]/
  - /^aff(iliat(es?|ion))?[_.-]/
  - /^analytics?[_.-]/
  - /^banners?[_.-]/
  - /^beacons?[0-9]*[_.-]/
  - /^count(ers?)?[0-9]*[_.-]/
  - /^mads\./
  - /^pixels?[-.]/
  - /^stat(s|istics)?[0-9]*[_.-]/
  - /(^|\.).+xxx$/
  - /(^|\.).+sexy$/
  - /(^|\.).+webcam$/
  - /(^|\.).+sex$/
  - /(^|\.).+porn$/
  - /(^|\.).+tube$/
  - /(^|\.).+cam$/
  - /(^|\.).+adult$/
  - /^(.+[_.-])?eulerian\.net$/
  - /^(.+[_.-])?dnsdelegation\.io$/
  - /^(.+[_.-])?amp(project)?\./
  - /^(www[0-9]*\.)?xn--/

 

[SomeWhereOverTheRainBow]

Also have these services enabled: