On 6/4/2004 12:13 AM, Andrew Newton wrote:
So he had an interesting idea. He suggested that instead of looking
for the MARID record in the domain of the sender, look for it at the MX
target of the sender. This solves his problem since his DNS zone is
the MX target. This also leads to a solution to the wildcard issue.
If MARID uses a name they can delegate the name itself. This is the same
model as having A, MX and other RRs at the same level as your SOA.
@example.com.
_marid NS ns1.example.net.
@_marid.example.com. SOA (...)
NS ns1.example.net.
MAR (...)
The domain owners have to create NS RRs delegating that portion of the
zone hierarchy away. If they can't get that right, they're beyond help.
Building in kludgery is the wrong way to go.
This won't work if the RR is bound to the parent name, of course.
--
Eric A. Hall http://www.ehsco.com/
Internet Core Protocols http://www.oreilly.com/catalog/coreprot/