So I built: Pi-hole
-
@JaredBusch said in So I built: Pi-hole:
@gjacobse said in So I built: Pi-hole:
@NerdyDad said in So I built: Pi-hole:
@hobbit666 Point your home DNS to your pihole on vultr.
Correct. This is all that is needed. @scottalanmiller has a PiHole setup for NTG,.. All that was needed post setup is to replaced the first DNS entry in my ERL router to the IP of the instance.
However that said.. down the road I could see MY needing to update this as I don't have a static IP. It may or may not change post restarts months down the road.
Change what? Did you setup some kind of firewall rule to only allow your IP to access it? Because there is no restriction by default.
No - nothing like that. I just expect that when rebooted the IP may change.
-
@gjacobse said in So I built: Pi-hole:
@JaredBusch said in So I built: Pi-hole:
@gjacobse said in So I built: Pi-hole:
@NerdyDad said in So I built: Pi-hole:
@hobbit666 Point your home DNS to your pihole on vultr.
Correct. This is all that is needed. @scottalanmiller has a PiHole setup for NTG,.. All that was needed post setup is to replaced the first DNS entry in my ERL router to the IP of the instance.
However that said.. down the road I could see MY needing to update this as I don't have a static IP. It may or may not change post restarts months down the road.
Change what? Did you setup some kind of firewall rule to only allow your IP to access it? Because there is no restriction by default.
No - nothing like that. I just expect that when rebooted the IP may change.
Vultr is a VPS provider. They don't change IP addresses of deployed systems.
What are you talking about?
-
@JaredBusch said in So I built: Pi-hole:
@gjacobse said in So I built: Pi-hole:
@JaredBusch said in So I built: Pi-hole:
@gjacobse said in So I built: Pi-hole:
@NerdyDad said in So I built: Pi-hole:
@hobbit666 Point your home DNS to your pihole on vultr.
Correct. This is all that is needed. @scottalanmiller has a PiHole setup for NTG,.. All that was needed post setup is to replaced the first DNS entry in my ERL router to the IP of the instance.
However that said.. down the road I could see MY needing to update this as I don't have a static IP. It may or may not change post restarts months down the road.
Change what? Did you setup some kind of firewall rule to only allow your IP to access it? Because there is no restriction by default.
No - nothing like that. I just expect that when rebooted the IP may change.
Vultr is a VPS provider. They don't change IP addresses of deployed systems.
What are you talking about?
Having not used them before - yes @NTG and @scottalanmiller does. but not myself. I didn't know. If it doesn't change,.. it doesn't. Nothing else I need to do.... moving on.
-
so - I have this show up.. since my system is open.
Should they be blacklisted? or allowed?
-
@gjacobse said in So I built: Pi-hole:
so - I have this show up.. since my system is open.
Should they be blacklisted? or allowed?
That's not what that blacklist means. I am assuming those IP addresses are not yours.
-
@JaredBusch said in So I built: Pi-hole:
@gjacobse said in So I built: Pi-hole:
so - I have this show up.. since my system is open.
Should they be blacklisted? or allowed?
That's not what that blacklist means. I am assuming those IP addresses are not yours.
They are not. And you are right. In this case, not blacklist.. FW maybe..
-
@gjacobse said in So I built: Pi-hole:
@JaredBusch said in So I built: Pi-hole:
@gjacobse said in So I built: Pi-hole:
so - I have this show up.. since my system is open.
Should they be blacklisted? or allowed?
That's not what that blacklist means. I am assuming those IP addresses are not yours.
They are not. And you are right. In this case, not blacklist.. FW maybe..
Correct. If that is what you want, then you need to look at restricting access to the Pi-Hole instance in the first place.
There is a thread on that here somewhere. But That is more work than it is worth IMO.
What I would do is setup the Vultr Firewall and add an allow for your network. Use ARIN to look up the range your ISP uses. Then add a drop all for all other traffic on port 53.
If you expand this to family, add their IP block as well.
Not 100% solid, but much less likely to be randomly hit.
-
@JaredBusch said in So I built: Pi-hole:
There is a thread on that here somewhere.
https://mangolassi.it/topic/15008/pihole-for-friends-and-family @gjacobse
-
@aaronstuder said in So I built: Pi-hole:
@JaredBusch said in So I built: Pi-hole:
There is a thread on that here somewhere.
https://mangolassi.it/topic/15008/pihole-for-friends-and-family @gjacobse
That thread. Don’t do it, as it is too much of a pain in the ass.
Just whitelist the CIDR of your ISP.
-
Where is @scottalanmiller to chime in that isn't the purpose of DNS?
-
@BRRABill said in So I built: Pi-hole:
Where is @scottalanmiller to chime in that isn't the purpose of DNS?
Careful, sounds like he's already infected you!
-
This post is deleted! -
@travisdh1 said in So I built: Pi-hole:
@BRRABill said in So I built: Pi-hole:
Where is @scottalanmiller to chime in that isn't the purpose of DNS?
Careful, sounds like he's already infected you!
Yes but I can't yell at people as good as him.
