DNS Record Registration Rules
Information Required for Record Registration
- A record consists of Name, TTL, Type, Value, Comment, and Label.
- Name, Type, and Value are required.
- For TTL, select whether to use the default TTL or enter an arbitrary value.
- Entering a Comment and Label is optional.
- You cannot register more than one record that has the same combination of Name and Type.
- You can register more than one record that has the same Name unless Type is the same.
- Multiple Values can be registered with respect to each combination of Name and Type.
Round-robin setting example
Name TTL Type Value Notes www.example.jp. 300 A 192.0.2.1
192.0.2.2You can increase the number of input fields by clicking the (+) icon in the Values column. - Refer to the following descriptions for detailed registration rules for each item.
Name
- For Name, the following rules further apply in accordance with "Common Rules for Host Names."
- When the last character of Name is a dot (.), Name must be either the zone name or the subdomain of the zone.
Example: When the zone name is example.jp, "example.jp." and "www.example.jp." can be registered, but "example.com." cannot be registered. - An asterisk (*) can be used as a label that represents a wildcard. Note, however, that some Types, such as an NS record, cannot be set as a wildcard record.
- When the last character of Name is a dot (.), Name must be either the zone name or the subdomain of the zone.
- Special treatment is given to columns whose Name is "$TTL." These columns are used to set a TTL default value. Refer to the rules for "TTL."
TTL
- Select whether to enter an arbitrary integer from 1 to 2147483647 or use the default TTL value. The unit is seconds.
- The default TTL can be changed to an arbitrary integer from 1 to 2147483647 by editing a record whose Name is $TTL.
- When the setting is configured to use the default TTL, the display on the control panel will be blank.
Type
- Select from the pull-down menu.
- Record types that are not present in the pull-down menu cannot be set.
Value
- Registration rules differ for each Type. Refer to "Registration Rules for Each Record Type."
- Unless you have limits based on the registration rules for each Type, you can register multiple values with respect to a single record.
- You can increase the number of input fields by clicking the (+) icon in the Values column.
- Even if you register the same value multiple times, only one value will be effective.
Comment
- You can register up to 80 characters as a comment for each record (for each combination of Name and Type).
Label
- You can register a Label for each record. Refer to "Labels" for more information.
Common Rules for Host Names
- When the host name consists of a single at mark (@), the zone name itself will be the host name.
- For example, when the zone name is "example.jp.", "@" becomes "example.jp.".
- Unless the last character of the host name is a dot (.), the zone name itself will be complemented to the end of the host name.
- For example, when the zone name is "example.jp.", "www" becomes "www.example.jp.".
- Each label that is separated with a dot (.) has at least one character and 63 characters at maximum. The entire length of a domain name must be 254 characters or less, including the trailing dot.
- The types of characters that can be used for each label separated with a dot (.) are alphabetic characters, numerals, and hyphens (-).
- Underlines (_) can also be used for some record types.
- Alphabetic characters are case-insensitive ("example.jp." and "EXAMPLE.JP." are regarded as the same name).
- Perform Punycode conversion on domain names that contain characters other than alphabetic characters, such as a domain name in Japanese.
Registration Rules for Each Record Type
| Type | Registration rule | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SOA | A record that registers information about the zone itself.
| ||||||||||||||||||||||||||||||
| NS | A record that defines a name server.
| ||||||||||||||||||||||||||||||
| A | A record that defines IPv4 addresses.
| ||||||||||||||||||||||||||||||
| AAAA | A record that defines IPv6 addresses.
| ||||||||||||||||||||||||||||||
| MX | A record that defines email transfer destinations
| ||||||||||||||||||||||||||||||
| CNAME | A record that defines the canonical name with respect to the host name.
| ||||||||||||||||||||||||||||||
| SRV | A record that defines service locations.
| ||||||||||||||||||||||||||||||
| TXT | A record that registers arbitrary strings.
| ||||||||||||||||||||||||||||||
| CAA | A record for specifying a certificate authority (CA) that can issue a certificate for the domain name.
| ||||||||||||||||||||||||||||||
| TLSA | A record for setting TLS server certificates.
[ Reference ]When DNSSEC is not enabled (including when the DS record with a signature is not registered and when the client has not validated DNSSEC) as well as for applications that do not support TLSA records, TLSA records will be ignored even if they are described. | ||||||||||||||||||||||||||||||
| DS | A record that registers DNSSEC key hashes of a subdomain.
[ Reference ]This record is used to register DS records in a subdomain. Apply to register DS records of that domain with the parent zone. | ||||||||||||||||||||||||||||||
| NAPTR | A record for defining and searching various resources.
| ||||||||||||||||||||||||||||||
| PTR | A record that registers a reverse lookup host name.
| ||||||||||||||||||||||||||||||
SVCB HTTPS | Records to define information for connecting to the network service. While SVCB is used for general services, HTTPS is used for HTTP(S) services. Both of them have the same format.
| ||||||||||||||||||||||||||||||
| ANAME | A record for registering alias with respect to a host name. This is a unique record of this service. Refer to "ANAME Specifications" for more information.
|
Rules for File Upload Registration
- You can upload zone files whose format is RFC1035 (BIND format).
- Each record in a zone file is subject to the restrictions of the above registration rules.
- Be careful with the serial value of the SOA record. Although you can upload values smaller than the current serial number, the value will not be reflected correctly on the Managed DNS Server.
- There are two patterns when you upload a file: a pattern in which a comment is registered, and a pattern in which a comment is not registered.
Pattern in which a comment is registered
www 86400 IN A 192.0.2.1 ; Registered only when a comment is assigned to the end of the record line that is completed in a single line.
Pattern in which a comment is not registered
; Comment not to be registered @ 86400 IN SOA ( ns dns-admin ; Comment not to be registered 86400 3600 604800 900 ) ; Comment not to be registered www 86400 IN A 192.0.2.1 86400 IN A 192.2.2.2 ; Comment not to be registered
- Comments in the pattern in which a comment is not registered are ignored, and therefore no error occurs.
- Use UTF-8 as the character code for comments.
- If even one record that cannot be registered is included in the zone file, all the processes will end in failure.
- As all the processes have been completed successfully, the entire zone is replaced with the uploaded zone file.
- To add some records, it is necessary to upload the entire zone file instead of only uploading the records to be added.
Rules for Using the Zone Proxy Function
- ANAME is not supported.
- Some restrictions are eased in some cases. An example is when records containing Type, which cannot be selected by editing from the control panel, are also allowed.
- Be careful with the serial value of the SOA record. A value smaller than the current serial number will not be accepted.