|
What I did was to setup yet another RPi in front of ISP router as my own router and of course the other as DNS/PiHole.
So basically I had my other local network that was having my RPi as a gateway to "ISP local network" that had gateway to the internet.
It is complicated setup so only if someone really really wants to shield yourself from ISP and has enough time to set it up, for me it was easy because I am quite into networking, but I can imagine for someone not so much into it, can take quite some time.
|
|
|
|
|
Yes, yes, and yes. 
Also have Comcast, my own modem, a separate wireless router, and Pi Hole (PH). The PH is wired to the router.
My router handles the DHCP and I have the DNS pointing to the PH. The PH handles forwarding, configured to Cloudflare’s service and secondly to Google’s service. I DO NOT use Comcast’s DNS.
Comcast wants me to replace my modem/router for better service, but I haven’t found one I like.
My setup seems to work well. Stable for over 2 years.
Cc @dandy72
Time is the differentiation of eternity devised by man to measure the passage of human events.
- Manly P. Hall
Mark
Just another cog in the wheel
|
|
|
|
|
I'm thinking of upgrading from my 1GB up/down pipe to 2GB up/down
My question is, can I even run a pi-hole on a multi-gigabit gateway or will it bottleneck?
That's why I haven't run one.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
DNS resolution only takes up so much time; once that's done and a large download is initiated, it gets out of the way.
What are you doing that would make 2gbps up/down worth it? 
And then your router, and whatever machine(s) you're doing your downloads from, would also all need to support it. You can't assume all of the latest hardware does automatically. Heck they still sell 100mbps switches brand new.
|
|
|
|
|
I've never actually seen a Pi-Hole. I've only heard about them. I didn't know how they worked. I thought they were a full on network pass through filter, not just DNS.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Pi-Hole is actually software. It might have originated for (or have been designed to run on) rPI, but I run it on a small Linux VM.
|
|
|
|
|
Ohhhhhhhhhh
I'm thinking of something maybe related. There's a little RPi dongle that plugs into your network you can do filtering and such with.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
I did some network switching around recently and learned how important the cables are. My upstream is fiber optic.
Find a good bandwidth tester. Start with the simplest setup with the shortest cables. Find the fastest speed even switching cables in the simplest setup to see if there is any impact.
Test every step of every change.
Why bother with a 1gig switch if you crater your throughput somewhere along the path.
|
|
|
|
|
Glad you got it going with the domain controller. Just to add some umph to your umphness...
The modem/router may or may not have a DNS server (most don't), but that's not the same thing as its DNS settings, which most likely will point to your ISP's DNS. So, in effect it would just be a pass through and your DNS look ups are still using the ISP's servers directly.
Just guessing in the past, you had that VM set up to talk to your ISP's DNS servers and then your machine's DNS settings pointing to the VM. So, in effect, it was acting kinda like a domain controller.
Pihole is awesome btw. I'll stick it on a cheapo raspberry pi though. Works like a champ. I'll set the pi up to use either my ISP's DNS servers directly or just use Google's. Then I'll configure my machines (or domain controller) to use the raspberry pi as its DNS server. Installing Pihole automatically includes installing DNS software, including caching and everything.
Just FYI, if you ever into DNS issues with your ISP, Google offers free to use ones to bypass any ISP wonkiness. Primary 8.8.8.8 and secondary 8.8.4.4. Seriously, do an ARIN search on it, those are Google IPs.
Jeremy Falcon
modified 2 days ago.
|
|
|
|
|
My previous ISP only provided me with a modem (no router functionality), so I used my own router and specified Pi-Hole's static IP for its primary DNS.
Since that router is now gone, and my current ISP's router doesn't allow me to specify an alternate DNS, Pi-Hole essentially stopped working then.
But as I said, when I can afford some down time, I'll set up the ISP's router in bridge mode and bring my old router back online to take over.
[Edit]
And yes, I've been relying on Google's DNS for years. I see no other reason to look for alternatives.
[Edit]
Since everybody should be using Google's DNS anyway, why don't they do us all a big favor and implement their own equivalent Pi-Hole functionality? Oh, wait, they're in the ad business, that's the last thing they'd ever do...
modified yesterday.
|
|
|
|
|
dandy72 wrote: ...why would the queries not go to Pi-Hole first and foremost? Now my configuration is:
Oh, to actually answer your question... 
It should do that. The only reason it would only default to a secondary is if the primary is down. So maybe the Pi had issues. Can be confirmed with an nslookup. Or maybe (unlikely but just shooting in the dark) windows made the DC settings take priority?
dandy72 wrote: a) The DC (with Pi-Hole's IP under Forwarders)
If you're going to use a DC this is the right way to do it anyway. Otherwise you'd be setting up DNS for every machine you logged in to, so may as well just do it on the DC. Unless you want to shut your DC down that is.
You shouldn't need forwarders though (I think, haven't used a DC in over a decade), your Pi has its own IP on the local network. For DNS, make sure they're static IPs though. But, if your DC is setting the configuration for DNS, an IP is an IP is an IP.
Jeremy Falcon
|
|
|
|
|
DNS is so crazy nowadays.
A couple things to note that wasn't mentioned.
Default settings for computers are to accept whatever DNS server that the DHCP server gave them when connecting to a network. So it is, without doubt, the ISP-provided router that is choosing to give their choice of DNS instead of your choice (the Pi) at the moment your machine requests an IP address from the router's DHCP server.
Probably your Domain Controller setup fixes this by being the gateway and/or DHCP server for the network, and that allows you to choose what you wish.
Do note that cable companies like Comcast *want* you to have their all-in-one modem/router combos, but they still *allow* you to have home-owned modem devices (certain ones are allowed, but they don't typically restrict it except by DOCSIS version capabilities). Bonus -- you don't pay the rental fee for having their all-in-one combo, Bonus 2 -- you can control what your router actually does.
When you have your own device, you can easily just set in the router config what DNS server will get returned to DHCP clients, and done deal.
Note that on computer side, you can override this with manual configuration per network (But Windows 11 is actually broken currently, and gets confused over whether this is set local to a network or globally for all networks -- Sigh -- that's a fun one to fix if you've ever had it manually set and Win11 UI won't allow you to change it, and nothing works to reset it)
Further, a browser can choose to resolve domain names differently as well, using DNS over HTTP -- it may also be that you have to turn this off to get things to work as expected.
A huge headache all around. Remember when the internet was simpler and well-designed hierarchy?
|
|
|
|
|
Tiger12506 wrote: accept whatever DNS server that the DHCP server gave them when connecting to a network. So it is, without doubt, the ISP-provided router that is choosing to give their choice of DNS instead of your choice (the Pi) at the moment your machine requests an IP address from the router's DHCP server.
Although I have DHCP enabled in my ISP's router, all systems connected to my network - except maybe for my phone - have been given an explicit IP address, locally. Still, based on what I've seen, it did look like the ISP's router got first dibs, despite DNS on any given computer specified as Pihole -> DC -> Router. Until I set up the forwarder on the DC to point to the Pihole machine, and then I removed Pihole from the explicit DNS entry on individual endpoints.
Tiger12506 wrote: Remember when the internet was simpler and well-designed hierarchy?
Was it, ever?
Simpler, maybe, but we were dealing with different problems.
|
|
|
|
|
Marking your own message as [Spam] does not grant you permission to blatantly violate the one rule shown in red at the top of the lounge.
Away with you!
|
|
|
|
|
I've probably watched a French video a few weeks ago on YouTube. Ever since, YouTube has been showing me a mixture of French and English ads (maybe 50-50). At least I'm attributing this fact to the one video I might've watched, I see no other reason it might be showing me French ads.
I do NOT log into YouTube, so there's no language preference for me to set. I have no language set in my browser (Edge) other than the default US-English.
And at some point starting this week, every time I go to www.microsoft.com, it explicitly sends me to www.microsoft.com/fr-ca/. Again, despite the fact that I have no other language set in my browser. Or the OS's Regional Settings page.
I could try to clear cookies, but that's an all-or-nothing type of thing - I'd probably lose a lot of tweaks for various sites I'd rather not go through again. As far as I know, you can't clear cookies specifically for one site only. Or can you?
I've just tried InPrivate mode with Edge and going to www.microsoft.com. It sent me to www.microsoft.com/en-ca, so it knows I'm in Canada, but at least the page is in English. That, to me, tells me it's got to be some data in a cookie.
How might I go about finding, then removing that cookie...? Or does someone have a better suggestion?
(and no, I'm not changing browsers for that, TYVM)
|
|
|
|
|
You're forgetting one teensy thing, geolocation of your IP. If the cookie doesn't exist, your country can be guessed by your IP address.
|
|
|
|
|
Jinx! Didn't see your post before I replied.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Bah! I would have beat you to it if I wasn't eating breakfast while I type.
|
|
|
|
|
Location doesn't infer language. It's the language I object to.
|
|
|
|
|
It's got you pegged for Quebec and the language is making certain assumptions about your location.
|
|
|
|
|
All geolocators I've seen since I've been on the internet (94? 95?) have shown my city as being my ISP's...which operates near Toronto, Ontario.
|
|
|
|
|
They do change. It used to be my location was pegged at about 50 miles away. Now it's got me down to about 6 miles.
|
|
|
|
|
Ok.
Riddle me this: Browsers on other systems within my LAN keep me on www.microsoft.com. Only one of them forwards me to www.microsoft.com/fr-ca.
Yet all my systems, from MS's perspective, should originate from the same public IP.
I'm not trying to be contradictory, I welcome the thoughts.
|
|
|
|
|
Ya got me there. I have no idea on that one.
|
|
|
|
|
Been a while since I messed with this but I suspect that finding your location from your IP is still a service that one can pay for.
So one place is using a service that pegs it to one location. And the others use something different.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
