ANSWERED Bluetit can connect to a specific server but not a region

[v0e#nuy 0]

With the following config I can connect.

# /etc/airvpn/bluetit.rc
airconnectatboot	server
networklockpersist	on
airusername		v0e#nuy
airpassword		*****
airserver		fleed

But if I specify a country or continent bluetit will exit

airconnectatboot	country
networklockpersist	on
airusername		v0e#nuy
airpassword		*****
aircountry		japan

Log file

Mar 02 13:54:41 bluetit[715]: AirVPN user v0e#nuy successfully logged in
Mar 02 13:54:41 bluetit[715]: Selected user key: Default
Mar 02 13:54:41 bluetit[715]: Starting OpenVPN connection to currently best AirVPN server in Japan
Mar 02 13:54:41 bluetit[715]: Starting OpenVPN Connection
Mar 02 13:54:41 bluetit[715]: OpenVPN3 client successfully created and initialized.
Mar 02 13:54:41 bluetit[715]: Allowing system DNS 10.26.126.1 to pass through the network filter
Mar 02 13:54:43 bluetit[715]: AirVPN Manifest successfully retrieved from server
Mar 02 13:54:51 bluetit[715]: ERROR: Cannot resolve jp3.vpn.airdns.org (Temporary failure in name resolution)
Mar 02 13:54:51 bluetit[715]: Logging out AirVPN user v0e#nuy
Mar 02 13:54:52 bluetit[715]: Session network filter and lock rollback successful
Mar 02 13:54:52 bluetit[715]: Persistent network filter and lock are enabled
Mar 02 13:54:52 bluetit[715]: Sending event 'event_end_of_session'
Mar 02 13:54:52 bluetit[715]: Waiting for pending threads to finish
Mar 02 13:54:52 bluetit[715]: Session network filter and lock rollback successful
Mar 02 13:54:52 bluetit[715]: Persistent network filter and lock are enabled
Mar 02 13:54:52 bluetit[715]: Sending event 'event_end_of_session'

I've tried it with a few countries in Europe. I have also tried it with networklockpersist commented out and networklock set to off with the same result. Any ideas why the connection fails?
 

[Staff 10052]

@v0e#nuy

Hello!

When Bluetit connection mode is set to country, Bluetit calls on domain names to get the destination server IP address (this feature is being completely rewritten and in the next versions domain names will not be used anymore). When a domain name can't be resolved the connection attempt unavoidably fails. In your situation the name resolution is impossible as the system DNS seems unreachable, and actually the DNS server address is private;  it is perhaps a spurious remnant from some previous session:

Quote

Mar 02 13:54:41 bluetit[715]: Allowing system DNS 10.26.126.1 to pass through the network filter
Mar 02 13:54:43 bluetit[715]: AirVPN Manifest successfully retrieved from server
Mar 02 13:54:51 bluetit[715]: ERROR: Cannot resolve jp3.vpn.airdns.org (Temporary failure in name resolution)

You can restore proper DNS settings and/or consider not relying on domain names by creating a white list of your favourite servers in Japan. When a white list of servers is created and the connection mode is set to quick (e.g. airconnectatboot quick in the run control file), Bluetit will select the best rated server in the white list.

Example for bluetit.rc:

airconnectatboot quick
airwhiteserverlist Ainalrami,Albaldah,Bharani,Biham,Fleed,Iskandar,Okab,Taphao

Kind regards