Discord not running on Pi-Hole Windows 11 client using PiHole DNS

Expected Behaviour:

Should be able to connect to Discord on Windows 11 client PC running Pi-Hole DNS
Should be able to enter voice chat/channels it does not connect

Actual Behaviour:

Discord does not connect/run on Windows 11 client PC running Pi-Hole DNS
Does not connect voice calls or chat/channels

What i have tried so far:

Pi-Hole is at fault as running normal DNS settings
on the CLIENT pc DOES resolve the issue
I have already tried to disable all adblocking lists still didn't resolve the issue
I have whitelisted all discord domain names
I have synced the time with RTC on Pi-Hole didn't solve the issue
I have restarted Ubuntu Server didn't solve the issue
I tried to reconfigure Pi-Hole still didn't solve the issue
I tried clearing the DNS cache still didn't solve the issue
I am using recursive dns tried cloudflare/google and still doesn't work

Debug Token:

This is usually indicates Pi-hole is not involved on the issue.

When you see the failure, which IP are you using as DNS on your Windows machine?
The router's IP 172.22.16.1? or Pi-hole's IP 172.22.20.152?

1 Like

I'm seeing the exact same thing.
Brand new pihole setup, windows 11, discord application (not website).
My pihole points to my firewall for upstream DNS, out of the box blocklist.

PC pointed to firewall for DNS, no problems.
PC pointed to pihole for DNS, discord app stops connecting.

  • Disable blocking, issue remains!
  • Point DNS back to firewall, discord immediately works.

Through all this, discord in a web browser works just fine, it's only the discord app that loses connection.

Nothing showing as blocked in the audit log, and I've whitelisted any discord URL I can find.

It's clearly something with routing DNS through the pihole breaking the discord app, maybe the discord app is doing some weird DNS tunneling for UDP that's getting caught up in the DNS settings?

To monitor the log in real time, first find the IP address of your PC. Eg 192.168.1.50

In a terminal on your Pi-hole run the following command, replacing this example IP address with that of your PC, in the same format with the backslashes. The character between the IP address and the word blocked is a vertical pipe symbol |

sudo tail -f /var/log/pihole/pihole.log | grep -E "(192\.168\.1\.50|blocked)"

That will show all the queries from your PC along with any responses which are blocked.

Then run the Discord app and see what is showing up. If you see any blocked entries which didn't first have a query from your PC then you can ignore it as it came from a different client on your network. You can whitelist any that look relevant that you've not already caught.

Here's the kind of correlation you're looking for, using a couple of random blocked domains here. Note these are unrelated to Discord, they're just examples from my log here.

Jun 28 12:53:52 dnsmasq[564]: query[A] segment-data-us-east.zqtk.net from 192.168.1.50
Jun 28 12:53:52 dnsmasq[564]: gravity blocked segment-data-us-east.zqtk.net is 0.0.0.0
Jun 28 12:53:52 dnsmasq[564]: query[A] js-sec.indexww.com from 192.168.1.50
Jun 28 12:53:52 dnsmasq[564]: gravity blocked js-sec.indexww.com is 0.0.0.0
Jun 28 12:53:52 dnsmasq[564]: query[A] cdn.cookielaw.org from 192.168.1.50
Jun 28 12:53:52 dnsmasq[564]: gravity blocked cdn.cookielaw.org is 0.0.0.0
Jun 28 12:53:52 dnsmasq[564]: query[A] media.cnn.com from 192.168.1.50
Jun 28 12:53:53 dnsmasq[564]: query[A] registry.api.cnn.io from 192.168.1.50
Jun 28 12:54:06 dnsmasq[564]: gravity blocked dit.whatsapp.net is 0.0.0.0
Jun 28 12:54:26 dnsmasq[564]: query[A] flightaware.com from 192.168.1.50
Jun 28 12:54:31 dnsmasq[564]: query[A] secure.gravatar.com from 192.168.1.50

Breaking these down...

Jun 28 12:53:52 dnsmasq[564]: query[A] segment-data-us-east.zqtk.net from 192.168.1.50
Jun 28 12:53:52 dnsmasq[564]: gravity blocked segment-data-us-east.zqtk.net is 0.0.0.0
... Query from PC which was blocked
... May be relevant and worth unblocking if this was Discord related

Jun 28 12:53:52 dnsmasq[564]: query[A] js-sec.indexww.com from 192.168.1.50
Jun 28 12:53:52 dnsmasq[564]: gravity blocked js-sec.indexww.com is 0.0.0.0
... Query from PC which was blocked
... May be relevant and worth unblocking if this was Discord related

Jun 28 12:53:52 dnsmasq[564]: query[A] cdn.cookielaw.org from 192.168.1.50
Jun 28 12:53:52 dnsmasq[564]: gravity blocked cdn.cookielaw.org is 0.0.0.0
... Query from PC which was blocked
... May be relevant and worth unblocking if this was Discord related

Jun 28 12:53:52 dnsmasq[564]: query[A] media.cnn.com from 192.168.1.50
Jun 28 12:53:53 dnsmasq[564]: query[A] registry.api.cnn.io from 192.168.1.50
... Queries from PC which were not blocked (no followup blocked entries for these domains)
... Not relevant since they were not blocked

Jun 28 12:54:06 dnsmasq[564]: gravity blocked dit.whatsapp.net is 0.0.0.0
... Blocked domain from another client (no preceeding 192.168.1.50 query entry for this domain)
... Not relevant since it was from another client

Jun 28 12:54:26 dnsmasq[564]: query[A] flightaware.com from 192.168.1.50
Jun 28 12:54:31 dnsmasq[564]: query[A] secure.gravatar.com from 192.168.1.50
... Queries from PC which were not blocked (no followup blocked entries for these domains)
... Not relevant since they were not blocked

1 Like

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