[SWLUG] Reverse DNS lookup problem

[Ash Whitney]

> The things that need configuring are not on your server.
> Your server is not automatically given control of its reverse dns, that
> is the job of the owners of the IP block, and indeed giving control of a
> single, or small chunk of addresses like that is often far more effort
> than anyone will be bothered to go to.
>
> Only your ISP, the ones that own the IP addresses, can arrange to setup
> the reverse-dns, and there is nothing you can do about it except to bug
> them.
>
> Having a quick investigate, going by the domain names you are using, i
> would guess that (one of) your ip address is 213.171.197.219
>
> $ whois 213.171.197.219 at whois.ripe.net
>
> Reveals that this IP address is indeed in a chunk allocated to Fast
> Hosts.
>
> $  dig 219.197.171.213.in-addr.arpa ptr
> (asking for the reverse dns record for your machine)
> Indicates that Fasthosts have not just failed to setup your one IP
> address, but have failed to get control of the entire block!
> As the chain of query stops at RIPE and has not even been forwarded as
> far as a fasthosts server.
>
> In fact, of that chunk of 32 * 256 IP address blocks assigned to them by
> RIPE, they only have the first TWO sections delegated, plus one higher
> up. so 213.171.192, 213.171.193, and 213.171.216 address may have
> correct reverse-dns, but everything else they control, does not.
>
>
> You need to nag them again to go and check _properly_ this time, failing
> that the only way to fix this is to move to a different hosting service
> with someone more competant.
>
> Oh, and ask them if they need some Consulting on how to run internet
> services ;)
>
> Justin
> caederus.com
>

Hello Justin

Many thanks for taking the time to write such a comprehensive and helpful
reply to my post.

I understand what you're saying about the reverse dns lookups only working
on the 213.171.192 and 213.171.193 sections of the block assigned to them.

It's like banging one's head against a wall trying to get any useful support
from Fasthosts, and frustrating to be getting palmed off with bad advice
from them. The last time I tried to tackle this issue they informed me that
all I needed to do was to switch on a feature in a traffic analysis package
that lets our server perform reverse DNS lookups on incoming traffic.

Unfortunately (and unwisely in retrospect) I've invested a fair amount of
money on this machine, and I'm reluctant to walk away from it at this stage.
Armed with the information you've kindly provided here I'll be on the phone
to them first thing tomorrow. I'll mention that you're looking for some
consultancy work !!

Thank you again

Ash