<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Greetings bind-users,</div><div class=""><br class=""></div><div class="">The `map` zone file format was introduced in BIND 9.10. <a href="https://bind9.readthedocs.io/en/v9_16_20/reference.html?highlight=map zone#additional-file-formats" class="">https://bind9.readthedocs.io/en/v9_16_20/reference.html?highlight=map%20zone#additional-file-formats</a></div><div class=""><br class=""></div><div class="">At the time, this format significantly sped up a named restart, which could take several hours in some situations. This new file format is very complicated, and maintaining it has proven difficult. Meanwhile, the performance advantage versus the `raw` format, or the default text files, has decreased as we have made other improvements in performance. </div><div class=""><br class=""></div><div class="">We would like to deprecate the `map` zone file format in future branches of BIND. The proposal is to deprecate the feature in the 9.16 branch, (users will see a warning when this feature is used but it will still work through the end of the 9.16 branch), and to disable the feature in 9.20.0 (it will no longer work in this and subsequent versions). </div><div class=""><br class=""></div><div class="">Per our policy on deprecating named options, we are notifying the user mailing list. You are welcome now to howl in protest or point out something we haven’t considered. ;-)</div><div class=""><br class=""></div><div class="">Regards,</div><div class=""><br class=""></div><div class="">Vicky Risk</div><div class="">Product Manager</div></body></html>