Jim Fenton wrote:
Hector Santos wrote:
What are the problems with this type of logic?
Again, the difficulty, if you receive a message from sales.idsg.net, is
knowing where to query. Is it sales._ssp.idsg.net, or
_ssp.sales.idsg.net? More complex domain names will result in more
possibilities.
I see.
But why not define it so its always two levels, isdg.net? and let the
zone define the rest?
Maybe a solution would be to use the main domain to obtain a record that
"instructs" the client to what is the the "main domain?"
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?
--
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