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

    NameTTLTypeValueNotes
    www.example.jp.300A

    192.0.2.1
    192.0.2.2

    You 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.
    • Name of a record you have registered once cannot be changed in "Edit Records." To change Name, refer to "FAQ (Q. I do not know how to change "Name" and "Type" of an existing DNS record.)."
  • 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
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
TypeRegistration rule
SOA

A record that registers information about the zone itself.

  • Name must be the same as the zone name when you register an SOA record.
  • Under normal conditions, you do not have to change it.
  • Register in "<mname> <rname> <serial> <refresh> <retry> <expire> <minttl>" format.
  • <mname> indicates the host name of the primary name server. Under normal conditions, you do not have to change it. Follow "Common Rules for Host Names."
  • <rname> is the administrator’s email address formed by replacing the at mark (@) with a dot (.). Follow "Common Rules for Host Names."
  • <serial> is the serial number. It is possible for you to change the value, but under normal conditions you do not have to change it because the system automatically updates it.
    • Although you can specify a value smaller than the current value for registration, the value will not be reflected on the Managed DNS Server. If you need to change the current value to a smaller one, use the RFC1982 procedure.
  • <refresh>, <retry>, and <expire> are parameters used to link to a secondary name server. Unless you perform zone transfer to a secondary name server you have prepared, you do not have to change them.
    • <refresh> is an integer from 600 to 86400, <retry> is an integer from 600 to 3600, and <expire> is an integer from 604800 to 1814400.
  • <minttl> is the negative cache TTL. It is an integer from 1 to 2147483647.
  • You cannot add or delete SOA records. In addition, you cannot register multiple Values.
  • Examples

    NameTTLTypeValue
    @
    SOAexample.jp. hostmaster.example.jp. 12345 3600 1800 604800 1800
NS

A record that defines a name server.

  • Refer to "Common Rules for Host Names" for information on name server names that can be registered.
  • When a name server name exists in the zone, an A record or an AAAA record must exist in the name server name.
  • You can set multiple name servers.
  • You cannot delete NS records that have the same name as the zone name.
  • Examples

    NameTTLTypeValue
    @
    NSns1.example.jp.
    ns2.example.jp.
A

A record that defines IPv4 addresses.

  • An A record cannot be defined in a Name that contains underlines (_).
  • You can set multiple IP addresses.
  • Examples

    NameTTLTypeValue
    www.example.jp.
    A192.0.2.1
AAAA

A record that defines IPv6 addresses.

  • An AAAA record cannot be defined in a Name that contains underlines (_).
  • You can set multiple IP addresses.
  • You can register valid IPv6 addresses regardless of whether or not normalization has been executed.
  • Examples

    NameTTLTypeValue
    www.example.jp.
    AAAA2001:db8::1
MX

A record that defines email transfer destinations

  • Configure the setting in "<preference> <hostname>" format.
  • You can set multiple email transfer destinations.
  • <preference> indicates the transfer priority. Set it using an integer from 0 to 65535.
  • <hostname> indicates the transfer destination host name. Refer to "Common Rules for Host Names."
  • When <hostname> exists in the zone, an A record or an AAAA record must exist in the host name.
  • Examples

    NameTTLTypeValue
    example.jp.
    MX10 mx1.example.jp.
    20 mx2.example.jp.
CNAME

A record that defines the canonical name with respect to the host name.

  • Refer to "Common Rules for Host Names" for information on canonical names that can be registered.
  • A name containing underlines (_) can be used for Name and Value.
  • Multiple Values cannot be registered.
  • A CNAME record cannot be set to a Name in which a different record type exists.
  • *CNAME cannot be set because there is always an SOA record and an NS record in the Name that are the same as the zone name. Use ANAME.
  • Examples

    NameTTLTypeValue
    foo.example.jp.
    CNAMEbar.example.jp.
SRV

A record that defines service locations.

  • You can set multiple locations.
  • Set Name in "_<service>._<protocol>.<domain name>." format.
    • For rules of strings to be specified for <service> and <protocol>, follow the service provider’s instructions.
  • Set Value in "<priority> <weight> <port> <hostname>" format.
    • All of <priority>, <weight>, and <port> are integers from 0 to 65535.
    • Refer to "Common Rules for Host Names" for information on <hostname>.
    • When <hostname> exists in the zone, an A record or an AAAA record must exist in the host name.
  • Refer to RFC2782 for more information about each parameter.
  • Examples

    NameTTLTypeValue
    _sip._tls.example.jp.
    SRV100 1 443 sip.example.com.
TXT

