Ask about IP request from router

@Azndfc The ISP can send you to a fake page by changing the DNS record on you, but you can’t do that the other way around so that the ISP thinks you are going to another page. If it was that simple then there would be no need for VPN.

You can only either actually go to the page directly, or not show it to the ISP, no other way.

@sammo
Actually this is good. If the VPN does not push DNS, then you end up with no DNS and can’t access any page. The user is then forced to set the DNS manually in the settings. If you backup the DNS, you are just backing up the ISP one in most cases.

All the mayor VPN providers usually ask you in the setup instructions to manually set the DNS to theirs.

The recommended procedure is:

  1. Use the scripts, they will give you the latest DNS from the VPN, since it can change at any time. People are not going to go onto their DNS provider page to check if the DNS is the same every time they connect. If the DNS were to change, an attacker would be able to use the old IP and force you to other pages. You want the correct DNS at all times.

  2. If the scripts fail, ie you end up not being able to access any page, then as you saw it means your provider is not pushing the DNS settings, and you have to set it manually but also keep an eye for when it changes.

But a novice will scream my vpn is not working…

#!/bin/sh
mv /tmp/resolv.conf.auto /tmp/resolv.conf.auto.hold
echo $foreign_option_1 | sed -e ‘s/dhcp-option DOMAIN/domain/g’ -e ‘s/dhcp-option DNS/nameserver/g’ > /tmp/resolv.conf.auto
echo $foreign_option_2 | sed -e ‘s/dhcp-option DOMAIN/domain/g’ -e ‘s/dhcp-option DNS/nameserver/g’ >> /tmp/resolv.conf.auto
echo $foreign_option_3 | sed -e ‘s/dhcp-option DOMAIN/domain/g’ -e ‘s/dhcp-option DNS/nameserver/g’ >> /tmp/resolv.conf.auto

[ -s /tmp/resolv.conf.auto ] || {
# 8.8.8.8 or 1.1.1.1 to /tmp/resolv.conf.auto
}

your mileage may vary.