This may not be so desirable with respect to the exposing an internal port to the outside world. To avoid having to use a public IP address, it is possible for the firewall to forward the incoming request (from outside the local area network) to the internal server. There may be occasions where the local area network behind a masquerading firewall contains a server which needs to be publicly accessed. Iptables and port forwarding should solve your problem. The test in this case is SSH, and I know that SSHD is working properly because I can log into that machine just fine from another PC on the same internal subnet. But when I log in to :port, it just times out. I *am* opening the ports in the firewall. But there's obviously something they're leaving out. I've read the sparse Webmin documentation in their Wiki, and it leads one to believe that you simply insert a "NAT" rule. But OpenSuse 10.3 is nearing EOL, we're buying a new machine, and I'd like to use CentOS on the new one. We're currently using OpenSuse 10.3 on this box, and YaST makes this criminally easy (you give it the incoming port number and the destination IP/port numbers and it just works). ![]() We have a BUNCH of exposed services that are on special ports - for example, to connect to one machine, you go in with :12000, and to connect to another, :12002, etc., etc. Internet - NIC1 NIC2 - Switch to other PCs If I can help any further, feel free to PM me.Can anyone here point me to a walk-through or discussion of how to use Webmin to set up port forwarding/NAT on a dual-NIC Centos 5.3 box? The layout will be simple: ServerAlias DOMAIN.NET will not answer to you will need to setup a serveralias for also. Until that is working, nothing else will help.Īfter creating the zone, or updating, make sure you reload bind.you may also need to increment the serial, I forgot if webmin/virtualmin does this automatically.Īlso, remember, in your apache conf, you need to add a ServerAlias for each FQDN you want that site to answer to. Will return the A record IP if it is setup correctly for DOMAIN.NET. They should all have the same A records for (base domain) and If your has all of these records loading, you should be able to query it, regardless of if you have changed those domain's authoritive name servers at the registrar. Just as you created a zone file with A records for DOMAIN.COM on your name server, you need to do the exact same thing for any other domains you want pointing to your DOMAIN.COM web site. If you can't resolve, then you need to get past that hurdle first. So you have DOMAIN.COM, DOMAIN.NET, OTHER-DOMAIN.COM setup, with dns zone records loaded in your name server, and the registrar is pointed to for all domains, correct? I can create new "virtual servers" for each domain and forward, but that won't work for my purposes. I did add 'A' records for each domain in the main DOMAIN.COM zone in BIND. ![]() I don't think that's the problem because the other domains do not resolve or ping. ![]() ![]() I did add other domains as server aliases in Apache's configuration. So I'm not understanding what I am doing wrong that it doesn't want to work. So when someone goes to OTHER-DOMAIN.COM I want them to connect to the DOMAIN.COM web site. to point to the main DOMAIN.COM web site.įor the other domains, I added the name server at the registrars. I want other domain names such as DOMAIN.NET, OTHER-DOMAIN.COM, etc. (I was indeed mistaken that I need CNAME).īasically I'm just trying to point other domains to a main website.ĭOMAIN.COM is the main website and works fine. Thanks for the response and tips, but again I'm not looking to create sub-domains.
0 Comments
Leave a Reply. |