3 ms·
It’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 stup
by teddyh 6y ago
It’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.