It appears that Paul Hoffman <paul.hoff...@icann.org> said: >> Not all record types are encoded as one or more <character-string>'s, >> for instance the SOA RDATA encodes two <domain-name>'s followed by five >> 32-bit integers. Should that be represented like this? >> >> ["DUJ", [["add", "yourname.example", "SOA", >> "ns1.yourname.example", "hostmaster.yourname.example", "2024112101", >> "7200", "3600", "604800", "60"]]] >> >> Or like this? >> >> ["DUJ", [["add", "yourname.example", "SOA", >> "ns1.yourname.example hostmaster.yourname.example 2024112101 7200 3600 >> 604800 60"]]] > >The latter, according to a normal reading of RFC 1035. Nothing in Section >3.3.13 suggests that the fields are <character-string>s; neither does the >example in Section 5.3 there.
Sec 3.3.13 is about the wire format and says nothing about the zone file format. Take another look at 5.3. The numbers in the SOA are separate tokens, grouped with parens so they can be spread over several lines, and with comments that are ignored. This is all described in 5.1. R's, John _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
