[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

server temporary config



Hi all,

I'm setting up a server that will eventually be connected directly to
the net - which I've never done before (except my firewall I guess,
which doesn't do anything else).

Currently, though, it's on my masqued internal network.
This has been causing me some grief. For example, apache (apache-ssl)
needs a ServerName, and it doesn't seem to like what's in /etc/hosts.

I've got a feeling there will be other configs (eg postfix) which need
to be different now from the eventual config.

Does anybody have any suggestions for a general approach to configuring
a server outside of its final environment?

There's a real box answering to the domain name at the moment, so I
don't want it conflicting with that.

Also, are debian-default installations of most packages safe for use on
the net? I'll set up packet filtering, and leave lots of stuff off, but
I wasn't going to do much more than that.

The server will eventually be doing www, mailing list, cvs, web forum,
database (prob with a www interface, maybe also curses), sshd for
config. I'm also assuming apache-ssl is what I want for this box.

This post is a real mess of different stuff - hopefully it makes some
sense :-)

Any help appreciated.

Thanks,

Richard



Reply to: