D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: summerstormpictures on January 22, 2009, 01:41:34 PM
-
I have noticed upon using the updated firmware 1.22 with SecureSpot 2.0, that upon registering and turning on my 30-day SecureSpot 2.0 ''trial period'' that OpenDNS is not reachable anymore.
Is this related to SecureSpot 2.0's handling of security?
Do I need to remove/change the OpenDNS DNS servers I currently have (Primary DNS Server: 208.67.222.222 and Secondary DNS Server: 208.67.220.220) -- and if so -- do I leave them blank or are there alternatives I should use?
-
I guess Securespot uses it's own DNS server to filter any 'bad seeds' almost at the source.
-
Thats a good question and I need to check that when I get home. I have securespot with ver 1.21 which most know has dns relay issues. I need to see if the 1.21 securespot FW actually turned off the dns relay on its own or not. I would think that with that F/W you should not be able to adjust the DNS parms. Well thats a good enough reason for me to get out of work early and head home to check... ;D
-
With Securespot it would not surprise me if choosing your own DNS is just not an option (perhaps you can fill it in, but it will not be used)
-
I dont appear to have any problems with opendns and securespot other than there are times opendns is not reachable for some odd reason and then it is. I changed over to some other public dns servers and they appear to be better at attaching to for queries then opendns is.
-
I dont appear to have any problems with opendns and securespot other than there are times opendns is not reachable for some odd reason and then it is. I changed over to some other public dns servers and they appear to be better at attaching to for queries then opendns is.
The problem I have is that when I configure my DIR-655 router with Open DNS servers securespot never lets me access opendns.com
It does not matter if I add opennds.com to the always alow list.
Is there a way around this?