There _is_ a way around the web and ftp part of your problem keeping the
addresses you've got, but if you've based your mail server on multiple
domains by IP, then you'll need official IP addresses, at least for each
domain on the mail server. If you're going to the trouble of getting some
official IP's for your mail server domains, you may as well get some for
your FTP and web server too.
If you've got private addresses, then DNS won't work properly in the
Internet wide scheme of things, because your machines won't have valid DNS
resolvable hostnames. Say your firewall machine is also your DNS server. Any
request coming externally to it for host.yourdomain.tld (assuming
yourdomain.tld is pointing to the fixed official IP of your firewall / DNS
server) will result in a return address of (say) 10.1.1.3, which won't be
routeable throught the Internet anyway.
If your DNS server is _inside_ your firewall, then it will have a private
address, and therefore will be inaccessable from the Internet.
In short, you need official IP's - ask your ISP if they can assign you a
> my whole network (DNS, Mail, Web, FTP servers) is composed with private IP
> addresses : 10.1.1.0
> I've setup a firewall between the Internet and my network.
> The mail server is running multiple domain (using vpop) so I've binded an
> address for each domain.
> I've done the same thing for the FTP server.
> Everything is working perfectly locally.
> Can I keep my private addresses or do I need official IP addresses for
> server and each virtual email domain ?