In message <[email protected]> Michael Thomas writes: > On 07/30/2012 04:54 PM, james woodyatt wrote: > > In the unicast DNS case, the content server probably does not know-- > > and arguably should not know-- the name of every host in the zone, so > > that's why it's wise to expect it will be synthesizing host names. > > Whether the default zone for ULA reverse mapping names over unicast > > DNS is "local." or "homenet." or something else is only tangentially > > relevant here. It's the same problem no matter what TLD we allocate > > for this purpose. > > > > Maybe I missed it, but why is lack of reverse map a problem, minus the > security desire to show some weak control of the allocated prefix? > > Mike
Mike, rDNS answers questions like who is that trying to connect to port X. If its just misconfiguration or a benign but unexpected behaviour, then knowing the host name helps. For a local mailserver having an accurate reverse DNS entry is a real good idea. If not some other mail servers will reject your mail, most often large consumer oriented ISP mail servers. Some of the same ISPs that won't do rDNS delegation reject mail from hosts with no rDNS entries or wrong entries. Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
