RFC 4343: Domain Name System (DNS) Case Insensitivity Clarification
In plain English — editorial summary, not part of the RFC
Domain Name System (DNS) names are "case insensitive". This document explains exactly what that means and provides a clear specification of the rules. This clarification updates RFCs 1034, 1035, and 2181. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4343
- Published
- January 2006
- Authors
- D. Eastlake 3rd
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 5890
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4361Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)Updated
February 2006
- RFC 4311IPv6 Host-to-Router Load SharingCurrent
November 2005
- RFC 4388Dynamic Host Configuration Protocol (DHCP) LeasequeryUpdated
February 2006
- RFC 4389Neighbor Discovery Proxies (ND Proxy)Current
April 2006
- RFC 4390Dynamic Host Configuration Protocol (DHCP) over InfiniBandCurrent
April 2006
- RFC 4391Transmission of IP over InfiniBand (IPoIB)Updated
April 2006
- RFC 4295Mobile IPv6 Management Information BaseCurrent
April 2006
- RFC 4294IPv6 Node RequirementsObsoleted
April 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?