Description
The most used DNS record types are explained here. In the Leaseweb Customer Portal, when adding/editing a DNS record, you need to tát select the correct DNS type.
Contents
TXT records
Text (TXT) records are used often with other protocols or systems. For instance, the SPF system uses TXT records to tát hold its information. Another use is for tên miền verification. Sometimes when a trang web needs to tát validate the owner of a tên miền, they ask the owner to tát create a TXT record with some information in it. It is then checked, and if the correct record is found, the tên miền owner can be verified.
SPF Records
An SPF record is a line of plain text that includes a list of tags and values. The tags are called mechanisms, and the values are typically IP addresses and tên miền names. If you are using SPF records for Leaseweb, choose the appropriate record based on the region:
- For NL: v=spf1 include:mh-spf.leaseweb.com ~all
- For US: v=spf1 include:mh-spf.leaseweb.us ~all
Explaining what the values mean in the above example:
|
Value |
What does it mean ? |
|---|---|
|
v=spf1 |
This means the SPF version being used is version 1. |
|
ip4:89.238.146.98 |
This means that the IPv4 address ‘89.238.146.98’ is allowed to tát send gmail from this tên miền. |
|
ip4:62.212.64.0/24 |
This means that the IPv4 range 62.212.64.0 through 62.212.64.255 is allowed to tát send gmail from this tên miền. |
| ip6:2001:1af8:4100:2::40 | This means that the IPv6 address ‘2001:1af8:4100:2::40’ is allowed to tát send gmail from this tên miền. |
| ip6:2001:1af8:4100:2::/64 | This means that the IPv6 range specified is allowed to tát send gmail from this tên miền. |
|
a:mail.leaseweb.com |
The IP address behind the A record of mail.leaseweb.com is allowed to tát send gmail from this tên miền. |
|
mx |
This means that all the MX records for this tên miền are allowed to tát send emails. |
|
Include |
Authorize third-party gmail senders by tên miền, for example: include:servers.mail.net |
|
~all |
If you put this at the kết thúc of the SPF rule, it means that if an gmail does not match this rule, we ask the receiving mail server not to tát throw it away but to tát keep it under SPAM thư mục. If we were to tát change this to tát ‘-all’ (note the – sign), we ask it to tát instead throw away all gmail not matching this rule. |
DMARC Records
This record is a DNS TXT record published in a domain’s DNS database that tells receiving mail servers what to tát bởi with messages that don’t align or authenticate with SPF and DKIM. The DMARC record enables reports to tát be sent back to tát the tên miền owner about which messages are authenticating and why.
SOA records
Information
Not editable
SOA records are part of the DNS infrastructure. They are generated automatically and are not editable.
A Start of Authority (SOA) resource record is the information stored in a Domain Name System (DNS) zone about that zone and other DNS records. A DNS zone is the part of a tên miền for which an individual DNS server is responsible. Each zone contains a single SOA record.
The SOA record stores the following information about a zone:
- Administrator of the zone
- Current version of the data file
- Default number of seconds for the Time to tát Live (TTL) tệp tin on resource records
CNAME records
Information
Please note that a CNAME is not a redirect. If you create a CNAME for a trang web, it will not redirect it to tát another tên miền. It will point the CNAME record to tát the IP listed at the original record.
Canonical Name (CNAME) records are used to tát create aliases for other DNS records.
This is convenient when running multiple services (such as an FTP server and a trang web server – each running on different ports) from a single IP address. For example, you can point ftp.example.com and www.example.com to the A record server.example.com, which in turn points to tát the IP address.
If you ever need to tát change the IP address, you only have to tát change it in one place. CNAME records must always be pointed to tát another tên miền name, never to tát an IP address. A CNAME must always be a sub-domain record.
MX records
Mail Exchanger (MX) records are used to tát help mail servers that are trying to tát send emails to tát your tên miền, and find the servers that are accepting emails for your tên miền. It is recommended to tát have more phàn nàn one MX record for your tên miền. You can add MX records to tát your full tên miền or for sub domains. For example, I can add MX records for test.domain.com and for domain.com. Emails sent to test.domain.com will go to tát the MX records created for that tên miền.
Priority
It is recommended to tát have multiple mail servers for each tên miền – and priority plays a critical role in this. For each MX records you add, you will have to tát enter a priority. This determines which mail server gets picked first. The MX record with the lowest priority will always be the first mail server where emails will be sent. If that server is down or fails for some other reason, the next mail server is picked. For example:
| Server | Priority | Description |
|---|---|---|
| mailfilter1.leaseweb.com | 10 | This mail server will always be tried first. If this mail servers does not work, the next one in the list will be tried. |
| mailfilter2.leaseweb.com | 10 | If the first mail servers does not work for some reason, these mail server(s) will be tried. You can see that we have placed 2 servers with the same priority. This means that DNS will pick one of the two at random. This is called Round Robin DNS, for more information on this, please visit this page. |
| mailfilter3.leaseweb.com | 10 |
Priority can be any number. In the example above, we have used increments of 10, but you could also use the values 1,2,3,4.
Pointing your MX record to tát your server.
If you wish to tát point your MX record(s) to tát your server you make sure to
- Create an A record e.g. “mail.example.com” with your server’s IP.
- Create an MX record with “mail.example.com” as the target.
A records
Address (A) records are the most basic of DNS records. They provide a way to tát translate host name into IP addresses. When creating an A record, you can fill in any sub-domain for your tên miền, and after the host name, you can fill in any IP address (either internal or external).
Adding more phàn nàn one record per subdomain
It is possible to tát add more phàn nàn one record to tát any sub-domain. For example, if you have the tên miền “example.com“, and you have added two A records:
When a user requests the IP address for “test.example.com“, it will get 127.0.0.1. When another user requests the same host name, it will get 127.0.0.2, the next one will get 127.0.0.1 again, and this continues. This method is called Round Robin DNS. For more information on this, please visit this page.
AAAA Records
IPv6 Address (AAAA) records work the same as an A record. The difference is that an A record is used for IPv4 addresses, while the AAAA record is used for IPv6 addresses.
For more information on the new IPv6 protocol, please visit DNS Record Types.
SRV records
Service (SRV) records provide information on available services for your systems. A SRV record has a unique system for naming.
The SRV record also has the following fields:
- Name – The naming system is an underscore followed by the name of the service, a period, an underscore, the protocol, a dot, and then the name of the tên miền (the name of the tên miền you bởi not need to tát include in DNS Made Easy of course).
- Host – The system that will receive the service.
- Priority – This acts the same way as the MX Level / preference in the MX record. The lower the number in the priority field, the more desirable the associated target. 0 is the highest priority (lowest number).
- Weight – Allows the zone administrators to tát distribute load to tát multiple targets (load balance). It is basically used to tát determine relative capacity and load between two SRV fields within the priority. Hits will be assigned proportionately by weight. This allows the administrators to tát have a powerful and a weak server, and share the appropriate loads between those systems. 0 is the lowest load.
- Port – the actual port of the service offered.
Example: _http._tcp.example.com. SRV 0 0 80. www.example.com.
This would make the trang web requests for “example.com” go to tát “www.example.com.”. 0 is the highest priority (lowest number) and 0 is the highest weight (lowest number).
DS records
(Delegation Signer): This records are used to tát secure delegations (DNSSEC). A DS record with the name of the sub-delegated zone is placed in the parent zone along with the delegating NS Records. This DS record references a DNSKEY record in the sub-delegated zone
NS records
(Name Server Record): This record identifies the authoritative name servers for a tên miền.
PTR records
(Pointer Record): This records maps an IP address to tát a tên miền name.
DNSKEY records
(DNS Public Key Record): This stores the public key used for DNSSEC (Domain Name System Security Extensions), which is used to tát add an extra layer of security to tát DNS queries.
CAA records
(Certification Authority Authorization): This records allow tên miền owners to tát declare which certificate authorities are allowed to tát issue a certificate for a tên miền. They also provide a means of indicating notification rules in case someone requests a certificate from an unauthorized certificate authority. If no CAA record is present, any CA is allowed to tát issue a certificate for the tên miền. If a CAA record is present, only the CAs listed in the record(s) are allowed to tát issue certificates for that hostname.
TLSA records
The TLS Authentication record (TLSA) is used to tát associate a TLS server certificate or public key with the tên miền name where the record is found. With a TLSA record, you can store the fingerprint of a TLS/SSL certificate in the DNS of your tên miền. TLSA records can only be trusted if DNSSEC is enabled on your tên miền.