Original Message From LAWRENCE GARVIN To BRIAN HILLIS...

Thanks for the response.  As usual, the information passed on
here is not only first class with regards to quality, but it's
also understandable .

LG->In this particular case, your host IP (24.112.65.3) is one of 510 hosts
LG->assigned to the 24.112.64.0 network, which consists of host addresses from
LG->24.112.64.1 through 24.112.65.254 (and the broadcast address will be
LG->24.112.65.255).

 BH> Needless to say, I have been having a few problems, primarily
 BH> failed DNS reverse lookups for the IP number, and I keep
 BH> thinking that the net mask might be the problem.

LG->Most likely the failed reverse lookups are because your ISP hasn't entered
LG->your host IP in the reverse DNS zone file.
LG->It's highly unlikely that it's related to a netmask issue. Generally if the
LG->netmask is configured incorrectly somewhere the misconfiguration is either
LG->ignored or it flat out doesn't pass any IP traffic at all.

Sorry to quote back so much of the original, but one other piece
of information I've come up with (but can't seem to get anyone
at {at}Home to pay attention to) is that if I do a DNS reverse
lookup on anything in the 24.112.65.* range, it fails, but
anything in the 24.112.64.* range (or 24.112.66.*) DOESN'T.

Considering what you've explained above, is it fair to assume
that because of the non-standard way they're doing things
(255.255.254.0 mask), this might be also causing problems with
the way things are functioning with regards to the reverse DNS
zone file?

I'm trying to put together a more technical explanation of the
problem to send to the tech support folks, and the information
you have sent helps a LOT.

Cheers...., Brian        EMail:  bhillis{at}pro-mail.com
                           Web:  http://www.pro-mail.com
                          Fido:  Brian Hillis{at}1:250/1004

 * 1st 2.00 #11111bt *  Pro-Mail - Toronto Canada - (416) 231-6884

--- QScan/PCB v1.19b / 01-0150