Common use of File Format Standard Clause in Contracts

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇RF▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ RFC ▇▇▇▇, Section ▇▇ction 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows:in 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X /\X and /DDD /\DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain- name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name> <TTL> <class> <type> <RDATAdomain-name>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X /\X and /DDD /\DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name< domain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format SubLformat is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomainLname> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat sub- format of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “"@” " to denote current origin. 10. No use of “"blank domain names” " at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐name< domain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain- name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar. 25. Section 2.1.5 of Specification 4 is hereby amended and restated in its entirety as follows:

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain‐name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X \X and /DDD \DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each zone goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain-­‐ name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “@” to denote current origin. 10. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

File Format Standard. Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat sub- format of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇RFC 1035, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format Sub-format is as follows: 1. Each record must include all fields in one line as: <domain-­‐namedomain-name> <TTL> <class> <type> <RDATA>. 2. Class and Type must use the standard mnemonics and must be in lower case. 3. TTL must be present as a decimal integer. 4. Use of /X and /DDD inside domain names is allowed. 5. All domain names must be in lower case. 6. Must use exactly one tab as separator of fields inside a record. 7. All domain names must be fully qualified. 8. No $ORIGIN directives. 9. No use of “"@” " to denote current origin. 10. No use of “"blank domain names” " at the beginning of a record to continue the use of the domain name in the previous record. 11. No $INCLUDE directives. 12. No $TTL directives. 13. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. 14. No use of comments. 15. No blank lines. 16. The SOA record should be present at the top and (duplicated at) the end of the zone file. 17. With the exception of the SOA record, all the records in a file must be in alphabetical order. 18. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.