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.
You can't specify port numbers in any way through DNS. That is not part of its capabilities. You can use the same or different names for the 2 targets, but you have to include the port number, using whatever method is correct for the client looking to your server.
If for example, people use a browser to look at your site or play on your MUD, you would have to send them to 'http://my-mud.com:4000' or 'http://my-mud.com:8000', and if connecting by telnet, it has to be 'telnet my-mud.com 4000' or 'telnet my-mud.com 8000'.
You could try SRV records I believe, but not one browser in the world asks for SRV records.
If you want to get rid of the port number in the address, you can pull some redirect and proxy tricks, but DNS cannot do what you are looking for.
No problem. After a quick reread of what you wrote originally, you absolutely can run both on one name, and just tag the port on at the end. So your website will exist at http://my-mud.com:8000 and the mud (accessed through telnet) would be 'telnet my-mud.com 4000'.
If that doesn't work, something else is wrong.
Peace,
JimBass
Last edited by JimBass; 10-24-2007 at 10:29 PM.
Reason: typo in the 4000/8000s at the end
There is no such service for telnet redirection. But you could configure your local machine to redirect port 22 to 4000 via iptables or squid or other ways.
DO NOT RUN YOUR MUD ON PORT 22! Doing so will require the engine to run as root. NEVER do this. Find some way for a 'stub' program to redirect packets to port 4000 from port 22.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.