[Solved] Various Issues after re-install

Asus RT-AC87U . I don't know if it does, I don't believe so?

Okay, can you run ipconfig on the Windows box and list the DNS servers that Windows is trying to use?

ipconfig /all will do that.

   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, April 26, 2020 3:42:30 PM
   Lease Expires . . . . . . . . . . : Thursday, April 30, 2020 12:11:35 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   ....
   DNS Servers . . . . . . . . . . . : 192.168.1.51
                                       192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

That's the problem. The router (DHCP Server) is sending itself as a DNS server. Windows will use both DNS servers, there is no primary and secondary or backup DNS servers.

Very weird. I have it set in the LAN DHCP Server (in the Router) as the DNS set to 192.168.1.51 (PiHole)

DHCP Server = Router
DNS Server = PiHole

A number of routers will hardcode themselves as DNS servers when you set them up for DHCP servers. I don't see any option to disable that in your router, you may have to use the DHCP server in Pi-hole instead, this situation is the reason we went with that feature for Pi-hole.

2 Likes

Asus again.
Can try flash Merlin firmware if want to continue using Asus DHCP with Pi-hole:

Thought about Merlin, wasn't sure the pros/cons of using PiHole vs Router as the DHCP server.

Tried setting up the DHCP on the PiHole and when I try to add a static lease I get this..

Error
There was a problem applying your settings.
Debugging information:
PHP error (2): fopen(/etc/dnsmasq.d/04-pihole-static-dhcp.conf): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/savesettings.php:84

Seems to have added the new static IP tho, just a weird error?

Does that file exist with the configuration you wanted?

We can check again with a new pihole -d token.

https://tricorder.pi-hole.net/aa3h186pz0

3 Likes

Yep that seems to match, added a second one and no error.

Is it normal to have a different IP in the DHCP leases for the PiHole (showing 192.168.1.75) even though I have a Static DHCP lease for the PiHole (192.168.1.51)? Both seem to resolve to the PiHole, I just figured they would be the same?

How are you connected ?

ip -4 a

tail /etc/dhcpcd.conf

journalctl --no-pager -u dhcpcd | tail -20

Ps. after the Pi-hole installer done its job, the Pi-hole host itself doesnt depend on DHCP anymore (see output for above two commands).

pi@pihole:~ $ ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    inet 192.168.1.51/24 brd 192.168.1.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    inet 192.168.1.75/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 83988sec preferred_lft 73188sec

pi@pihole:~ $ tail /etc/dhcpcd.conf
#static routers=192.168.1.1
#static domain_name_servers=192.168.1.1

# fallback to static profile on eth0
#interface eth0
#fallback static_eth0
interface eth0
        static ip_address=192.168.1.51/24
        static routers=192.168.1.1
        static domain_name_servers=127.0.0.1

pi@pihole:~ $ journalctl --no-pager -u dhcpcd | tail -20
Apr 29 16:36:09 pihole dhcpcd[407]: eth0: adding address xxxxxxx
Apr 29 16:36:09 pihole dhcpcd[407]: eth0: probing address 192.168.1.51/24
Apr 29 16:36:10 pihole dhcpcd[407]: wlan0: soliciting an IPv6 router
Apr 29 16:36:10 pihole dhcpcd[407]: eth0: soliciting an IPv6 router
Apr 29 16:36:14 pihole dhcpcd[407]: wlan0: probing for an IPv4LL address
Apr 29 16:36:14 pihole dhcpcd[407]: wlan0: DHCP lease expired
Apr 29 16:36:14 pihole dhcpcd[407]: wlan0: soliciting a DHCP lease
Apr 29 16:36:14 pihole dhcpcd[407]: eth0: using static address 192.168.1.51/24
Apr 29 16:36:14 pihole dhcpcd[407]: eth0: adding route to 192.168.1.0/24
Apr 29 16:36:14 pihole dhcpcd[407]: eth0: adding default route via 192.168.1.1
Apr 29 16:36:18 pihole dhcpcd[407]: wlan0: using IPv4LL address 169.254.124.7
Apr 29 16:36:18 pihole dhcpcd[407]: wlan0: adding route to 169.254.0.0/16
Apr 29 16:36:22 pihole dhcpcd[407]: wlan0: no IPv6 Routers available
Apr 29 16:36:23 pihole dhcpcd[407]: eth0: no IPv6 Routers available
Apr 29 16:36:26 pihole dhcpcd[407]: wlan0: offered 192.168.1.75 from 192.168.1.51
Apr 29 16:36:26 pihole dhcpcd[407]: wlan0: probing address 192.168.1.75/24
Apr 29 16:36:31 pihole dhcpcd[407]: wlan0: leased 192.168.1.75 for 86400 seconds
Apr 29 16:36:31 pihole dhcpcd[407]: wlan0: adding route to 192.168.1.0/24
Apr 29 16:36:31 pihole dhcpcd[407]: wlan0: adding default route via 192.168.1.1
Apr 29 16:36:31 pihole dhcpcd[407]: wlan0: deleting route to 169.254.0.0/16

Well you seem to be connected via copper as well as WiFi so doesnt seem unusual to show up twice ?

You have active IPs on wlan0 and eth0 interfaces on the Pi.

Unless there is a need to have two active interfaces on the Pi, it is simpler and easier to manage IPs if you use only one.

Thanks, noticed that and disabled WiFi.

I'm still noticing the Connection Reset error page on calling a page, right before it auto reloads and actually loads the site.. disabled Wifi on the PiHole and haven't seen the issue so far.. let's hope it's resolved, otherwise any ideas what it may be?

Update: Same issue with connection reset appearing still :expressionless:

This is sounding like a client issue. Is this only with that browser, and only on that client? Or is this with all browsers on that client, or all browsers on all clients?

Thanks everyone, I'll look into the Connection reset issue, seems to only be my machine but I only have virtual hosts connections (they are inactive), then WiFi but I'll figure it out.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.