Geographical rules depend on database versions, resolution results, and rule order. IP geolocation and domain classifications are not real-time and may have edge cases. Update the rule data, then use connection records to see whether a more specific rule matched first. For services that require stable routing, add an exact domain rule before geographical rules and use the geographical database only as a fallback.
How to verify the database version, resolution result, and rule order
In the connection detail, verify the actual domain, resolved IP, geographical rule, and database update time. A CDN address differing from the user's region is common.
- Is the database or rule set up to date?
- Did a more specific rule match the domain first?
- Does fake-ip mode require enhanced mapping?(See DNS settings)
- Does the destination service use a CDN or IP addresses in multiple regions?
Override geographical misclassification with an exact-domain rule
- Use the connection list to confirm the rule that actually matched
- Use a specific DOMAIN rule to override the misclassified destination
- Update GeoIP, GeoSite, or the rule provider
- For high-priority services, use explicit domain or subnet rules instead of relying only on geographical rules(See Rule-based Routing documentation)
Geographical rules work well as fallbacks, not as replacements for every exact rule
Database update frequency is determined by the corresponding project
A CDN service's actual egress can change with region and network