> > > We already have a problem with too many TXT records with the same name > used for different purposes. SPF, various validations, and who knows what > else are all at the same name. Could we do instead: > _RFCxxxx.domain.name IN TXT "<data>" > > That reduces the packet size and the amount of records that the > application has to process and discard, since it will only ask for its own > records. >
Agree with you Bob that this is an important decision (whether to do it subdomain or as apex), I can include your feedback in the updated RFC, Here is what I think the tradeoffs of each: (please correct me as wrong) - Subdomain approach (`_rfcxxx.domain.name IN TEXT "<data>"`) is usually managed in a zone *under* `domain.name`, making it more separate, and less spammy, and enable larger numbers of records - Apex TXT approach is usually managed in the zone *of* `domain.name`, making it easier to manage, and if the parent zone want to delegate child zone out, having apex TXT record method doesn't interfere with that too. > > -- > Bob Harold > >
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
