fake-ip uses virtual IP addresses to improve domain mapping and rule capabilities, while redir-host is closer to conventional resolution. The right choice depends on the client, TUN, app compatibility, and configuration template. Start with the value recommended by the client or configuration provider. If LAN domains or devices fail, adjust the filter list for those cases.
Check these four conditions before choosing
Do not switch based on the name alone. Check the core, TUN, app compatibility, and whether rules depend on domain names before choosing a mode.
- Does the current core support fake-ip?
- Is TUN or transparent proxying enabled?
- Is the app sensitive to virtual IP addresses?
- Do rules depend on domain names rather than final IP addresses?
Choose for the use case
- For a standard client, use the DNS mode recommended by the subscription provider
- Under TUN, configure DNS hijacking according to the client documentation
- When LAN devices, printers, or internal domains fail, configure fake-ip-filter
- After changing DNS mode, clear the DNS cache and restart the client
An incomplete fake-ip configuration can break access in some apps(See DNS settings)
redir-host may reduce domain-rule recognition(See Rule configuration)
Do not let multiple clients take over DNS at the same time