Been a while since I installed so I don’t know how or why but my default domain shows up in the virtual server list. I thought it was automatic? I guess not?
I tacked ‘admin’ onto the back of the name of the service I was exploring helping to move from their current provider. (that never happened but I kept the server space for my purposes). There is a virtual server with that domain. If you mean the fully qualified name? I think a sub server would work but you’d have to play with the DNS settings maybe.
Well, if it wasn’t created automatically as the ‘default’, then I created it. So it is possible. Why do you think it should would be an bug to create it? Doesn’t your initial post show it isn’t possible to recreate it?
throughout the forum joe has said it is bad to create a virtual server with the same name as the hostname.
So i wanted to know if virtualmin prevented the created of a virtual server with the hostname, if it doesn’t I would then flag this as a bug/feature request.
The problem is virtually hosting mail with the same name as the host you’re hosting the mail virtually on. You then have two things with the same name, which confuses postfix (postfix is being told to rewrite, e.g. joe@virtualmin.com to joe@virtualmin.com which is a crazy thing to do, so we recommend you don’t do it, and the simplest way to not do that is to not name your system the same as a name you’re hosting in Virtualmin, since Virtualmin defaults to creating a virtual mail domain when you create a virtual server in Virtualmin.
If you want to host one domain you are now required to purchase a second for admin purposes? That’s basically what I did since it was originally supposed to host a few dozen sites.
That said, maybe Virtualmin should create a special default with the hostname that doesn’t use the rewrite rules? Easy enough to say for the person that doesn’t have to write the code.
For example, because you need to have some kind of system in it, or order and logic. All my real server’s is placed in xxx-services.yy domain. real1.xxx-services.yy, real2. … My presentation domain is xxx.yy (from xxx-services.yy) . And my all not routable systems is on real registered xxx-intra.yy domain. And no problem with automatic deploying, fresh instalation and other and it have other benefit’s. And if I read log’s, I know immediately where the problem is. However, this scheme does not contradict your statement, I just want to point out the advantages.
Sure, that’s fine. I just mean “you do not need to use it for anything in Virtualmin”. Not that you can’t have a sensible hostname that makes monitoring and alerting comprehensible. My point is that people keep wanting to use it for the same things that are virtually hosted in Virtualmin, which means there are two things with that name, which is a nonsensical thing to do. I think it’s just a conceptual leap that folks aren’t making; what you do in Virtualmin is virtual, it is not the physical host. Mail in Virtualmin is configured in the virtual map in Postfix. Websites configured in VirtualHost sections in Apache configuration. The system hostname is the system itself, and not anything virtually hosted on it.
our internal Nagios monitoring service does simple health checks on our many Linux servers — one crude check it does, using the RedHat server name, is to see if port 80 and 443 are responding (to check to see if apache/httpd is running). My older approach to support that was – create a Virtual Server using the Linux host name