A record that registers arbitrary strings.

  • You can set multiple strings.
  • You can use a string that contains underlines (_) as the Name.
  • Enclose a string in double quotes (").
  • To include a double quote (") and/or backslash (\) within the string enclosed by "", prepose it with a backslash (\) as in "\"" and "\\".
  • You can define more than one string that is enclosed by "". Separate each string with a single-byte space.
    • Note that "Defining multiple strings in a single Value" and "Registering multiple Values" differ in meaning. Take extra care, because the meaning required differs depending on the usage.
  • The maximum length of a string enclosed by "" is 255 characters.
  • Examples
    • Defining a single string

      NameTTLTypeValueNotes
      example.jp.
      TXT"v=spf1 +ip4:192.0.2.0/24 -all"Example of a common SPF record
    • Defining multiple strings in a single Value

      NameTTLTypeValueNotes
      example.jp.
      TXT"v=spf1 " "+ip4:192.0.2.0/24 " "-all"SPF can be divided into multiple strings. (Be careful about space characters.)
    • Defining multiple Values

      NameTTLTypeValueNotes
      example.jp.
      TXT

      "MS=msXXXXXXXX"
      "google-site-verification=XXXXXXXX"
      "v=spf1 +ip4:192.168.0.2/24 -all"

      To set records for authentication required by some cloud business operators or to allow them to coexist with SPF, register multiple Values.
CAA

A record for specifying a certificate authority (CA) that can issue a certificate for the domain name.

  • You can set multiple values.
  • Configure the setting in "<flag> <tag> <value>" format.
  • For more information on the meaning and value of each parameter, refer to RFC6844 or follow the CA’s instructions.
  • Examples

    NameTTLTypeValue
    example.jp.
    CAA0 issue "ca.example.com"
    0 issuewild "ca.example.com"
    0 iodef "mailto:admin@example.jp"
TLSA

A record for setting TLS server certificates.

  • You can set multiple pieces of certificate information.
  • Set Name in "_<port>._<protocol>.<domain name>" format.
  • Set Value in "<usage> <selector> <type> <data>" format.
  • Refer to RFC6698 for more information of the meaning and value of each parameter.
  • Examples

    NameTTLTypeValue
    _443._tcp.example.jp.
    TLSA3 0 1 0123456789ABCDEF...
[ 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.

  • You can set multiple key hashes.
  • Configure the setting in "<keyid> <algorithm> <hashalgorithm> <digest>" format.
  • Normally, copy and paste the information output by the DNSSEC operation tool without changing it.
  • An NS record whose name is the same as the Name to be registered must be registered.
  • Examples

    NameTTLTypeValue
    sub.example.jp.
    DS12345 13 2 0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF01234567 89ABCDEF
[ 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.

  • You can set multiple values.
  • Configure the setting in "<order> <preference> <flag> <service> <regex> <replacement>" format.
  • Refer to RFC3403 for more information on each parameter.
  • Examples

    NameTTLTypeValue
    example.jp.
    NAPTR0 0 "se" "SIP+D2U" "" _sip._udp.example.jp.
PTR

A record that registers a reverse lookup host name.

  • Refer to "Common Rules for Host Names" for information on host names that can be registered.
  • Note that a dot (.) is normally required at the end of a host name.
  • A host name can be registered in a forward zone too, but you do not have to do so under normal conditions.
  • Examples

    NameTTLTypeValueNotes
    1.2.0.192.in-addr.arpa.
    PTRwww.example.jp.Example of reverse lookup of 192.0.2.1
    1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
    PTRwww6.example.jp.Example of reverse lookup of 2001:db8::1

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.

  • You can register multiple pieces of information.
  • Use a <svcpriority> <targetname> <svcparams> format to configure the setting.
  • <svcpriority> is a high-priority element for the connection (required). It must be an integer from 0 to 65535. While 0 represents AliaslMode, an integer other than 0 represents ServiceMode.
  • <targetname> is the connection destination host (required). Refer to "Common Rules for Host Names."
    • If "." is set, it is regarded as the Name itself.
  • <svcparams> is additional information (optional). It contains information in which <key>=<value> or <key> is enumerated.
  • Refer to draft-ietf-dnsop-svcb-https for more information on <key>, <value>, and other elements.
  • Examples

    NameTTLTypeValueNotes
    example.jp.
    HTTPS0 www.example.jp.AliasMode
    www.example.jp.
    HTTPS10 . alpn=h2 ech="abc..."
    10 www2.example.jp. alpn=h2 ech="xyz..."
    ServiceMode
    "." for <targetname> is the same as that "www.example.jp." is specified.
    _9999._foo.example.jp.
    SVCB0 svc.example.jp.AliasMode
    SVCB record corresponding to a URL "foo://example.jp:9999"
    svc.example.jp.
    SVCB1 foo.example.jp. foo=barServiceMode
    [ Reference ]

    As of 2022, there are many web browsers that do not support HTTPS records. Therefore, it is recommended that you use not only HTTPS records but also A/AAAA and ANAME records so that name resolution can also be performed with browsers that do not support HTTPS.

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.

  • Refer to "Common Rules for Host Names" for information on host names that can be registered.
  • An ANAME record can be registered only with a Name that is the same as the zone name.
  • It is not possible to register multiple ANAME records.
  • Examples

    NameTTLTypeValue
    @
    ANAMEwww.example.com.
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.