5 ms·
Sigh, it isn't a BIND zone file, it's a standard RFC 1035 zone file https://tools.ietf.org/html/rfc1035#section-5 https://tools.ietf.org/html/rfc1035#section-5
by fanf2 6y ago
Sigh, it isn't a BIND zone file, it's a standard RFC 1035 zone file https://tools.ietf.org/html/rfc1035#section-5 https://tools.ietf.org/html/rfc1035#section-5 If you want to tie it to a particular piece of software then JEEVES would be more accurate :-) https://www.icann.org/en/system/files/files/rssac-023-17jun20-en.pdf https://www.icann.org/en/system/files/files/rssac-023-17jun2...
- tptacek 6y agoIt's a BIND zone file, and the elevation of an implementation detail to a standard is an artifact of a time --- a bad time --- where BIND was the only mainstream option for authority servers. That the file itself originates in an earlier piece of software doesn't change that. The DNS doesn't interoperate through "zone files", but through the DNS protocol itself. Modern zones don't even have "files".
- teddyh 6y agoIt’s a standardized format for serializing DNS data to ASCII text and back. There’s nothing wrong with that. This is like complaining that Lisp syntax is stupid since no Lisp implementation stores the Lisp syntax as ASCII, but stores it as the parsed AST. This does not make the Lisp syntax for humans any less useful. Would you prefer it if every DNS implementation had its own text syntax for DNS records?
- tptacek 6y agoDNS implementations do have their own syntax for DNS records! The implementation details of how DNS servers choose to represent records are not properly part of the DNS standard. You saw this play out in the early days of tinydns/djbdns, when people on namedroppers accused djbdns of being noncompliant because it used a different format. The whole point of the DNS protocol is that systems interoperate through the protocol, which exists exclusively for that purpose. Zone files aren't an interchange format.
- teddyh 6y ago> Zone files aren't an interchange format. Oh yes they are. It’s an everyday occurence to export a zone from one name server to standard “master zone file” format and then import that into another name server running some other software DNS implementation. Having a standardized file format for machine-readable DNS data is extremely useful. It’s also used as an interchange format between people, so that people can talk about DNS data structure in technical detail without having to either send binary DNS data to each other or use some program-specific syntax, which might be misunderstood or be incomprehensible by users of some other program. You might want to argue that it’s a bad format, and you should feel free to do that. However, to argue that the RFCs either are wrong and don’t exist, and the standard “master file” format somehow is some program-specific format, when the format is clearly and demonstrably used by most extant DNS servers (if only for import/export) and is useful for a number of things, is not productive discourse.
- tptacek 6y ago1035 is The DNS RFC. Using BIND's archaic zone file format is in no sense a requirement to interoperate with other DNS protocol servers. You could argue that the IETF should have another RFC specifying the zone file format; what could be wrong with standardizing a file format? Standardize my iTunes Library database file while you're at it; that would help far more people. But it has nothing to do with provisioning DNS service, and the claim that BIND zone files have any kind of special status is bogus, despite what 1035 mistakenly says.
- teddyh 6y agoDoes RFC 1035 specify that the master zone file format must be used to provision DNS service? If it does not, then RFC 1035 just happens to specify both the DNS protocol and a canonical ASCII serialization of DNS zone data.
- belorn 6y ago> Standardize my iTunes Library database file There is a de facto standardized computer file format for playlists, called Moving Picture Experts Group Audio Layer 3 Uniform Resource Locator, and it is supported by iTunes together with basically every music player and device cable of playing music. It is one of the few file formats where you can take a file that is 20 years old and it still works to create a play list anywhere.
- 1vuio0pswjnm7 6y agoTo defend your point, section 5 only says a "master file is most often used". It does not require the use of a master file to load a zone. Further, in section 5.2, it says "when a master file is used to load a zone". This suggests there could be occasions when a master file is not used to load a zone, e.g., a zone transfer. Correct me if I am wrong but I think one difference between tinydns and, say, nsd is that tinydns reads a zone file from disk to answer queries while nsd loads the entire file into memory. The whole "on-disk" concept seems a bit dated when one considers tinydns zone files are stored on mfs/tmpfs. I still use tinydns (and cdb) heavily. I think it is well-suited for the home user. BIND OTOH is an ever-changing, relatively large amount of code to compile, a hybrid authoritative server/cache, and it comes with a sizeable amount of complexity. BSD developers have long been trying to replace it with something else like unbound. djb used to refer to "the BIND company" and I think that is a reasonably accurate description of its developers. Thankfully, djbdns is non-commercial. Its author does not try to earn a living by monitoring/manipulating other people's DNS use.
- tptacek 6y agoPresumably, Route53 isn't serving DNS out of zone files either.
- fanf2 6y agoYou misunderstood my point that the zone file design was originally implemented in JEEVES, which was the first DNS server written by Paul Mockapetris; it did not come from BIND. Other servers such as NSD and Knot and PowerDNS support standard zone files, and many other DNS tools use the standard presentation format for printing and reading DNS records.