Open Advanced > Xray > Routing data. GeoData supplies the domain and IP categories used in routing and editor suggestions.

Default routing data

The default section contains:

• geosite.dat — domain categories from domain-list-community.
• geoip.dat — IP categories from geoip.

Use the section’s Update button to update both files together. They cannot be updated separately or deleted.

Custom routing data

Add a source with a name/file name, a domain or IP type, and an HTTPS download URL. The name identifies the saved file used by rules such as ext:other.dat:cn.

Each source can be inspected, updated, or deleted. There is no local file-import action. The app downloads and validates the data before making it available.

Files live in one flat managed directory. Subdirectories and conflicting file names are not supported. Do not manually move files while the app is using them.

After restoring a backup

Backup & restore restores source records, not DAT files. Matching valid local files are reused; other sources remain pending download. This does not block restoring configurations or opening the home page.

Download pending sources here before using a configuration that needs them. Until the file is downloaded and indexed, its categories are not available for autocomplete. If the source is blocked on your network, use another working VPN configuration before downloading. Restore does not start a download or silently remove dependent rules. Default data uses valid existing or bundled files.

Categories and routes

Domain/IP rule inputs suggest categories from installed data. Direct-region choices also depend on actual default categories; a country name alone does not create a valid GeoSite or GeoIP entry.

Deleting a custom source can make routes that reference it invalid. Remove or update those references before using the route again.

A shared Custom/Raw configuration can declare custom dependencies by file name and URL. Import rejects a name conflict instead of overwriting an existing source. Sharing format.

Data updates apply to later starts; they do not hot-replace the rules loaded by an active core. Configure schedules in Data updates.