Allow DNS (un)blocking - Githubissues

GoogleCodeExporter commented 8 years ago

It would be great to see PeerBlock allowing domains in their black and
white lists, so that certain domains can be blocked or unblocked. That way
PB could also be used with e.g. dynDNS.

Original issue reported on code.google.com by messo...@gmail.com on 5 Dec 2009 at 7:24

GoogleCodeExporter commented 8 years ago

this is obviously not a defect report but a feature request ;)

Original comment by messo...@gmail.com on 5 Dec 2009 at 7:26

GoogleCodeExporter commented 8 years ago

This would be a real useful feature in my view also. I use peerblock to block 
certain ip ranges within dc++. I allow specific hub ips to connect to me only 
ie 
people whom I trust. However from time to time their ip will change when 
rejoining 
our hub. This means that I have to change the allowed list for some of the 
users and 
allow the new ip again. By linking their ip to a dyndns address this could be 
solved. If peerblock which is a great software may I add had a feature which 
would 
allow you to add a dyndns address it would make for the perfect setup for such 
a 
scenario. This is not a bug or defect as messo has already stated but perhaps 
somethign to  consider in the future? Love your software its absolutely superb! 
Keep 
up the great work!

Original comment by matthaus...@gmail.com on 6 Dec 2009 at 1:02

GoogleCodeExporter commented 8 years ago

Hmm, the difficulty here would be would be that as y'all have identified, IP
addresses can and will change.  Since PeerBlock operates at an IP address 
level, we'd
need to every so often query for what IP address a DynDNS type name maps to.  We
wouldn't want to check this for every single packet, because that would just be
silly.  So what we'd have to do would be to check every so often, and then 
cache the
result until the next time.  This means that you'd have a window during which we
could be allowing the wrong IP address...

Note that I'm not nixing the idea, I'm just trying to make sure we capture some 
of
the issues we could be confronted with if we decide to start implementing this
feature request.

Original comment by peerbloc...@gmail.com on 20 Jan 2010 at 12:10

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 8 years ago

I also don't see any way to do this without either updating a list of IP's for a
domain or doing a Reverse DNS lookup on every packet (which would kill your 
machine)

Original comment by brent.ne...@gmail.com on 20 Jan 2010 at 5:45

GoogleCodeExporter commented 8 years ago

Hello,

I am using version 1.2 of Peerblock which has the Port-settings tab, I set it 
to allow PORT 53 for both incoming and outgoing directions and still some IP 
addresses are blocked even if connecting to/from that port.

Original comment by Ruslan.A...@gmail.com on 5 May 2014 at 1:52

Attachments:

333333.png

GoogleCodeExporter commented 8 years ago

Hi,
I use this C:\Windows\System32\drivers\etc\hosts to block by name

192.1.0.2 www.red-gate.com
192.1.0.2 update.red-gate.com
192.1.0.2 red-gate.com
192.1.0.2 ui.skype.com
192.1.0.2 pricelist.skype.com
192.1.0.2 armorgames.com
192.1.0.2 apps.skype.com
192.1.0.2 wrapper.g.msn.com
192.1.0.2 g.msn.com
192.1.0.2 apps.skypeassets.com

I now some programs add here some things, e.g. Cisco Any Connect
119.221.19.37   vpn.coolcompany.com ###Cisco AnyConnect VPN client modified this 
file. Please do not modify contents until this comment is removed.

So it would be alternative to "DNS" blocking.

Right now I have to put stuff into hosts manually, some automated stuff 
integrated with peerblock could be good.

Original comment by Dzmitry....@gmail.com on 30 Aug 2014 at 5:51

lismore / peerblock

Allow DNS (un)blocking #220