(SOLVED) Changing to pihole dns kills my internet

Help
41

I followed this thread

I did a ping pi.hole:

anonymous@mint ~ $ ping pi.hole
PING pi.hole (202.71.99.194) 56(84) bytes of data.
64 bytes from 202.71.99.194: icmp_seq=1 ttl=57 time=11.8 ms
64 bytes from 202.71.99.194: icmp_seq=2 ttl=57 time=11.7 ms
64 bytes from 202.71.99.194: icmp_seq=3 ttl=57 time=12.4 ms
64 bytes from 202.71.99.194: icmp_seq=4 ttl=57 time=10.4 ms
64 bytes from 202.71.99.194: icmp_seq=5 ttl=57 time=12.5 ms
^C
--- pi.hole ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 10.490/11.828/12.599/0.763 ms

The 202.71.99.194 ip isn't my wan ip. I've checked. What is going on here? something to do with lighttpd?

nslookup pi.hole:

anonymous@mint ~ $ nslookup pi.hole
Server: 127.0.1.1
Address: 127.0.1.1#53

Non-authoritative answer:
Name: pi.hole
Address: 202.71.99.194

42

I have just setup my pihole, and this is what I am experiencing. My linux box just...never gets an answer. domain gets whitelisted(cached), but DNS_PROBE_BAD_CONFIG comes back.

Router: Archer C3200

Pihole is using ethernet, WLAN disabled. Static IP assigned

Pinging the pihole from linux box: success
Dig google.com from linux box: Connection timed out; no servers could be reached
dig google.com from pihole: Success

Here is my debug token f90abseeaa

Note that it seems to be working over wifi on my macbook...and my android phone.

43

5 posts were split to a new topic: Extreme number of queries passed to Pi-hole - dnsmasq throttling lookups

45

So my pihole is working now, after doing a reboot , the pi.hole/admin web interface works again.

So i'll mark this thread as solved and call it done ! Thanks to both of you @DanSchaper and @deHakkelaar for helping me out throughout !

Really appreciate it :clap::clap::+1::+1:

47

Thanks for this snippet of code, it now shows wlan0 again ! :+1::+1:

48

You can rename any network interface like this by just changing the MAC address: "ATTR{address}=="c4:e9:84:0d:37:1c"

MAC addresses for the interfaces are displayed when doing "ip link show".

49

thanks for the info :+1::+1:

50

If you know which driver is used for the network interface, "sudo lsmod", you wont even need a reboot:

sudo rmmod <DRIVER_MODULE>
sudo modprobe <DRIVER_MODULE>