|
From: Thomas L. <th...@th...> - 2005-10-02 21:01:05
|
I've set up a "demo" sub-server/sub-domain, to host demonstration projects and client prototypes... the URL to access these is "demo.godmomasforge.com" *normally*, in an unmanaged/unautomated situation, I would put the DNS entries for this in the same file as I do for the root domain and it's sub-hosts (www.godmomasforge.com, ftp.godmomasforge.com, etc.) This is what I expected Webmin to do. Instead, however, it created a separate file... which the secondary DNS server never picked up (since it is not managed), because I didn't expect to have to configure it to do so (this has resulted in a very puzzled customer whose attempts to access the demo site have failed inconsistently). I'm assuming that putting this stuff in a separate file isn't a technical issue (since it works, on the main server)... but should webmin be doing this? Also, instead of renaming or over-writing existing /etc/httpd/conf/vhost files when a domain is created (not imported), it appears to be appending to them... renaming the file would seem to make more sense, because the result appears to be that the new configuration directives are ignored in favor of the existing ones. Regards, Thomas Leavitt |