PDA

View Full Version : DNS config doubt


trident
07-08-03, 04:17 PM
Hi

This is the problem that I need to solve:
I am running apache at port 85 (because I can't run it in port 80...), but I need to configure my domain name to point for that port in the specific IP when somebody tries to access my website...so, how do I do that ?
:banana: THANKS:banana:

beley
07-08-03, 05:06 PM
Not that I know of... you should make sure your firewall isn't blocking that port though, as some setups will only set to allow http, ftp, etc. it won't by default allow 85.

Domain should just propegate to the server IP itself, from there it should be up to apache.

trident
07-08-03, 05:15 PM
Hi Beley,

Thank you for your help....I will try to configure apache to handle that....
But anyway, If somebody knows how to do that on apache, please let me know.

beley
07-08-03, 05:28 PM
in your httpd.conf file there is a section that states the port to listen on... you'll have to change that to 85 from 80. Other than that... I couldn't say. I could look it up in my apache reference book :D

soapsud
07-08-03, 05:33 PM
your visitors would actually have to type:

http://yourdomain.com:85/ to access your site though, you won't be able to let them access http://yourdomain.com and have that forward to port 85.

beley
07-08-03, 05:38 PM
I'm not sure about that... if you reconfigure apache to listen on port 85, it should work, right?? I've never reconfigured it to listen on a different port... so I'm not positive though :-P

soapsud
07-08-03, 09:29 PM
no, essentially, the browser (or whatever you're using to access the site) will assume port 80. finding no service (or something else) it will just time out.

by placing the :85 after the domain, it forces the browser to look for service on that port.

ie, think of it this way, apache is listening to port 85, yes, but the browser is still trying to connect to port 80 unless you tell it not to.

trident
07-09-03, 08:53 AM
Yeah...I think that now is more clear how it works...but doesn't exist anyway, like in the DNS config or something like that that may redirect the connections in port 80 to the port 85??
Thanks.

:-)

allan
07-12-03, 12:45 PM
Originally posted by trident:

Yeah...I think that now is more clear how it works...but doesn't exist anyway, like in the DNS config or something like that that may redirect the connections in port 80 to the port 85??
Thanks.


No, DNS is an intentionally dumb service -- it directs people where to go, it does not tell them how to get there, or what to do when they are there. Ports are an application level concept. If someone does not know to ask for web services on port 85 they will get whatever is on port 80.

The only way you can do what you are describing would be to redirect traffic as it came into your server using a CGI script or an Apache redirect statemnet (eg: www.domain.com:80 redirect www.domain.com:85), but if you cannot listen on port 80 in the first place that won't do you any good.

Toolz
07-12-03, 12:53 PM
Originally posted by beley:

in your httpd.conf file there is a section that states the port to listen on... you'll have to change that to 85 from 80. Other than that... I couldn't say. I could look it up in my apache reference book :D
He's already done that I think: " I am running apache at port 85"

Question to poster: Do you have anything at all listening on port 80? Is it a httpd? IIS maybe? If so it's simple to put a page there that redirects to yourdomain:85

trident
07-12-03, 12:56 PM
actually not...my port 80 is blocked!

Toolz
07-12-03, 01:18 PM
Interesting!!! Can you put a proxy in front of your machine that performs a mapping/redirect?

Remember there are commercial url obfuscating services that might, just might, be able to perform such a function as well.

allan
07-12-03, 01:21 PM
Originally posted by Toolz:

Interesting!!! Can you put a proxy in front of your machine that performs a mapping/redirect?

Remember there are commercial url obfuscating services that might, just might, be able to perform such a function as well.

Sure, then you would just map the domain to the IP address of the proxy server. People hit www.domain.com:80 and the proxy server redirects them to www1.domain.com:85

trident
07-13-03, 11:45 AM
Yeah! I think that this is the solution! Using proxy for redirection....good way...
=)
IŽll try it.
Thanks

allan
07-13-03, 11:47 AM
Good luck -- let us know how it goes :)