IP-Based Rule
There are 2 IP-based rule types. For a request whose hostname is a domain, the rules are matched strictly in order: when the walk reaches an IP-based rule and no rule above it has matched, Chute resolves the domain with DNS and walks the rules again from the top with the resolved IP address. If the DNS lookup fails, IP-based rules simply do not match and the walk goes on with the rules below them.
IP-CIDR
IP-CIDR,192.168.0.0/16,DIRECT
IP-CIDR,10.0.0.0/8,DIRECT
IP-CIDR,172.16.0.0/12,DIRECT
IP-CIDR,127.0.0.1/8,DIRECT
Rule matches if the IP address of the request matches a specified range.
GEOIP
GEOIP,US,DIRECT
Rule matches if the GeoIP test result matches a specified country code.
GEOIP,UNKNOWN,DIRECT matches an address the country database has no entry for — a private or unallocated range, or no database at all. It works in [Rule] and inside a rule set alike.
IP-based Rule Option
Option: no-resolve
GEOIP,US,DIRECT,no-resolve
IP-CIDR,172.16.0.0/12,DIRECT,no-resolve
With the 'no-resolve' option, the rule never asks for that lookup and is skipped for a request that names a domain, so it only ever matches requests that already carry an IP address.
Notice: A rule never overtakes an IP-based rule written above it, and an IP-based rule without 'no-resolve' placed above domain rules costs a DNS lookup for every request that reaches it. If DNS resolution fails, IP-based rules do not match and the walk goes on with the rules below them, down to FINAL; rule evaluation is not aborted.