bk99.de entertain the web since 1997

bk99.de
RFC · DNSStandard explained

RFC 1035: DNS messages and resource records

Summary

RFC 1035 specifies the DNS packet format, resource records and the communication between resolvers and servers. A compact binary format was crucial for global scalability. Extensions have to cope with old resolvers and limited packet sizes.

Ideas

  • Resource records combine name, type, class, TTL and data.
  • Transaction IDs match answers to their queries.
  • UDP serves short answers, TCP handles larger or special transfers.

Facts

  • RFC 1035 replaces RFC 882.

Remarks

  • RFC 1035 has the status “Internet Standard”; current errata and successor documents should also be checked.

Recommendations

  • Test authoritative answers over UDP and TCP.
  • Validate zone data before every publication.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 2018

RFC 8484: DNS over HTTPS

RFC 8484 encapsulates DNS queries in HTTPS and thereby uses existing web transport and authentication mechanisms. DoH makes path-based observation and classic network diagnostics harder at the same time. Choosing the resolver remains a decision of trust.

RFC · 2016

RFC 7858: DNS over TLS

RFC 7858 describes encrypted DNS transport over TLS between a client and a recursive resolver. Transport encryption protects the path, not against the chosen resolver. Encryption can reduce observation and centralise trust.

RFC · 2003

RFC 3490: Internationalised domain names

RFC 3490 introduced IDNA so that Unicode domain names can be carried over the ASCII-based DNS. RFC 3490 was superseded by RFC 5890. Compatibility layers extend old infrastructure without breaking the protocol.