Port 80 blocked by ISP

I've not heard nor run across an instance that verizon has blocked port 80 http traffic. I have verizon DSL service and port 80 http traffic works fine. 99.999% of all web site traffic use http [default port is 80] and using a site IP address assumes [unless otherwise specified] e.g. 4.46.46.1 would use port 80 traffic.

If you wish to use a different port for security reasons then you would have to specify in the DNS A record that is IP address 4.46.46.1:8081. Then when an internet wide WhoIS query on name resolution is requested for your site, DNS will respond that is IP address 4.46.46.1:8081 public inbound http requests will be redircted to that address and port.

Further, IIS will have to be configured to listen on that port for http traffic and any firewalls will have to have that port configured to allow TCP/IP http traffic.

Yes, you are correct about Verizon not blocking port 80. I should have been more specific, Cox Cable is the ISP blocking port 80. Thanks.

Hi, If Cox is blocking port 80, then it's a policy to prevent someone on your class of service from hosting a website. They probably have a different pricing structure if you wish to do that, so there's probably no workaround except: 1) call them and find out OR 2) find another ISP who will let you do what you want for the price you wish to pay. Sorry it's not an answer, but just a guess of an explanation.

---Will

see paragraph 2 of answer #1 of how to set up domain name to IP address resolution for other than the default http port 80. [the explanation is that unless otherwise specified, meaning if no specific port is stated in the IP address, http traffic goes through port 80] You can workaround cox cable's blocking of traffic on port 80 buy using a 3rd party DNS service and specifiying that is ip address on port via the A record. It's a tricky situation if you have a dynamically assigned IP address in that updates to the A record with a new IP address will be done with the default port 80 which then requires a manual imput of the proper port. Better route would be a static IP address.

Even better is using Verizon DSL service instead of Cox Cable. Though some swear by cable internet service, cable service is prone to network congestion and loss of bandwidth [with more severe slow down than DSL ]as the # of users on the cable system increases.

As a cable network, Cox has limited bandwidth to share for all users. By hosting a Web site, you impact performance for other Cox subscribers on the same segment.

This isn't a pricing issue, but a technology issue. Rather than search for a way around the constraint at the performance expense of others, use the Cox personal Web site hosting or choose an alternative Internet access that will allow you to purchase the capacity and capability you want.

This question was closed by the author