Please click here for an overview of the DNS records supported by GeoScaling and on short descriptions of the most important ones, along with examples. If you're a beginner, read the overview before reading this page, as this document assumes that you know what A, MX, and CNAME records are.
Once you define a domain name and click on it, you will see the following form:
Not all fields in the Add record box are used for all types of records you can add. For example, A records don't have priorities, like MX records do. So just ignore the extra fields in the form and fill in only the ones you need.
You can see the following fields in the form:
name - this is where you define the name of the subdomain in A and CNAME records.
type - here you can select the type of records you are adding
content - here you define the IP address in case of A records or where the alias is pointing in case of CNAMEs
ttl - ttl means
Time-to-live. This is a numeric field that defines the number of seconds DNS2 results can be cached by a client or a recursive nameserver. 300 is the default value, which means 5 minutes. If you set this value higher than the default of 5 minutes, it will take more time for any changes you make to the record to propagate everywhere on the Internet. You cannot define a value less than 300 here without our
assistance.
priority - this field is used when adding MX or SRV records. Here's a quote from Wikipedia about MX priorities: “When a server decides to send
SMTP mail, the relative priority of an MX server is determined by the preference number present in the
DNS MX record of the recipient's domain. When a remote client (typically another mail server) does an MX lookup for the domain name, it gets a list of servers and their preference numbers. The smallest preference number has the highest priority and any server with the highest priority must be tried first. To provide reliable mail transmission, the
SMTP client must be able to try (and retry) each of the relevant addresses in this list in order, until a delivery attempt succeeds. If there is more than one MX record with the same preference number, all of those must be tried before moving on to lower-priority entries.”