Blocked port 80 on ISP, need my DNS server to serve IP address and redirected port.

[Mech-Man]

Hi all,

I have DNS (BIND) and Apache running on linux behind a linksys router just fine. The problem is that I can ping my domain (www.patchworkcrazy.com) fine. However, my ISP is blocking PORT 80 so even though I can ping and my DNS serves the correct IP, Apache never gets the request. So I need my DNS to provide the IP (137.118.207.9)with port 8080 when www.patchworkcrazy.com is requested. I already have Apache listening on 8080.

example:

when listen in http.conf is set to 8080

http://137.118.207.9:8080 works fine

when listen in http.conf is set to 80

http://137.118.207.9:80 does not work

How do I set up my DNS server to provide a different port for the web address (URL).

Me thinks the big DNS use a portforward type when you use thier nameservers?

Thanks

[Gertrude]

If they block port 80 your out of luck. There won't be a way for Apache to listen on port 80 and have connections take place on that port if it is getting blocked by your ISP, the only thing you could do would be what your doing now and thats running it on port 8080, or some other port.

EDIT:

Im not sure if there is a service like this or not, but if you could have another company or person just host the domain name then have them forward all request to your IP address on another port. So that the first connection to www.whateverdomain.com goes to Jack DNS holder then he forwards those request to whatever domain it came in on to the customers IP on another port. If there is a company that does this tell me cause I would do that for my domain.

[Mech-Man]

So,

There is no way I can tell the world out there to use 137.118.207.9:8080 via my DNS when they request www.patchworkcrazy.com?

I don't mind using 8080 instead of the default 80. I just need to know how to tell the world to use it.

:(

[viperlin]

if your url www.patchworkcrazy.com is just a URL re-direct to http://137.118.207.9
then make the re-direct go to http://137.118.207.9:8080 and it should work

however i do not know about doing this with other types of DNS other than simple URL re-direction

[Mech-Man]

Hummm,

Please correct me if I am wrong, but I believe your application (webserver, portforwarder, etc) would have to be able to recieve on port 80 before redirecting it to 8080 via a URL-forward type application.

When I host my address on domainsite.com's nameserver, they allow you to enter a ip address with a seperate port ipaddress:8080 for example when they create host record (zone) on thier nameserver ns1.domainsite.com for example.

:confused:

[Mech-Man]

Im not sure if there is a service like this or not, but if you could have another company or person just host the domain name then have them forward all request to your IP address on another port. So that the first connection to www.whateverdomain.com goes to Jack DNS holder then he forwards those request to whatever domain it came in on to the customers IP on another port. If there is a company that does this tell me cause I would do that for my domain.

Well, this is what I was doing at domainsite.com. When you use their DNS servers, they allow you to include a port :8080 when you create a host record. They also allow you to use URL-forwarding but that is really slow.

[bwkaz]

Wouldn't it be simpler to just keep the name resolution the same, and tell people to connect to yoursite.com:8080?

:confused:

Although dyndns (www.dyndns.org) does have some sort of URL-rewriting service. I don't know if there's a one-time fee attached to it, though.

[Mech-Man]

Wouldn't it be simpler to just keep the name resolution the same, and tell people to connect to yoursite.com:8080?

Will this appear in searches generated by google and the such? It's for my wifes business/hobbie and a lot of her potential customers might have a little trouble with it.

I would like to have the port implicit to the web page www.patchworkcrazy.com if possible. If this can't be done, then I might have to go back to using the nameserver of domainsite.com.

I am new to this and prehaps I am not understanding to well.

:(

[homey]

If you are successful in allowing web traffic into your machine which is obviously something your ISP doesn't want... You may be searching for a new ISP soon.

Just a thought. :)

[Alex Cavnar, aka alc6379]

Originally posted by homey
If you are successful in allowing web traffic into your machine which is obviously something your ISP doesn't want... You may be searching for a new ISP soon.

Just a thought. :)

I would second this. Even though my ISP disallows SSH and FTP, I run them, but only for personal use. If you're looking to run a website for a business, I would seriously recommend using a real hosting company.

I've heard of cases where ISPs have terminated users' accounts for running servers off of a home connection, especially for commercial purposes.

[Mech-Man]

If you are successful in allowing web traffic into your machine which is obviously something your ISP doesn't want... You may be searching for a new ISP soon.

Well, I would agree but the problem is not with my direct DSL ISP provider (a small telco). I do pay an additional charge for a static IP and they are aware that I am running a server. I believe the blocking takes place further up the food chain. Who ever my telephone company's provider is.

I can us dialin (modem) of my telco and display the web page (on my DSL connected server) with the default port of 80.

Its when I try to do it out side of the telco domain (their firewall) that it is blocked.

I do realize that other ISP frown on this. Its a shame, the only thing broadband offers for those guys (home users who want a web server) is a better gaming experience.

Pricks IMO.

Thanks

[bwkaz]

Originally posted by Mech-Man
Will this appear in searches generated by google and the such? If you get linked to, yes. If you don't, then it won't matter -- Google won't index your site if it's not linked to from anywhere else. Google's just a massively large web crawler.

If you have other people add an <a href> to yoursite.com:8080, then Google will pick it up.

[Ofloo]

or what you can do as wel is use an external free dns provider like zoneedit.com and an dns provider with port forwarding cname it on th zoneedit.com done ;) it will go to the cname dns and forward the domain to the other port don't know if it will work tho but worth to try like this you can use your own domain.

- some free dns providers have port forwarding on port 80 to 8080 deerfield used to have it but is no longer free, i am sur there other free dns providers that do support it. Just can't think of one now hehe ;)

[Ofloo]

or you can use zoneedit url forwarding then you be able to forward your www.domain.com to an url any url don't know if they support domain cloacking tho. check afraid.org out *** wel i think they have port forwarding not sur tho but isn't as good as zoneedit at least that is what i think ;).

[Ofloo]

looked true there help files (zoneedit.com) and found this:

My ISP blocked port 80. How can I run a web server?

Don't worry, you can still run one!

Sign up and get started with ZoneEdit.
Make your web server listen on port number like "6000" or "5000"
Check to see if your web server works in a browser by using a URL: http://3.4.5.6:6000/. Use the port number that you're listening on and the real IP address of your machine.
Add the "IP Address" for your web server in ZoneEdit: "ww2.domainname.com" points to "ip address".
Add a Web Forward entry for your domain called "www.domainname.com" that points to http://ww2.domainname:6000/
We recommend turning cloaking off in this case, letting people know thay are going to http://ww2.domainname.com:6000 is usually OK, and it allows the browser to perform better.


btw: don't think you be able to run your own dns servers if you want to do port forwarding. don't know if it is required for you tho. but zoneedit is free at least if you don't use more then 5 domains and still if you wanted to you could make 2 accounts or more.

sorry didn't put this in one answer.

oh and they have catch mail *** wel and do support dynamicdns so in a way they have it all ;) lol if port 80 is blocked port 25 will be for sur so .... if your planning on running a mailserver ... you can use fetchmail and forward it to sendmail ;)

[Mech-Man]

Thanks,

I will try it.

All good info and thanks to everybody for all the information provided here.


Thanks again.

rodger

[Ofloo]

np