On 05/22/2014 12:33 PM, John R Levine wrote:
It's long been clear that any real solution to "the same" will involve
some way for application servers to configure themselves automatically
to match what the DNS expects them to handle.
No, that's broken. DNS should never dictate how an application
server behaves. If anything, the application should be able to
configure DNS.
Hmmn. Tell us about http virtual domains.
What is there to tell? The HTTP server has to be explicitly
configured to recognize the virtual domain anyway, otherwise it has no
idea where to find the content that goes with that domain. That's how it
is with most applications - the application server needs to know more
than could reasonably be included in the DNS anyway. Add to that that
it's pretty common for servers to handle multiple DNS domains - so how
is the server to know which DNS domains it should trust? Trusting every
DNS domain that references the server makes no sense because anybody can
reference your server in their DNS domain. So at a minimum the
application server needs to know which DNS domains to trust. Finally,
there's the problem that even for "legitimate" DNS references to your
server, the people who run the DNS servers are often out of touch with
reality.
Executive summary: DNS should never dictate how an application server
behaves. If anything, the application should be able to configure DNS.
Keith
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp