Advanced Configuration
Safely tune AiBooster DNS and routing behavior, verify each change, and recover from a broken configuration.
Advanced Configuration
Advanced controls vary by AiBooster version and operating system. Use only the options shown by your installed client; a setting documented here may be hidden when the platform does not support it.
Export a known-good configuration before changing DNS, route rules, listening addresses, or ports. Change one setting at a time so it can be rolled back.
Safe change workflow
- Record the AiBooster version, platform, active profile, and current mode.
- Export or copy the current configuration to a private location.
- Make one change and reconnect.
- Test both a direct destination and a destination expected to use the proxy.
- If either fails, restore the previous value before trying another change.
Do not paste subscription URLs, access tokens, private keys, or complete configuration exports into public issue reports.
DNS controls
If your client exposes DNS settings, choose resolvers that are reachable on the current network and permitted by your organization. Encrypted DNS endpoints also require the device clock and TLS validation to be working.
After a DNS change:
- reconnect so the active profile is reloaded;
- retry with a new browser window or clear only the relevant DNS cache;
- confirm that ordinary hostnames resolve before debugging route rules;
- restore the previous resolver if lookups time out or return no answer.
Avoid adding copied DNS JSON unless your installed client explicitly offers a raw configuration editor and documents the accepted schema for that version.
Route-rule order
Route rules are normally evaluated in order. Keep specific rules above broad catch-all rules and verify the resulting action for each destination.
| Action | Use it for | Check after saving |
|---|---|---|
| Direct | Destinations that must bypass the proxy | The destination still opens on the current network |
| Proxy | Destinations that should use the selected node | The selected node is connected and reachable |
| Block | Destinations intentionally denied | Only the intended hostname or address is affected |
Prefer exact hostnames or the narrowest supported suffix. Broad wildcards and IP ranges can unexpectedly affect login, update, and payment endpoints.
Listening addresses and LAN access
Keep local proxy listeners bound to 127.0.0.1 unless another device must use
them. Binding to 0.0.0.0 exposes the listener to reachable network interfaces;
enable it only on a trusted network and restrict access with the host firewall.
Never expose a local proxy port directly to the public internet.
Recovery checklist
If AiBooster stops connecting after an advanced change:
- Restore the last exported configuration.
- Return DNS and route mode to their previous values.
- Disable LAN sharing and restore the prior listen address and ports.
- Reconnect or restart the client.
- Follow the proxy settings guide and then the troubleshooting guide.
When contacting support, include the app version, operating system, the exact error text, and whether rollback restored service. Redact all credentials.