Tony says this: " It isn't a judgment about what's good, but an observation about what is done."
I can't stress this enough - when you see ALIAS records at zone cuts that point to a database server, already, then we've missed the "server specific" ball. And can someone show a significant number of SRV examples outside of SIP and some gaming servers? On Thu, Nov 8, 2018 at 3:48 AM Richard Gibson <richard.j.gib...@oracle.com> wrote: > This is such a salient point, and always draws me back towards a desire > for accompanying questions. They wouldn't directly address exactly the > issue handled by ANAME (the addresses of one host corresponding to those > of a distinct [probably out-of-bailiwick] name), but might make it > moot—or at least tolerable—by tackling more fundamental progress > blockers. Support for covering apex A, apex AAAA, and service-specific > SRV (especially with target host addresses in the additional section of > the response) in a single transaction could absolve many sins. > > On 11/6/18 13:51, Ray Bellis wrote: > > IMHO, any record that doesn't support a service selector isn't doing > > its job properly. > > > > You _have_ to be able to say "if I want this service at this domain, I > > either prepend this prefix, or lookup this type", otherwise you're > > just forcing _all_ services to connect to the A and AAAA found there. > > > > A and AAAA should be for connecting to the right _host_, once you've > > established from the _service_ which host that is. > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
