I recently signed up with a new ISP who gave me a new router and without changing too much on their router I thought I'd rather update my servers IP address instead. It was a static IP address before and was working 100% but after the new static IP address domains don't want to resolve for some reason.
I am running a pi-hole server but not as a DHCP client, the router is still handling that. The routers DNS just points to the pi-hole.
The setup was working before the server IP change so I am not sure what I am missing now. Perhaps someone could shed some light?
/etc/network/interfaces file:
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eno1
iface eno1 inet static
address 192.168.101.110
broadcast 192.168.101.255
netmask 255.255.255.0
network 192.168.101.0
gateway 192.168.101.1
dns-nameservers 192.168.101.1
Not sure if this is relevant?
etc/resolv.conf
Code:
# 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 127.0.0.1
SOLUTION EDIT:
The routes table and /etc/dhcpcd.conf needed to be updated.
If there are any IP's relating to the router or network in /etc/dhcpcd.conf they will need to be updated.
Then check the routes using sudo ip route if there are any IP's that shouldn't be there delete them by executing:
Code:
sudo ip route del default via 192.168.1.254 dev eno1
sudo ip route del 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.100 metric 202
Then add the default gateway:
Code:
sudo ip route add default via 192.168.101.1
Bookmarks