Tutorial
Set Default Address
by admin on Feb.10, 2012, under cPanel
The default email address will “catch” any mail that is sent to an invalid email address for your domain. All mail that is sent to an address that does not exist will go to the default email address. To send all default mail to the main mail account, simply type the user name of your cPanel account in the email address input field.
WebHost Manager 11 Documentation – Networking Setup
by admin on Feb.09, 2012, under Tutorial, cPanel
Modify Hostname
The Change Hostname option enables you to change the hostname of your server. It is important to choose a hostname that will not be used for any account and the hostname must be socially acceptable, as it will appear in all mail headers. The hostname must be a FQDN (Fully Qualified Domain Name). All valid hostnames must have at least 2 dots in them, for example entropy.yourdomain.com.
WebHost Manager automatically generates 10 random hostnames based on your current hostname as samples, which you can use.
NOTE: Your hostname should be a Fully Qualified Domain Name that will not be used elsewhere on the server. You should never set your hostname to a name that is already used (www, ftp, mail, etc) or to the name of an account on the server (www.domain.com). This means that your hostname should never be a domain name and especially not the name of your domain!!
Steps
- To access the Networking Setup Menu, click on Networking Setup, on the main screen of your WebHost Manager interface.
- Click on Change Hostname.
- Enter your changed hostname in the New Hostname field.
- Click on Change.
Troubleshooting (advanced users only)
If you are receiving any errors related to your hostname or you’re unable to change your hostname through WebHost Manager, please try the following from the command line:
hostname
The output shown should be in the following form:
servername.domain.com
NOTE: The hostname must contain two periods or dots (.), you will need to change the hostname to a fully qualified domain name.
To change your hostname to a fully qualified domain, use the following from the command line:
hostname servername.domain.com
Replace “servername” with a unique server name and replace “domain.com” with a domain name that you control, for example: the domain of your hosting company or the main domain on the server.
Now, run:
hostname
If the output is the same as the name you used, everything should be fixed. If you still get any hostname errors, please contact your host or cPanel for support.
Manage Nameserver IPs
You will need to add an IP address for a nameserver when you create a new nameserver.
Steps
- To access the Networking Setup Menu, click on Networking Setup, on the main screen of your WebHost Manager interface.
- Click on Manage Nameserver IPs.
- Enter the IP for the new nameserver in the Nameserver field and click on Assign.
- If you wish to remove a nameserver, click on the red X to the right of its name.
Modify Resolver Configuration
The resolver configuration file (/etc/resolv.conf) is a configuration file for name server routines. Normally you do not need to modify resolv.conf.
NOTE: Do not modify the IP values unless you know what you are doing. If they are not altered properly, your server will not function properly.
Steps
- To access the Networking Setup Menu, click on Networking Setup, on the main screen of your WebHost Manager interface.
- Click on Modify Resolver Configuration.
- Click on Continue.
- Read the information unless you are sure that you know what you are doing. Enter your primary resolver’s IP address in the Primary Resolver field.
- Enter additional resolver IP addresses in the Secondary Resolver and Tertiary Resolver fields, if required.
- Click on Continue.
OpenVZ or Xen ?
by admin on Feb.08, 2012, under Tutorial
OpenVZ:
Advantages: allows overselling. Very light weight. Can accommodate more Virtual Machines in a server.
Disadvantage: There is no per vps swap.
Why this is important:
OpenVZ will KILL your application if it goes beyond the limit, and this can cause some trouble. There are people out there who want to host oracle on a 64MB vps, and with such customers, using openVZ will lead to constant application crashes, which ultimately will be blamed on the provider. (This is actually something that is common with openvz/virtuozzo hosting in general; you can check some threads at wht).
With Xen, each vps has its own swap, and thus you get an EXACT dedicated server like environment, but with lesser resources. So here, the customers applications will NOT crash, but rather it will become slower. Also, majority of the applications, like apache, spamassassin expects a lot of memory, and openVZ makes memory a very valuable commodity.
So generally my recommendation is that: For friendly customers use openVZ, and use a lot of burst memory. For not-so-friendly customers, use Xen. And that is why we are providing transparent migration. You can start a customer on openVZ, and see how it works out, and if he is getting too many application crashes, you can move him to the SAME configuration on Xen, and he should be able to do fine, though his application would be slower.
Adding a partial wild-carded Address record
by admin on Feb.07, 2012, under Tutorial
Our Managed DNS service currently does not support partial wildcards in Address (A) Records. For instance, consider the following example, where Managed DNS services are purchased for domainname.com:
Domain name: domainname.com
Go to Manage DNS Records, and add the following A record
Hostname: *.something.domainname.com
Destination IP Address: 203.199.114.89
The system will throw an exception: Invalid Name *.something for A Records
In order to circumvent this, you would have to add a new Managed DNS Order for something.domainname.com, and create the wild-carded A record here, as below.
Domain name: something.domainname.com
Hostname: *.something.domainname.com
Destination IP Address: 203.199.114.89
Now, abc.something.domainname.com will point to 203.199.114.89
I want domain.com/stats to be present by default
by admin on Feb.06, 2012, under DirectAdmin
If you want webalizer or awstats pages to be available by default for new domains, you can do so by creating:
/usr/local/directadmin/scripts/custom/domain_create_post.sh
In the file add the code
#!/bin/sh
ln -s ../stats /home/$username/domains/$domain/public_html/stats
exit 0;
Then chmod the domain_create_post.sh script to 755.
If you want it to be for awstats, then change the bold stats name to be awstats instead.
