ISP's that block port 80

Jeff jeep at rahul.net
Fri Oct 28 22:08:18 UTC 2005


Hello-

I know this topic has come up in the past as Ive looked
at a few posts about it.  I wanted to add my 2 cents and
also find out if anyone has any good suggestions about it.

It seems to me that most cable, dsl and other ISP providers
take advantage of the fact that they can restrict and block
port 80 (and possibly others like 25, 110 etc) and charge you
more to 'have' those services.  I think many would agree that
most of us do not need large upload speeds just to play or
have a basic webserver at home, but thats getting away from my
point....

My point is, I realize bind is targetted for IP's, not ports,
however, it sure would be a nice addition to the RFC specs and
bind itself to add port numbers (somehow) as part of this service
and bypass companies raking in bucks just to have a small webserver
at your house.

Im in a situation in which I am in a new development now for
nearly 1 year and DSL *still* isnt available.  My ONLY choice
is cox cable.  My current cox cable residential service has a
great up and down speeds of 500k/4M respectively.  Cox's basic
business is only 256k/768k for $79/month, which wouldnt be so
bad except they charge $245 installation charge!  give me a break!
Im currently underemployed so the $79 wouldnt be so bad, but the
$245 install charge is outrageous.

Like most things in software, there IS a way around it.  The only
thing I can see that makes sense is if bind was made slightly more
flexible by adding ports as well.  It would force a lot of things to
change in the ISP/business vs residential arena also.  After all,
telephone lines and internet connectivity in 2005 pretty much already
'installed'.  At this point most of these companies are just raking in
profits I would think.

Just my 2 cents.



More information about the bind-users mailing list