RFC 882/883 DNS is not interoperable with RFC 1034/1035

RFC 973 enumerates the changes between RFC 882/882 and RFC 1034/1035. There are several compatibility breaks:

* TTLs and serial numbers expanded from 16 bits to 32 bits: this breaks wire format compatibility;

* wildcard semantics change: an 882/883 implementation will handle them incorrectly;

* master file syntax changes: modern master files will be read incorrectly by an 882/883 parser

* CNAME semantics change: modern DNS data is probably compatible with 882/883 semantics but not the other way round;
This commit is contained in:
Tony Finch 2018-03-29 13:32:03 +01:00 committed by GitHub
parent 5f0562ffca
commit 49c2ce82f7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -24,9 +24,9 @@ administrators.
DNS was originally written down in August 1979 in '[IEN
116](https://www.rfc-editor.org/ien/ien116.txt)', part of a parallel
series of documents describing the Internet. IEN 116-era DNS is not
compatible with today's DNS. In 1983, RFC 882 was released, and stunningly
enough, an implementation of this 35 year old document would function
on the internet and be interoperable.
compatible with today's DNS. In 1983, RFC 882 and 883 were released,
describing a version of the DNS very similar but not quite interoperable
with the one we have today.
DNS attained its modern form in 1987 when RFC 1034 and 1035 were published.
Although much of 1034/1035 remains valid, these standards are not that easy