Jim Fenton wrote:
Hector Santos wrote:
But why not define it so its always two levels, isdg.net? and let the
zone define the rest?
But it's not always two levels: I gave one example for that in
.k12.ca.us, but there's also .co.uk, .edu.au, and too many other
examples to enumerate.
Ok. How is the zone file defined?
whatever.edu.au
If this is a problem and it seems no one here knows hows to address it,
it sounds to me the WHOLE domain is the only recourse.
Also, if DNS can't handle the representation of complex unions, then
why not just go to a TXT result syntax that provides a masking concept
and let the client perform this task all in single line? Ala SPF-like
directives?
I'm not sure what you mean here. Discovery of the TXT record and
retrieval from the right place would still be a problem.
Well, then if this is a ISSUE then there is only one SOLUTION - use the
whole domain as provided by the email address.
And then within this TXT record, it can provide a wildcard, MASKING
syntax, if required, to represent subdomains.
It just sounds to me that if this 2 vs 3 zone, and cuts is getting in
the way, then we need to go with POSSIBLE today and then see if it can
be optimized later.
--
Sincerely
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html