At 12:48 am -0500 2004/06/15, Edgar Lovecraft wrote:
>David Brodbeck wrote:
>>
>> > -----Original Message-----
>> > From: Greg A. Woods [mailto:woods@most.weird.com]
>>
>> > However you might consider trying to get this mismatch fixed:
>> > > $ host -A mailhost.humph.com
>> > *** mailhost.humph.com address 217.155.139.146 maps to
>> > hostname dsl-217-155-139-146.zen.co.uk
>> > *** Hostname mailhost.humph.com does not belong to address
>> > 217.155.139.146
>> > *** Not all addresses for hostname mailhost.humph.com have a
>> > matching hostname.
>>
>> You do realize, right, that almost no one has control of their own
>> reverse DNS anymore? Most ISPs will not bother with it unless you have
>> at least a Class C netblock, and Class C's are hard to come by. The
>> company I work for has one, but our ISP has told us that if we were just
>> signing up now, they wouldn't give us one. We only have it because
>> we're grandfathered in.
>
>You do not need to control the in-addr.arpa space to have your ISP
>setup a proper DNS PTR record for your Internet connected host(s). I
>have never once had any ISP tell a client that they would not set a DNS
>PTR record for them upon request, to point to a specifc DNS A record
>that matches the IP address they want a PTR record for.
you have been very lucky then.
>Well, that is, as long as the IP range that the client is on is not
>with a 'non-reversable' IP range (i.e. Dynamic cable/dsl/adsl/dialup).
oh well, the one above, incorrectly identified by Greg's clever
routine as dynamic, is in one of the two (static) zones I use and on
which I have no say DNS wise. Still, if I used the PTR for the
server's HELO I would make a mistake, as the only name that really
identifies that host is the FQDN that belongs to my domain, as I
administer the server, not my ISP.
Giuliano
