-
Notifications
You must be signed in to change notification settings - Fork 10
MasterDNS Profiles
فارسی: پروفایلهای MasterDNS
Every time you click 💾 Save to MasterDNS Profiles, a profile is saved in the masterdns_profiles/ folder next to the KevinNet app. The MasterDNS Profiles tab lets you manage, edit, and launch any saved profile without scanning again.
Shows all saved profiles sorted by date (newest first). Each row shows:
- Profile name
- Save date
- Resolver count
Click any profile to open it in the detail panel.
You can rename the profile. If the name matches the folder name, renaming will also rename the output folder on disk.
Shows domain, folder name, resolver count, and save date.
These settings are written into client_config.toml when you save.
Iran optimal: 1 — XOR
Encrypts the payload inside each DNS packet.
| Value | Method | Notes |
|---|---|---|
0 |
None | No encryption — not recommended |
1 |
XOR | Lowest overhead — best for Iran |
2 |
ChaCha20 | Stronger but adds bytes, reducing usable MTU |
3 |
AES-128-GCM | Strong |
4 |
AES-192-GCM | Strong |
5 |
AES-256-GCM | Strongest — highest overhead |
Must match the server's
DATA_ENCRYPTION_METHODsetting exactly.
Iran optimal: 3 — Least Loss
Controls how the client picks which resolver to send each packet through.
| Value | Strategy | Notes |
|---|---|---|
1 |
Random | No feedback loop |
2 |
Round Robin | Cycles evenly — good default |
3 |
Least Loss | Favours resolvers with fewest dropped packets — best for Iran |
4 |
Lowest Latency | Favours fastest resolver |
Iran has high, uneven packet loss across resolvers. Least Loss adapts automatically.
Iran optimal: 2–3
Sends each packet to this many resolvers simultaneously. If one path drops the packet, another copy arrives via a different resolver.
-
1— no redundancy -
2— good baseline for Iran -
3— increase if you see frequent disconnections -
4+— wastes bandwidth without benefit once you have many resolvers
Iran optimal: 80–100
Upper bound for upload payload size (bytes). MasterDnsVPN probes each resolver to find the largest packet it accepts. Smaller DNS queries look less suspicious to Iran's DPI.
- Default:
150 - Iran optimal:
80–100
Iran optimal: 38
Minimum upload payload size. Resolvers that only accept smaller packets than this are excluded from the pool. 38 is very conservative — keeps the maximum number of resolvers usable.
Iran optimal: 700
Upper bound for download payload size. Large DNS responses (800–900 bytes) are more likely to be fragmented by Iranian ISPs or trigger DPI. 700 keeps downloads in a safer zone.
Iran optimal: 400
Minimum download payload size. Lowering to 400 keeps more resolvers in the pool — useful in Iran where many resolvers work but return slightly smaller responses.
Default: 18000
The local port your browser/app connects to. Set your browser proxy to SOCKS5 127.0.0.1:18000.
Only change this if another application is already using port 18000.
Iran optimal: INFO
| Level | What it shows |
|---|---|
DEBUG |
Every packet event — very noisy, for troubleshooting only |
INFO |
Connection events, resolver switches, errors |
WARN |
Warnings only |
ERROR |
Errors only |
| Option | Value | Reason |
|---|---|---|
| Encryption Method | 1 — XOR |
Lowest overhead in small DNS packets |
| Balancing Strategy | 3 — Least Loss |
High uneven packet loss in Iran |
| Packet Duplication | 2–3 |
Redundancy on lossy paths |
| Max Upload MTU | 80–100 |
Smaller queries avoid DPI |
| Min Upload MTU | 38 |
Keep maximum resolver pool |
| Max Download MTU | 700 |
Avoid ISP fragmentation |
| Min Download MTU | 400 |
Keep marginal resolvers |
| Log Level | INFO |
Normal operation |
| Button | What it does |
|---|---|
| 💾 Save Changes | Rewrites client_config.toml and client_resolvers.txt with current settings |
| 🚀 Launch VPN | Regenerates files and opens a terminal running MasterDnsVPN |
| 📋 Duplicate | Copies the profile and folder — use for A/B testing different settings |
| 🗑 Delete | Removes the profile JSON and optionally the output folder |
- Click 📋 Duplicate on a working profile
- Change one setting in the copy (e.g. lower Max Upload MTU to
80) - Save both profiles
- Launch each one and compare stability/speed
- Delete the worse one