mirror of https://github.com/dler-io/Rules.git
Resolve LAN rules so domains pointing at LAN go direct
pull/98/head98413a7added no-resolve to Domestic IPs. That rule set was the last one before LAN to resolve a domain, and LAN's own IP rules never resolve, so a domain whose DNS record points at 192.168.x.x now falls through to MATCH and reaches the proxy node's network instead of the local one. Let the LAN IP rules resolve again. In Rule.yaml and Rule_Lite.yaml the GEOIP,CN rule right after LAN resolves anyway, so this adds no lookups. Egern's LAN set goes back to resolving as it did before98413a7.
parent
563f42db53
commit
944051cef5
@ -1,11 +1,12 @@
|
||||
payload:
|
||||
# > LAN
|
||||
# No no-resolve: domains whose records point at these ranges must match here.
|
||||
- DOMAIN-SUFFIX,local
|
||||
- IP-CIDR,10.0.0.0/8,no-resolve
|
||||
- IP-CIDR,100.64.0.0/10,no-resolve
|
||||
- IP-CIDR,127.0.0.0/8,no-resolve
|
||||
- IP-CIDR,172.16.0.0/12,no-resolve
|
||||
- IP-CIDR,192.168.0.0/16,no-resolve
|
||||
- IP-CIDR6,::1/128,no-resolve
|
||||
- IP-CIDR6,fc00::/7,no-resolve
|
||||
- IP-CIDR6,fe80::/10,no-resolve
|
||||
- IP-CIDR,10.0.0.0/8
|
||||
- IP-CIDR,100.64.0.0/10
|
||||
- IP-CIDR,127.0.0.0/8
|
||||
- IP-CIDR,172.16.0.0/12
|
||||
- IP-CIDR,192.168.0.0/16
|
||||
- IP-CIDR6,::1/128
|
||||
- IP-CIDR6,fc00::/7
|
||||
- IP-CIDR6,fe80::/10
|
||||
|
||||
Loading…
Reference in New Issue