Subject: Re: [DNSOP] Fundamental ANAME problems Date: Sat, Nov 03, 2018 at 12:04:18PM -0700 Quoting Joe Abley ([email protected]): > On Nov 3, 2018, at 03:20, Bob Harold <[email protected]> wrote: > > > My preference would be a *NAME record that specifies which record types it > > applies to. So one could delegate A and AAAA at apex to a web provider, MX > > to a mail provider, etc. That would also be valuable at non-apex names. > > But I am happy to support ANAME as part of the solution. > > I don't understand this suggestion. > > Some use-cases (or even hypothetical examples) might help.
example.org. IN SOA foo bar 2018102802 300 3600 3600000 300 example.org. IN NS primary.se. example.org. IN NS secondary.se. example.org. IN MX 10 some.host.gmail.com _http._tcp.example.org. IN URI 10 20 "https://example-lb-frontend.hosting.namn.se:8090/path/down/in/filestructure/"; example.org. IN TXT "v=spf0x41 not valid. because SPF records belong in RRtype 99." example.org. IN AFSDB 1 db0.example.org. example.org. IN AFSDB 1 db1.example.org. example.org. IN AFSDB 1 db2.example.org. example.org. IN SPF "v=spf1 +all" We already have this. We need not build a new mechanism. /Måns, sounding like a broken record. -- Måns Nilsson primary/secondary/besserwisser/machina MN-1334-RIPE SA0XLR +46 705 989668 Is this an out-take from the "BRADY BUNCH"?
signature.asc
Description: PGP signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
