<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hello, (hopefully on-topic for this list!)<br><br>I am looking for some tips as to how to deal with DNS and rDNS in a residential service provider scenario. This document, http://tools.ietf.org/html/draft-howard-isp-ip6rdns-02, doesn't seem to have been updated in ages and I haven't found any more recent pertinent information.<br><br>Basically, this doc offers the following options to provide forward and reverse DNS; our customers are residential and will not be asking for, or in a position to, operate reverse delegations themselves.<br><br>1) not answer at all (NXDOMAIN). This breaks applications that check forward>reverse <br><br>2) wildcard reverse DNS. This also breaks forward>reverse since as far as I know you can't have a wildcard forward lookup?<br><br>3) Dynamic DNS updates. At first this sounds interesting, except that from what I can tell most current OSs don't by default register in DNS, and if they do, don't use the domain obtained by DHCP unless that is enabled as well. And, IP-based DNS updates are inherently insecure.<br><br>4) delegate DNS to the customer gateway (never heard of a platform that actually supports this??)<br><br>5) "on the fly" record creation. I find no doc for this other than a vague PowerDNS reference, does BIND support something like this?<br><br>Any tips appreciated, RTFM links, whever.<br><br>Thanks,<br><br>Ron<br> </div></body>
</html>