[dns-wg] Matching forward and reverse DNS for DSL pool addresses

On Tue, 2004-11-30 at 17:31 +0000, brian.wilkinson at bt.com wrote:
> Can anyone confirm whether DSL (and dial) providers are required to
> provide matching forward and reverse DNS for the address pools or is
> a wildcard in the reverse zones sufficient?

Afaik there is no political requirement.
But I think your clients will be *VERY* happy when you do provide them
with a matching forward and reverse.

Ever tried ssh'ing into a server with a host which had a mismatching
reverse!=forward?

Also you will block your clients from using protocols like SMTP and some
others that do forward=reverse checking, not even mentioning the various
logging methods around the world. Note that for SMTP it is almost a real
requirement as it aids a lot of people in debugging. Oh and don't forget
that some people actually also use IRC...

If you intend on a 'wildcard' entry for a reverse, better not do any
reverse at all...

Generating a reverse is not that difficult, bind offers that nice
$GENERATE option anyway. Though nicer is too use one of the various
dictionary lists, which will make your clients a bit more happier.
The best for your clients of course is to allow them to change the
reverses, which is seen as quite a value for a lot of customers.

Greets,
 Jeroen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 240 bytes
Desc: This is a digitally signed message part
URL: </ripe/mail/archives/dns-wg/attachments/20041201/152751c6/attachment.sig>