I hereby claim:
- I am al-azif on github.
- I am alazif (https://keybase.io/alazif) on keybase.
- I have a public key ASC9rBLX1P39vfqfmOS3Y5qVLf2EnL2VxLfapuGi1tsg3Ao
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
# 0. Use `crtl+h` and replace `{{HOST}}` with the IP address of a server you | |
# control and want to direct the traffic to. Or Just use `0.0.0.0` to block it. | |
# | |
# 1. Log into your Pi-hole device and move this file into the `/etc/dnsmasq.d/` | |
# directory. Feel free to rename it. | |
# | |
# 2. Run the command `pihole restartdns` | |
# Redirects Nintendo Landing Page Domains | |
address=/ctest.cdn.nintendo.net/{{HOST}} |
REDIRECT_IPV4
address to your computer's IPROOT_DOMAIN
and ROOT_DOMAIN_PATH
to where you want to redirect to (Change redirect type if necessary)docker compose up -d
from cmd
in the directory with this fileSo I feel like I need to address this specifically because there is an incredible amount of incorrect info being passed around, especially here.
No, the DNS server are both up and running. Request forwarding is disabled for non-sponsors, due to it being abused. You can read more info about the situation that caused open forwarding to be removed here. For non-sponsors connection tests will pass and will allow access to the exploit host that's running on the same server. You can also access resources directly by IP address.
So I gotta have a minute of real talk where I'll explain the issues and why no automated solution will really solve the issue. Do not just read part of this, do not take someone else’s, often incorrect, TL;DR as what was actually said.
There's an extremely large amount of IPs trying to use the DNS for browsing on their PC (or w/e). Literally millions of requests a second. I cannot separate these out without it becoming a full time job just watching traffic and reacting. This will also cost an amount, monthly, that I'm not willing to pay for a free service. I have a way for it to work, but a fair amount of people aren't going to like it.
These are the issues I'm running into:
192.168.1.*
Lots of stuff going on in my personal life the last few months. An immediate family member went from completely independent, at the end of February, to bedridden in a two week span and given a death sentence diagnoses. Part of their wishes was minimal people knowing/visiting during the process, but they passed this Monday and the obituary was published today (Some people I know IRL know *this* is me so I couldn't post any of this before). They were a huge part of my life, a central part of my entire family, all my friends knew them, and I had seen them nearly daily since I stopped traveling for work three years ago. So this is a huge event for me. A few people in the PS community knew about it because I didn't have time to try and make some made up excuse for my absence the times I was able pop online the last few months, I appreciate they kept it to themselves (If they did... I haven't been around to see if they did).
Add to this there's been a local "natural" disaster on their property, that I'm now part