Family Shield - no servers could be reached

Follow

chrisdotcollins

April 05, 2020 21:07

Hi,

I'm trying to use Family Shield on individual devices on my home network - a pi and linux laptop that my kids can use without fear of accidentally stumbling on anything during this school free lockdown. I use standard opendns on my Netgear router, which works fine and passes the basic welcome.opendns.com test, however when I change the DNS servers on any device to point to the Family Shield servers (208.67.222.123 and 220.123) I just get "connection timed out; no servers could be reached" returned from nslookup etc.

Am I missing something here, are the FS DNS servers not generally accessible? I have an OpenDNS account, and my IP should be updating, if that is required?

Any advice would be appreciated,

Chris

0

• 

  rotblitz April 06, 2020 10:55

  It looks like you have enabled LPC. This is a feature of Netgear LPC. You cannot specify alternative DNS server addresses at the end user devices. These devices must point at the router‘s IP address.

  And with LPC you cannot use OpenDNS Home and its dashboard at the same time. These two services are incompatible.

  0

  Comment actions Permalink
• 

  chrisdotcollins April 06, 2020 14:29

  Thanks - I did indeed have LPC enabled. And there was me thinking it had just set the DNS servers for my home network. Disabled LPC and now I can use OpenDNS for standard lookups and Family shield for the kids devices.

  0

  Comment actions Permalink

Please sign in to leave a comment.