Last modified: 24 Dec 2007
WARNING: This documentation covers Parallels H-Sphere versions up to 3.1. For the latest up-to-date Parallels H-Sphere documentation, please proceed to the
official Parallels site.
Custom DNS records are required to manage non-HSphere servers with H-Sphere DNS zone or to
configure new logical servers that are added manually. This document tells how to add custom DNS records.
Depending on the service, you can add:
To add new custom DNS records:
- In your admin control panel go to the E.Manager menu -> DNS Manager.
The following page shows:
- Click the Edit icon near the chosen DNS zone. A page similar to this will appear:
- At the bottom of the page that shows, select a DNS record from the drop-down
list and click the Go button.
- On the form that shows enter all necessary data and click Submit to save.
You can add one of the following types of DNS records:
- A records to map domain names and web server IP's.
- MX records to map domain names and their mail server IP's.
- CNAME records to map aliases with domain names.
Adding custom A records
The Address record (A record) gives you the IP address of a domain.
That way, users that try to go to www.example.com will get to
the right IP address.
To add a new DNS A record, you need to provide a set of parameters:
- Name: the string appended to the domain name to
create a FQDN mapped to the IP. For example, if your domain
name is besthosting.com, entering cp will
make the fully qualified domain name cp.besthosting.com.
- TTL (a Time To Live): seconds to elapse before the record is refreshed
in the provider's DNS cache.
- Data: the IP address that fully qualified domain
name will be mapped to. You can get this IP address with any ping utility.
Adding custom MX records
A host name can have one or more Mail Exchange (MX) records.
These records point to hosts that accept mail messages on behalf of the host.
Adding MX records is similar to adding A records:
- Name: your local domain name.
If you leave the Name field blank,
all mail will be redirected for the base zone.
- Data: the priority of the record and mail domain name
(not the IP) mail will be forwarded to.
Note: The priority of the custom MX record defines
whether your external servers will act as secondary or primary.
For instance, if you set the priority of the custom MX record higher than 10 (e.g. 11),
your external mail server will be used as secondary.
If you set the priority of the custom MX record lower than 10 (e.g. 9),
your external mail server will be used as primary.
In the latter case, your mail will be sent to your external mail
server until it goes down or becomes otherwise inaccessible.
Then the default mail server will take over.
WARNING: Please pay attention to $ORIGIN when you
add an MX record.
Adding custom CNAME records
The Canonical Name (CNAME) record allows a machine or host to be referenced by more than one name.
A CNAME can be used to define an alias host name. You can also use aliases when a host changes its name.
If you have selected CNAME record, the following page appears:
In the case of CNAME records, the values have the same format
as in the A record with the exception of the Data field.
In the Data field you have to enter the name of the server
to which you are creating the alias record.
WARNING: Please pay attention to $ORIGIN when you add a CNAME
The DNS records you create appear on the zone management page:
You can't edit DNS records. To remove unnecessary records, click the Trash icon