AZ Tools

DNS 레코드 참조

네트워크

실제로 마주치는 DNS 레코드 타입의 빠른 참조 — 용도, 주의점(예: CNAME은 zone 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에 못 사는 이유?
모든 zone이 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) 추가로 해당 기관으로 발급 제한.

관련 도구