Based on some feedback we received, I created a draft that describes what to do if you want to build a proxy that acts as an authoritative server in an anycast setup. The draft just describes the basics, if there is interest we can add the details.
Name: draft-homburg-dnsop-igadp Revision: 00 Title: Implementation Guidelines for Authoritative DNS Proxies Date: 2023-10-17 Group: Individual Submission Pages: 5 URL: https://www.ietf.org/archive/id/draft-homburg-dnsop-igadp-00.txt Status: https://datatracker.ietf.org/doc/draft-homburg-dnsop-igadp/ HTML: https://www.ietf.org/archive/id/draft-homburg-dnsop-igadp-00.html HTMLized: https://datatracker.ietf.org/doc/html/draft-homburg-dnsop-igadp Abstract: In some situations it be can attractive to have an authoritative DNS server that does not have a local copy of the zone or zones that it serves. In particular in anycast operations, it is sensible to have a great geographical and topological diversity. However, sometimes the expected use of a particular site does not warrant the cost of keeping local copies of the zones. This can be the case if a zone is very large or if the anycast cluster serves many zones from which only a few are expected to receive significant traffic. In these cases it can be useful to have a proxy serve some or all of the zones. The proxy would not have a local copy of the zones it serves, instead it forwards request to another server that is authoritative for the zone. The proxy may have a cache. This document describes the details of such proxies. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
