Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Is it possible to use bind to resolve a domain name to a port on the localhost.
IE. Im running BIND on domain.org, and I want BIND to resolve sub.domain.org to port 22?
Story goes, Ive got a new office, full of computer projects im working on. Ive got a new freebsd box acting as a gateway with my single ip address on the external interface. On the internal lan, Ive got a number of boxes with privately routable ip addresses.
I need to be able to ssh to one of these internal boxes, names andromeda. Already, im setting up ipnat port forwarding to forward the external port 42000 on the freebsd machine to the internal port on andromeda 22. What I was to know is, is there a way to have bind resolve andromeda.domain.org to 127.0.0.1:42000?
So far, bind doesn't seem to like it when I try to resolve a port and an ip address.
Distribution: Slackware / Debian / *Ubuntu / Opensuse / Solaris uname: Brian Cooney
you can probally get somthing to work with iptables fowarding, but im to nibby to tell you how exactly
you might have to use a different port on the external if that machine needs ssh as well, and just have that port foward to the correct port on the internal machine.
somthing else that I do here at home that works well, is to simply ssh into the gateway machine, then ssh FROM the gateway machine to the internal client machine. Probally not very efficiant if you want to copy files over ssh bc you woudl have to use two hops, but it works just fine for running commands (even wget ect)
a domain name doesn't have any connection to a port. wether you are useing http, smtp, ssh etc.. the hostname is still the same... the port number comes later on. basically this isn't bind's "problem" in any way. i would say just use the different port number on the external machine. forward port 222 or something instead.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
An "unroutable" IP is just that: Not routable to from the Internet, period.
What's wrong with normal port forwarding? You can forward a port from an external IP to the same, or a different port an an arbitrary internal IP. It has nothing to do with resolving names to IPs, it has everything to do with translating external IPs to internal IPs and translating (or not) port numbers.
But you see not every application layer protocol require that the domain name to be passed to the server. HTTP does, and in fact using Apache virtualhosts and mod_proxy you can achieve what you want, though only on http.
It is possible to accomplish what you said, but will require a rewrite on many protocols and many existing softwares.
IP shortage is a problem yes, but a solution called ipv6 is being developed.