Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to help two friends. One is on a home cable/DSL network with ports 25 and 80 blocked. The second has a T1 and offered to allow the home user access to redirect port 80.
We have all searched, but are still unclear what the zone file for DNS on the T1 host should look like to make this happen.
A zone file have been created for the home cable user's domain on the T1 host, but we are not certain how to create the A/SRV/CNAME records that will cause http://domain.com:8080 to be redirected to http://domain.com.
Could anyone point to where there are guidelines or rfc docs that explains what to do.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
You cannot do port translation with DNS. Redirecting port 80 (because http://domain.com is the same as http://domain.com:80) to port 8080 must be done some other way.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
What the sites you mentioned do is direct the traffic to themself, then have a reverse-proxy running to send the traffic to your HTTP server on a different port. Of course, you could do the same thing by using mod_proxy on the T1 host instead of simply using an HTTP redirect.
Proxying is more transparent and will work for a lot more different types of web apps, deep links, etc, but it also requires that all the traffic goes through the T1 host first before it reaches you. With a redirect, only the first request goes to the T1 host, after that they're on your page and all the requests go directly to your server.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.