Design Flaw in All LMAP Proposals
- Sub-domains of LMAP-protected domains vulnerable
- aol.com vs ipt.aol.com vs AC9F3838.ipt.aol.com - Wildcards overridden with defined sub-domains
- Comformance with RFC 1034 section 4.3.2 forces this behaviour
- Two clear choices to defeat this, there may be others:
- Require LMAP records on ALL domains - not practical until LMAP is widely used
- Change DNS software to support other types of synthesised records based on query type and input
Example: If querying record type "x" in a domain,
with a "y" part (ie: _smtp-client)
and no record exists (NXDOMAIN),
synthesize a response of "z" if you are authoritative for the domain.