General Dyndns Question for new Setup

[preemo]

Hi everybody and Scalix,

I'm going to set up a brand new Scalix 11 Server on a Fedora Core 5 distribution.
It should be accessable from the Internet via a dyndns Domain so my question is what servename and domain name do I have enter when I install FC5.

Example

The dyndns domain is mailserver.dyndns.org

So when I install Fedora :

Is It

1. Name: mailserver Domain: dyndns.org

or

2. Name: scalix Domain mailserver.dyndns.org

and Do I have to setup a own DNS Server (like BIND9) to resolve the name in the second case

thanks in advance

preemo

[kanderson]

I think what you'll need to do is have a firewall or Router in front that dyndns resolves to. If the IP address of your server changes, you WILL have problems.

PostgreSQL, for example, allows access to it's database based on your IP address.

As I remember it, you will probably also recieve a hostname from your dsl/cable provider, and it will change as the IP changes. This will cause problems within Scalix.

Kev.

[preemo]

My plan was to install the Dyndns client on this machine to update the changing IP's at dyndns and maybe use BIND9 to resolve the domain name on the machine to it's static 192.168.xxx.xxx. could that work or do i really need a axternal router to do this ??

[kanderson]

It could be done, but again, I'd recommend against it.

You'll need to reconfigure PostgreSQL after ever change, and you won't have access to webmail until you do that.
You'll also, and much more importantly, need to fix the mailstore each time the hostname changes. If you search the forum, you'll see that people have PLENTY of issues with hostname changes, though they can be managed.

At minimum, you'll want to read both of these:

http://www.scalix.com/wiki/index.php?ti ... ChangeFQDN
http://www.scalix.com/wiki/index.php?ti ... s/ChangeIP

And I'll say again. Just get a router. I'm certain you can find a headless Pentium class machine that someone will give you for nothing with 32 megs of ram. Install IPcop, and port forward ports 25 + 80 (at least, you might want 110, 143, 5729). Then give the server the same name as you'll use with dyndns. That will be constant, and it will work fine.

Or rather than the IPcop box, use a dlink/linksys router.

It will REALLY save you alot of hassles.

Kev.

[swordfish]

In my situation I have the following setup. The server is installed with name server.domain.com with private IP address. Then I have a firewall at the front of it which updates the name server1.dyndns.org automatically. The firewall is doing port forwarding for incoming request to server1.dyndns.org on ports 25, 80 and 443 to the private IP address. The users internally have static mapping in the hosts file for server.domain.com to resolve to the private IP. This was they access from outside the server via SWA pointing to server1.dyndns.org/webmail and via Outlook through VPN on the private IP address. Internally they can access it either way. So far I haven't had any issues with name resolution etc. in this type of setup.