Brian,
Can anyone confirm whether DSL (and dial) providers are required to provide m atching forward and reverse DNS for the address pools or is a wildcard in the reverse zones sufficient?
from a DNS perspective there's no difference between dialup providers, large companies using static allocations or Joe User in his garage. However, apart from the fact that a 'requirement' to provide reverse mapping may be difficult to enforce, it is best practice that if it is present, it must be consistent with the forward entries. Otherwise a lot may break for people using that address space due to certain popular cross checks. See draft-ietf-dnsop-inaddr-required-05.txt 9may be expired) for a discussion. "Wildcards" nowadays will produce sort of allergic reaction all over the place. While you can of course apply them to PTR RRs in IN-ADDR.ARPA zones, they're likely to break consistency. In addition, in a namespace as structured as IN-ADDR.ARPA what's the advantage of '*' over some lines of perl script (or BIND's $GENERATE) and "doing it right"? -Peter