AZ Tools

DNS レコードリファレンス

ネットワーク

実際に遭遇する DNS レコードタイプのクイックリファレンス — 用途、注意点(例:CNAME はゾーン apex に置けない)、zone-file の具体例。一般的なセット + DNSSEC + HTTP/3・ECH 用の新しい SVCB / HTTPS レコード。

A

Maps a hostname to an IPv4 address. The most common record — every domain that resolves to a server has at least one.

Zone-file の例

example.com.   IN  A      93.184.216.34
AAAA

Maps a hostname to an IPv6 address. Pronounced "quad-A".

Zone-file の例

example.com.   IN  AAAA   2606:2800:220:1:248:1893:25c8:1946
CNAME

Aliases one hostname to another. The target must itself resolve; CNAMEs cannot coexist with other records at the same name, and cannot appear at the apex (root) of a zone.

Zone-file の例

www.example.com.   IN  CNAME  example.com.
MX

Mail exchanger — where SMTP for the domain should be delivered. Includes a priority (lower = preferred).

Zone-file の例

example.com.   IN  MX  10 mail.example.com.
TXT

Arbitrary text. Used for SPF (mail anti-spoofing), DKIM keys, domain verification (Google, Facebook, etc.), and human-readable notes.

Zone-file の例

example.com.   IN  TXT  "v=spf1 include:_spf.google.com ~all"
NS

Delegates a (sub)domain to a set of authoritative name servers. Every zone has NS records at its apex.

Zone-file の例

example.com.   IN  NS  ns1.example.com.
SOA

Start of Authority — administrative info for the zone: primary name server, hostmaster email, serial number, and TTLs for negative caching.

Zone-file の例

example.com.   IN  SOA  ns1.example.com. hostmaster.example.com. 2025010101 7200 3600 1209600 3600
PTR

Reverse lookup — maps an IP back to a hostname. Lives under the `in-addr.arpa` (v4) or `ip6.arpa` (v6) zones.

Zone-file の例

34.216.184.93.in-addr.arpa.   IN  PTR  example.com.
SRV

Locates the host and port for a named service (with priority and weight). XMPP, SIP, and Microsoft AD all use SRV.

Zone-file の例

_sip._tcp.example.com.   IN  SRV  10 60 5060 sipserver.example.com.
CAA

Certification Authority Authorization — restricts which CAs may issue TLS certs for the domain. Modern CAs are required to check CAA before issuing.

Zone-file の例

example.com.   IN  CAA  0 issue "letsencrypt.org"
DNSKEY

DNSSEC public key used to verify signatures in the zone. Paired with RRSIG records.

Zone-file の例

example.com.   IN  DNSKEY  257 3 13 mdsswUyr3DPW132mOi8V9xESWE8jTo0d…
DS

Delegation Signer — published at the parent zone to fingerprint the child zone's DNSKEY. Forms the DNSSEC chain of trust.

Zone-file の例

example.com.   IN  DS  31589 13 2 3490A6806D47F17A34C29E2CE80E8A999FFBE4BE…
RRSIG

Resource Record Signature — cryptographic signature over a record set, validated against the zone's DNSKEY. Added automatically when the zone is signed.

Zone-file の例

example.com.   IN  RRSIG  A 13 2 300 20260101000000 …
NSEC / NSEC3

DNSSEC "authenticated denial of existence" — proves a record does not exist. NSEC3 hashes names to discourage zone walking.

Zone-file の例

example.com.   IN  NSEC  www.example.com. A NS SOA MX TXT RRSIG NSEC
TLSA

DANE — binds a TLS certificate (or its public key) to a hostname via DNSSEC. Lets clients verify certs without trusting a CA.

Zone-file の例

_443._tcp.example.com.   IN  TLSA  3 1 1 ABCD…
SVCB / HTTPS

Service Binding — advertises alternative endpoints, ALPNs, port, and ECH config for a service. `HTTPS` is the HTTPS-specific subtype enabling HTTP/3 and ECH.

Zone-file の例

example.com.   IN  HTTPS  1 . alpn="h3,h2"
NAPTR

Rewrites a name to a URI / regex result. Used by ENUM and SIP for service discovery.

Zone-file の例

example.com.   IN  NAPTR  100 10 "u" "E2U+sip" "!^.*$!sip:info@example.com!" .
LOC

Geographic location — latitude, longitude, altitude. Rarely used in practice.

Zone-file の例

example.com.   IN  LOC  37 30 N 127 0 E 30m
ALIAS / ANAME

A non-standard "flattened CNAME" supported by some providers (Route 53 alias, Cloudflare CNAME flattening). Lets you point the zone apex at another hostname.

Zone-file の例

example.com.   IN  ALIAS  app.example.cdn.com.

使い方

  1. 検索ボックスにレコードタイプ (`mx`) またはキーワード (`mail`、`dnssec`) を入力。
  2. 説明と zone-file の例を確認。
  3. タイプチップのコピーボタンでレコード名を zone file にドロップ。

よくある質問

なぜ CNAME は apex に置けない?
すべてのゾーンが apex に SOA と NS をサーブする必要があり、CNAME は同じ名前で他のレコードタイプと共存できないため。ALIAS / ANAME(プロバイダ固有の flattening)や HTTPS レコードで回避。
SVCB と HTTPS の違いは?
どちらも Service Binding レコード。`HTTPS` はブラウザが自動的にクエリする HTTPS 専用サブタイプ — HTTP/3 (`alpn=h3`)、代替ポート、Encrypted Client Hello (ECH) 設定を広告。`SVCB` は他のプロトコル用の汎用形式。
CAA は必要?
技術的には任意だが強く推奨 — なければどの公的 CA でもドメインの証明書を発行できる。`0 issue "letsencrypt.org"`(または使用中の CA)を追加して発行をその機関に制限。

関連ツール