AndIodine
About
- autodetect
- NULL
- TXT
- SRV
- MX
- CNAME
- A
- Network default
- Custom
- Tunnel Endpoint
Add Account
Cancel
Close Tunnel
Password
Tunnel Toplevel Domain
Tunnel Nameserver
Nameserver Mode
Nameserver Address
Configuration Profile Name
Use default Nameserver for tunneling
Name for this configuration.
The dns traffic will be sent as queries for subdomains under _topdomain_. This is
normally a subdomain to a domain you own. Use a short domain name to get better throughput. If nameserver is the
iodined server, then the topdomain can be chosen freely. This argument must be the same on both the client and
the server.
Use lazy mode for improved performance and decreased latency. A very small minority of
DNS relays appears to be unable to handle the lazy mode traffic pattern, resulting in no or very little data
coming through. The iodine client will detect this and try to switch back to legacy mode, but this may not
always work. In these situations use this switch.
If set used, iodine will try getting the public IP address of the iodined host and test
if it is reachable directly. If it is, traffic will be sent to the server instead of the DNS relay.
The nameserver to use to relay the dns traffic. This can be any relaying
nameserver or the server running iodined if reachable. This field can be given as an IP address, or as a
hostname. This argument is optional, and if not specified the default system Nameserver will be used.
This field is optional. Only the first 32 characters will be used
Source of the Nameserver to use for name resolution while tunnel is
active
Custom Nameserver IP-Address to set if Nameserver-mode is "Custom"
DNS request type override. By default, autodetection will probe for working
DNS request types, and will select the request type that is expected to provide the most bandwidth. However, it
may turn out that a DNS relay imposes limits that skew the picture, which may lead to an "unexpected" DNS
request type providing more bandwidth. In that case, use this option to override the autodetection. In
(expected) decreasing bandwidth order, the supported DNS request types are: NULL, TXT, SRV, MX, CNAME and A
(returning CNAME). Note that SRV, MX and A may/will cause additional lookups by "smart" caching nameservers to
get an actual IP address, which may either slow down or fail completely.
Maximum size of upstream hostnames. Valid values are from 100 to 255.
Default is 255. Decrease if you find some DNS relays answer to full-length queries unreliably giving widely
varying results of fragment size autoprobe.
Response fragment size. Autoprobed when set to 0 which is a default.
Enable
Configuration is incomplete
Cannot start VPN Service, VPN-Thread is already running
VPN Thread exited unexpected
Can\'t open DNS Socket
Handshake failed
Unknown Error. Code %d
Unknown Error. Reason: %s
No valid IPv4 name servers detected
Failed to create tunnel network device
No active network
Idle
Warning
Error
Configure this Connection Profile
Connection Configuration
Set default Route for the tunnel device
Create DNS Tunnel from Configuration named %s
New Account
About
Delete