Quote:
Originally Posted by The Jackal
Which going back to what I've been saying before - your DNS is barfed I would seriously like to know how you are blocking phorm.
Can I add a final note ?
I don't know how you're blocking those IP ranges but it's not going to help. If I were to design the phorm infrastructure I would have to build my application servers and message queuing system within Virgin's infrastructure.
Pushing each request out especially if they are managed by some small outfit like fasthosts is going to overload their network and imply latency to the end user. Hmmm come to think about Virgin doesn't give a toss about the end user experience so they might adopt this model anyway 
But ideally message pooling within Virgin's network is going to be the best way to implement phorm and if that's the case there's going to be no escaping phorm  |
I'm simply blocking phorm.com via my firewall -- Comodo. Yes, DNS seems to be the culprit, but the question is why does it fail
only when I have phorm.com blocked? It's unlikely to be the firewall itself as I've tried blocking other domains like bbc.co.uk or google.com and things function fine except when trying to reach the blocked domain -- as it should be. But switch google.com to phorm.com and DNS gets borked.
Also, please forget about the IP ranges. Since this morning the only thing I have blocked is the domain name phorm.com -- that's where I'm seeing the problem.
As for helping to keep phorm at bay or not, I don't know -- but it just seems like a prudent thing to do -- certainly not something that should have a negative impact unless trying to visit phorm.com.
