Asus AC68

[deHakkelaar]

Looks good.
Run below ones on Pi to enable the sshd daemon and start sshd for next time you lose VNC:

sudo systemctl enable ssh

sudo systemctl start ssh

From the pj-selgbuild client, you should now be able to ssh into Pi with:

ssh -l pi 10.1.1.3

Next configure Pi-hole to use the new 10.1.1.3 address by running reconfigure:

echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf

pihole -r

Reboot Pi to be sure and test from Pi and a client:

nslookup pi.hole 10.1.1.3

If that all works, you can try switching DHCP service from router to Pi-hole:

How do I use Pi-hole's built in DHCP server (and why would I want to)?

Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page, which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. …

After the switch, reboot the pj-selgbuild client and run below ones on it to see if it picked up the new DHCP settings including the Pi DNS IP:

ip a

cat /etc/resolv.conf

nslookup pi.hole

If that looks good, reboot your other client devices to renew DHCP lease so they too start using the new DHCP service + ad blocking through Pi-hole's DNS.