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.
Hi all. Just wondering if any of you could help me out here.
Basically, I have two servers here and one external IP address.
I have MX records on the internet for both machines pointing at the same external IP address.
linux.njdownes.com is the name of the DNS server (web server also running) which points to 80.7.13.151
I also have njd-vaio.njdownes.com (mail and web server running on this server) set up to point to 80.7.13.151.
I'm not entirely sure what you're trying to do. You've only got one public IP address, so all externally available services need to be using that IP address. The easy solution is to put all of the services on one physical machine - DNS, Web and mail all have very low starting requirements (i.e. at least a 486). You can also use port forwarding so that whatever machine is on the external IP address forwards connections for particular ports to another machine. Your Linux box can do port forwarding for any ports you like, or you can assign the external IP to a router which will host no services of it's own but merely forward connections to the appropriate Linux box.
I'm doing exactly what you said at the minute - simple and it works.
Though, I'd like to know how to sort out a zone that could be used internally only.
Would I have to set up a zone for 192.168.2.x and then set ACL's so that it is not externally viewable?
I tried it before but the internal IP and external IP were showing when doing a DIG of NSLOOKUP on the internet.
OK, I think I understand - your forward lookup zone has internal IPs in it that shouldn't be shown to outside systems.
It's not a huge security issue as private IPs addresses obviously can't be reached, but I beleive that you can define "views" on zones with BIND 9 so that different systems get different results.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.