DNS at 10.4.0.1 no longer work...

[avpnhome 3]

Hello

 

Did something change?

 

I have my pfSence configured to enfore using 10.4.0.1 as the DNS.

 

Up to very recently, this worked perfectly, however, at least currently, I'm no longer able to contact a DNS at 10.4.0.1 (while connected, of course!).

 

I'm able to use the currently obtained AirVPN tunnel address as the DNS address, this work fine.  However, that address is dynamic and change each time I connect.  So that's the reason why I use 10.4.0.1 (which is documented in the tech specs on this site).

 

Best regards

 

Edit:

Oh, by the way, that's at Netherland server.  I tried 2 servers.  Currently connected to Alphard.

 

Thanks.

[Staff 9973]

@avpnhome

 

Hello!

 

10.4.0.1 is reachable by DNS queries on Alphard (just remember that it will not reply to pings). The DNS server works fine, so we can't confirm the issue. Any other server for an additional cross check?

 

Kind regards

[hbs 1]

Hello

 

Did something change?

 

I have my pfSence configured to enfore using 10.4.0.1 as the DNS.

 

Up to very recently, this worked perfectly, however, at least currently, I'm no longer able to contact a DNS at 10.4.0.1 (while connected, of course!).

 

I'm able to use the currently obtained AirVPN tunnel address as the DNS address, this work fine.  However, that address is dynamic and change each time I connect.  So that's the reason why I use 10.4.0.1 (which is documented in the tech specs on this site).

 

Best regards

 

Edit:

Oh, by the way, that's at Netherland server.  I tried 2 servers.  Currently connected to Alphard.

 

Thanks.

 

Hi, I am having this very same issue.

 

Did you found a solution?

 

Please, let me know.