New 1 Gbit/s server available (US)

[Staff 9973]

Hello!

We're very glad to inform you that a new 1 Gbit/s full duplex servers located in Chicago, Illinois, is available: Superba.

The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637 and 47107 UDP for WireGuard.

Superba supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard.

Full IPv6 support is included as well.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.

You can check the status as usual in our real time servers monitor:
https://airvpn.org/servers/Superba/
 

Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

[dIecbasC 38]

Is DNS taking time to propagate or is this a change to config generation etc? 
 

% ping -c 1 superba.airvpn.org
ping: cannot resolve superba.airvpn.org: Unknown host

% ping -c 1 sneden.airvpn.org
PING sneden.airvpn.org (68.235.52.35): 56 data bytes
64 bytes from 68.235.52.35: icmp_seq=0 ttl=50 time=65.048 ms

and some addiyional debug info that may be useful

superba.airvpn.org@8.8.4.4 (Default):  Copy results to clipboard 
.			71614	IN	NS	h.root-servers.net.
.			71614	IN	NS	k.root-servers.net.
.			71614	IN	NS	f.root-servers.net.
.			71614	IN	NS	b.root-servers.net.
.			71614	IN	NS	d.root-servers.net.
.			71614	IN	NS	g.root-servers.net.
.			71614	IN	NS	j.root-servers.net.
.			71614	IN	NS	e.root-servers.net.
.			71614	IN	NS	a.root-servers.net.
.			71614	IN	NS	i.root-servers.net.
.			71614	IN	NS	c.root-servers.net.
.			71614	IN	NS	m.root-servers.net.
.			71614	IN	NS	l.root-servers.net.
;; Received 228 bytes from 8.8.4.4#53(8.8.4.4) in 24 ms

org.			172800	IN	NS	a0.org.afilias-nst.info.
org.			172800	IN	NS	b2.org.afilias-nst.org.
org.			172800	IN	NS	c0.org.afilias-nst.info.
org.			172800	IN	NS	a2.org.afilias-nst.info.
org.			172800	IN	NS	b0.org.afilias-nst.org.
org.			172800	IN	NS	d0.org.afilias-nst.org.
;; Received 444 bytes from 192.36.148.17#53(192.36.148.17) in 124 ms

airvpn.org.		3600	IN	NS	pdns03.domaincontrol.com.
airvpn.org.		3600	IN	NS	pdns04.domaincontrol.com.
;; Received 95 bytes from 199.19.57.1#53(199.19.57.1) in 58 ms

airvpn.org.		600	IN	SOA	pdns03.domaincontrol.com. dns.jomax.net. 2023072605 28800 7200 604800 600
;; Received 109 bytes from 173.201.79.51#53(173.201.79.51) in 1 ms

sneden.airvpn.org@8.8.4.4 (Default):  Copy results to clipboard 
.			76667	IN	NS	g.root-servers.net.
.			76667	IN	NS	j.root-servers.net.
.			76667	IN	NS	e.root-servers.net.
.			76667	IN	NS	l.root-servers.net.
.			76667	IN	NS	d.root-servers.net.
.			76667	IN	NS	a.root-servers.net.
.			76667	IN	NS	b.root-servers.net.
.			76667	IN	NS	i.root-servers.net.
.			76667	IN	NS	m.root-servers.net.
.			76667	IN	NS	h.root-servers.net.
.			76667	IN	NS	c.root-servers.net.
.			76667	IN	NS	k.root-servers.net.
.			76667	IN	NS	f.root-servers.net.
;; Received 228 bytes from 8.8.4.4#53(8.8.4.4) in 42 ms

org.			172800	IN	NS	d0.org.afilias-nst.org.
org.			172800	IN	NS	a0.org.afilias-nst.info.
org.			172800	IN	NS	c0.org.afilias-nst.info.
org.			172800	IN	NS	a2.org.afilias-nst.info.
org.			172800	IN	NS	b0.org.afilias-nst.org.
org.			172800	IN	NS	b2.org.afilias-nst.org.
;; Received 437 bytes from 192.58.128.30#53(192.58.128.30) in 51 ms

airvpn.org.		3600	IN	NS	pdns04.domaincontrol.com.
airvpn.org.		3600	IN	NS	pdns03.domaincontrol.com.
;; Received 94 bytes from 199.19.54.1#53(199.19.54.1) in 52 ms

sneden.airvpn.org.	3600	IN	A	68.235.52.35
airvpn.org.		3600	IN	NS	pdns04.domaincontrol.com.
airvpn.org.		3600	IN	NS	pdns03.domaincontrol.com.
;; Received 110 bytes from 97.74.111.51#53(97.74.111.51) in 1 ms

[go558a83nk 362]

2 minutes ago, dIecbasC said:

Is DNS taking time to propagate or is this a change to config generation etc? 
 

% ping -c 1 superba.airvpn.org
ping: cannot resolve superba.airvpn.org: Unknown host

% ping -c 1 sneden.airvpn.org
PING sneden.airvpn.org (68.235.52.35): 56 data bytes
64 bytes from 68.235.52.35: icmp_seq=0 ttl=50 time=65.048 ms

been this way for years that some Air servers didn't resolve with that domain pattern but that's the one I always try to use so I forget the "proper" way.  apparently it's superba.airservers.org

[dIecbasC 38]

Thanks for the insight, I haven't seen this before. I noticed it because the config generator didn't provide a non-resolved config file when requested too. 
 

[go558a83nk 362]

6 minutes ago, dIecbasC said:

Thanks for the insight, I haven't seen this before. I noticed it because the config generator didn't provide a non-resolved config file when requested too. 
 

I always get resolved hosts configs anyway so that DNS isn't required for connection.

[Staff 9973]

3 hours ago, go558a83nk said:

been this way for years that some Air servers didn't resolve with that domain pattern but that's the one I always try to use so I forget the "proper" way.  apparently it's superba.airservers.org

Hello!
Correct. The old <servername>.airvpn.org for the entry-IP address 1 has been maintained for backward compatibility for some years only on old servers for a smoother transition. New server domain names (for all servers) follow the current documentation for example https://airvpn.org/faq/servers_ip/

Kind regards
 

[go558a83nk 362]

10 minutes ago, Staff said:

Hello!
Correct. The old <servername>.airvpn.org for the entry-IP address 1 has been maintained for backward compatibility for some years only on old servers for a smoother transition. New server domain names (for all servers) follow the current documentation for example https://airvpn.org/faq/servers_ip/

Kind regards
 

If you could only get a pattern like

superba3.airservers.org

or

superba3.vpn.airdns.org

working.   But it seems requesting an alternate entry IP only works with regions or nations.

[Staff 9973]

@go558a83nk

Hello!
Yes, the lack of entry-IP addresses 2, 3 and 4 on server domain names persists since 2010 and probably does not make sense anymore now. We'll think about it.
Kind regards
 

[eStolkYw 13]

This is awesome news! I had just posted about this not even a week ago and you guys already added another server. Problem solved. Love to see it. Keep up the good work!