@Bucking_Horn
Alright! That worked out really well and fixed my ip issue no problem.
Wifi is turned off on the pi now and I'm only running ethernet.
Testing it only on my iMac using the DNS of the pi-hole it seems to be working! I've got internet and the admin page works great.
Currently Its only set to OpenDNS and I haven't added or changed anything but what comes standard, but its working! So thank you for the help there. The only thing that seems to be hitting back red now is listed below..
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.31/24 matches the IP found in /etc/pihole/setupVars.conf[✓] IPv6 address(es) bound to the eth0 interface:
fe80::e728:3434:a975:9214 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
[i] Default IPv4 gateway: 192.168.1.1
- Pinging 192.168.1.1...
[✓] Gateway responded.*** [ DIAGNOSING ]: Ports in use
127.0.0.1:5942 teamviewer (IPv4)
[:80] is in use by lighttpd
[:80] is in use by lighttpd
[:53] is in use by pihole-FTL
[:53] is in use by pihole-FTL
[127.0.0.1:4711] is in use by pihole-FTL
[[::1]:4711] is in use by pihole-FTL*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] vserv.bc.cdn.bitgravity.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] vserv.bc.cdn.bitgravity.com is 0.0.0.0 via Pi-hole (192.168.1.31)
[✓] doubleclick.com is 74.125.136.101 via a remote, public DNS server (8.8.8.8)*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] www.ads.revenue.net is :: via localhost (::1)
[✓] www.ads.revenue.net is :: via Pi-hole (192.168.1.31)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
But aside from those two things in bold everything seems to be flowing well.
If there are any additional recommendations I would happily take them.
Thank you for your advice @Bucking_Horn!
Update - I haven't seen a noticeable ad blocking shift just yet from Facebook or simple browsing, but I may need to wait more I would guess. The pi.hole/admin page is working and I can see nearly 1,000 queries hitting and around 120 blocked now, just not sure how to make it more effective really.