Jump to content
Not connected, Your IP: 54.90.236.179
Sign in to follow this  
hmmmm

[SOLVED] I didn't pay to be filtered.

Recommended Posts

"Sorry, but bayfiles.com is blocked on this network.

This site was categorized in: File storage

Contact your network administrator"

What is this garbage???

It's on the .de host and at least one of the Dutch ones.

Share this post


Link to post

"Sorry, but bayfiles.com is blocked on this network.

This site was categorized in: File storage

Contact your network administrator"

What is this garbage???

It's on the .de host and at least one of the Dutch ones.

Hello!

We strictly respect Net Neutrality, so no website is blocked from our network. We have just checked that Omicron (the german server) and the 4 servers in the Netherlands (Castor, Leonis, Lyra and Orionis) can all access bayfiles.com without problems. Are you sure to be connected to one of them while you receive that message?

Kind regards

Share this post


Link to post

It seems that you are using opendns

Change dns and try again

Ah, yeah — OpenDNS. I have no idea why I though of Cloudflare. Thank you.

Share this post


Link to post

@hmmmm

It seems that you are using opendns

Change dns and try again

Hello!

The remark from blknit suggests that you are using a Windows system. First of all, flush the DNS resolver cache (only if you have Windows). If the problem is not fixed after the flush, you might check that:

- you don't have DNS leakage on your system (you may use http://www.dnsleaktest.com)

- your system is not compromised (scan for malware, check hosts file)

- your system, after the connection, is capable to contact the VPN DNS address (see here for further details: https://airvpn.org/specs).

We're looking forward to hearing from you.

Kind regards

Share this post


Link to post

A quick addition:

There is a domain/categories blocking feature that everyone can configure using opendns

Among the categories that everyone can block you can find : pornography, file sharing, adware, proxy ...

If there are 20 users connected to Omicron server they share all the same exit ip.

If one of the users configure the opendns blocking feature, all users connected to the same server are affected.

So.. no more opendns for me while i'm connected to airvpn

Best regards

Share this post


Link to post

A quick addition:

There is a domain/categories blocking feature that everyone can configure using opendns

Among the categories that everyone can block you can find : pornography, file sharing, adware, proxy ...

If there are 20 users connected to Omicron server they share all the same exit ip.

If one of the users configure the opendns blocking feature, all users connected to the same server are affected.

So.. no more opendns for me while i'm connected to airvpn

Best regards

Hello!

Thanks. Also please note that if you don't use internal Air resolution, you might not be able to take advantage of the anti-ICE/DHS USA censorship system: since it is based on domain name seizure at VeriSign/ICANN etc. level, no matter which DNS that recognizes ICANN authority you use, you will always be censored. On Windows system, using custom DNS rises probability of DNS leakage (we are investigating - Windows users can get rid of this potential leakage by blocking outgoing packets from svchost.exe NOT from IP range 10.4.0.0->10.9.255.255, or by blocking connections from network card IP address to port 53 when destination IP is not AirVPN entry-IP address).

Kind regards

Share this post


Link to post

I didn't notice about internal Air resolution.

My linux box does not update the dns after connection.

As soon i come back home i will try adding the following lines to the connection script :

up /etc/openvpn/update-resolv-conf

down /etc/openvpn/update-resolv-conf

Best regards

Share this post


Link to post

It worked

steps are :

Install resolvconf :

sudo aptitude install resolvconf

Modify the air.ovpn fine adding at the beginning (before client) the following lines :

script-security 3

up /etc/openvpn/update-resolv-conf

down /etc/openvpn/update-resolv-conf

After the connection this is the "new" resolv.conf

cat /etc/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)

# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

nameserver 10.8.0.1

a quick check with dig :

;; Query time: 111 msec

;; SERVER: 10.8.0.1#53(10.8.0.1)

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  

×
×
  • Create New...