rDNS pointer records and web proxies?
I've just received an interesting email from a customer who hosts a client's website with us and is looking to move her website to us. She emailed me with an interesting question - something I have not come up against before. She seems to be implying that some web proxies may block traffic from hosts who do not have a rDNS pointer record for their IP. That is the first I have heard of such a thing. I am aware of this practice for email servers but not for web proxies. Does anyone have any information or experience of such a practice?Thanks
extract of email from customer sent to her existing web host:
I am experiencing problems accessing my website (www.crankdesign.com.au)
> which is hosted by XXXXX. It seems the website cannot be viewed
> from inside organisations that have their own server.
>
> I have had this looked into from the technical dept at my employment, and
> it seems that the ip address which hosts the web server for my domain does
> not have a reverse-dns record. I know to the normal web browser this does
> not matter, but from the proxies point of view it requires a successful
> reverse look-up before allowing the retrieval of
> content from my site.
>
> Are you able to ensure that XXXXX's address range delegations are
> complete. From what I understand, standard practice is to perform a
> reverse look-up of the incoming connection before allowing email etc from
> anywhere.
> which is hosted by XXXXX. It seems the website cannot be viewed
> from inside organisations that have their own server.
>
> I have had this looked into from the technical dept at my employment, and
> it seems that the ip address which hosts the web server for my domain does
> not have a reverse-dns record. I know to the normal web browser this does
> not matter, but from the proxies point of view it requires a successful
> reverse look-up before allowing the retrieval of
> content from my site.
>
> Are you able to ensure that XXXXX's address range delegations are
> complete. From what I understand, standard practice is to perform a
> reverse look-up of the incoming connection before allowing email etc from
> anywhere.