master files are ASCII files. Non printable ASCII is encoded as \DDD in TXT fields and domain names with the additional constraint that space is encoded as \032 in domain names. Binary in other fields is encoded as base64, base32hex, hex and other rdata specific encodings. The DNS presentation format for all records only emits ASCII.
If you have a file that contains u-labels it is not as master file. It can be converted to a master file by processing the labels and turning them into a-labels. Master files are supposed to be able to be processed by nameservers that are not IDNA aware. If you use master files extensions such as $TTL, $DATE and $GENERATE then you need to ensure that the nameserver can process them. A cannonical version of the master file contains none of these extensions. Additionally you need to be aware of what types the nameservers supports otherwise you should encode all non RFC 1034 records as unknown types. Unfortunately RFC 103[45] failed to specicify how to encode unknown types in master files which makes it impossible to have a master files that contains new types be readable by all nameservers in existence. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
