cancel
Showing results for 
Search instead for 
Did you mean: 

Content screening again

bombinho1
Member

Dear Sirs and Madam Mods

 

I would have liked to read that the issue is resolved before you close the older thread.

As for me it seems to be working again. Time will tell.

If I would not have tried I would not have known as I was using the openDNS workaround.

 

Thank you,

 

Bombinho

3 REPLIES 3

DaveA
BT Partner
BT Partner

Hi,

 

Yeah it wasn't intended as a block to further comment, but it wasn't until just now that I thought about putting up a specific thread for it.

 

Apologies.

 

Dave

daempii
Member

I am also using an openDNS. Does this mean that I might be able to get this problem as well?

bombinho
Super User

Not likely OpenDNS and BT CS are two different things. OpenDNS boasts to have hat since switching on 100% availability.

The content screening at question was BTs.

There are many stories and no official comment. But to me it looked like someone did a mistake on an firmware update.

As per my log the router was making a DNS request for the CS server with an empty string.

If you have not switched on content screening in your router but changed your DNS servers for the OpenDNS then you will not be affected by this specific problem.

 

OpenDNS has only been discussed as an alternative to no content screening at all.