AdguardTeam / AdguardTeam/AdGuardDNS

AdguardDNS syntax - wildcard rules

Aperta
#550 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Go
Stelle
952
Fork
82
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Hello, I use the AdguardDNS list on NextDNS and ControlD, but I realized that this list has its own rules and that only AdguardDNS (https://adguard-dns.io/en/public-dns.html) can solve it.

I went to test blocking two Amazon telemetry domains used on the Echo Show and Fire TV.

You can see in your list here: https://adguardteam.github.io/AdGuardSDNSFilter/Filters/filter.txt

Domain blocked in the AdguardDNS list (Edit: Both domains has an asterisk * , for some reason they sometimes disappear from this post):
||device-metrics-us*.amazon.com^
||device-metrics-*.amazon.com^

You can see that instead of adguard team blocking **device-metrics-us.amazon.com** and **device-metrics-us-2.amazon.com** probably to save space in the list and make it smaller or to cover possible new tracking domains of the same company, you (Adguard team) block some domains in a single line and put an asterisk * on the domain itself.

I went to test it in the linux terminal and realized that this type of approach works when using your DNS (https://adguard-dns.io/en/public-dns.html), but testing Next DNS or ControlDNS with the AdguardDNS list, these domains are not being blocked.

You use this type of approach in 244 domains, such as:
||sock*-goguardian.pusher.com^
||analytics*.clickdimensions.com^
||dualstack.adbert-web-lbs-*.elb.amazonaws.com^

With that, I would like to ask you from the AdguardDNS team that, in the name of transparency and in order to benefit many other users of other services and who like your AdguardDNS list, **please clarify what are the specific syntax rules that AdguardDNS uses, because this way it would be much easier for NextDNS and ControlD to implement and support 100% of your list. What is the syntax? What are the wildcard rules?**

Thank you very much

**TERMINAL LINUX (USING ADGUARD DNS):**
acer@acer-Aspire-A315-51:~$ nslookup device-metrics-us.amazon.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: device-metrics-us.amazon.com
Address: 0.0.0.0
Name: device-metrics-us.amazon.com
Address: ::

acer@acer-Aspire-A315-51:~$ nslookup device-metrics-us-2.amazon.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: device-metrics-us-2.amazon.com
Address: 0.0.0.0
Name: device-metrics-us-2.amazon.com
Address: ::

**TERMINAL LINUX (USING NEXTDNS OR CONTROLD WITH ADGUARD DNS LIST):**
acer@acer-Aspire-A315-51:~$ nslookup device-metrics-us.amazon.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: device-metrics-us.amazon.com
Address: 52.1.172.87
Name: device-metrics-us.amazon.com
Address: 3.208.140.212
Name: device-metrics-us.amazon.com
Address: 44.197.43.221

acer@acer-Aspire-A315-51:~$ nslookup device-metrics-us-2.amazon.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: device-metrics-us-2.amazon.com
Address: 54.157.203.98
Name: device-metrics-us-2.amazon.com
Address: 54.205.24.65
Name: device-metrics-us-2.amazon.com
Address: 54.166.21.152

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.