Dear all, I have a setup fot virtualmin behind firewall :
202.1.1.1 -----------------> 192.168.1.1 (abc.com) Internet -> Firewall & NAT -> virtualmin
I already define external IP to 202.1.1.1 and virtual server IP address to 192.168.1.1.
After created a new domain name, all DNS record already use external IP. It is correct for lookup for external. But if I send mail from abc.com to abc.com, it cannot send to user and postfix appear unable to lookup the host. I believe that server is trying to find external IP MX record and cannot locate back to server. Is it need to setup internal dns server for internal lookup ??
You have already achieved what you want using the portforwarding rule. Any connection attempts to your public IP will be forwarded to the internal host as long as there is a corresponding portforwarding rule for each network service you want available like web, mail, ftp, ssh, etc.
If the internal server is only hosting one web site your all set.
Note that most consumer "routers" do not actually route on behalf of internal hosts. So, traffic coming from inside will not be able to connect to the public addresses. I don't know if this specifically applies to your router, but it's almost universal among the routers you find at Best Buy or Fry's or whatever.
I just mention this as a heads up, so you don't waste time "testing" from inside your network. It will probably simply not work, and you'll have to connect from outside to actually test it. You can hit the private address from inside, obviously, and that'll work find...so you can add the domains to your hosts file on your client machines so that the name-based hosts work.
--
Check out the forum guidelines!
MX records do not have IP addresses. They are just a name. e.g.:
$ host -t mx virtualmin.com
virtualmin.com mail is handled by 5 mail.virtualmin.com.
Rather than come up with theories about what Postfix might be doing...you should check the maillog/mail.log. That will tell you why it actually isn't being delivered.
--
Check out the forum guidelines!