06-20-2012 07:39 PM - edited 06-20-2012 07:40 PM
Is this going to be the only solution for this problem (changing the DNS settings from auto detect and entering manual addresses, a method I would prefer not to use) or is a fix going to be released in order to solve this problem?
06-20-2012 08:35 PM
Just ran a quick scan on my desktop and it worked perfectly! I'm gonna do a full scan just to check after it and see if it continues to work. I haven't done anything with my laptop but I'm gonna try that too.
06-20-2012 08:52 PM
Ok, I got the full scan running now and apparently it got past the SecurityRisk.FlushDNS test in about 30 seconds on my desktop! I'm switching my desktop to the Norton DNS servers you and Vineeth have provided here right now. I already switched to the Norton DNS servers earlier on my laptop and that helped a lot. I'm also gonna run more scans on the laptop to see if that continues to work properly and I will let you know what happens.
06-21-2012 04:36 AM
I've just done a Live Update and Quick Scan on all 7 Win 7/32 bit PCs. Quick Scan back to 3 minutes per PC.
The Quick Scan results panel showed 500 or so fewer items scanned than when "SecurityRisk.FlushDNS" had caused Quick Scan to be slow.
What I don't get is the recommendation to change to ConnectSafe DNS because I've been using ConnectSafe as Primary and Secondary DNS in all PCs and all OS, including Linux, since April - if ConnectSafe was a "fix" then I shouldn't have experienced yesterday's Win 7 / N360 v126.96.36.199 glitch at all, surely?
06-21-2012 06:04 AM
How are the scans for everyone now? Are they still taking forever?
Norton DNS Type A adresses are entered into my router, and the scan is still taking forever.
When I do the check on the Norton DNS site, it says I am running Norton DNS.
This is in Windows 7 and running Norton Internet Security 2012.
06-21-2012 06:55 AM - edited 06-21-2012 07:13 AM
Hi. I am experiencing the same problems as listed above. But I need some clarification please because I am a little confused. My quick scan is still stuck on SecurityRisk.FlushDNS. So if I was to change my DNS to the one Norton has provided Do I have to attempt to stop the scan first?
Also, for the DNS. I am using a home network setup. I am currently using a laptop connected to the internet via my home desktop's modem. If I were to change my DNS settings would this change anything else in my home setup? And is it possible to set my DNS back to how it was before?
Some help would be appreciated.
Update: My scan finished and all is well. after some google searches I answered my questions. Ill be getting some sleep now then ill run a manual live update tomorrow for any patches they might be released :)
06-21-2012 07:41 AM
Now everything works like magic and I state that I have not made any changes to DNS or anything else.
The only thing I noticed is that Windows Update Agent has been silent updated on PC startup, I do not know though this may have influenced, for as far as I know, should not get into anything ...
I had same problems during quick scan, 10 min. just for SecurityRisk.FlushDNS until last night.
Today I turned On the PC, I run 2 times a quick scan and a full scan, the problem does not longer occurs. The scan times are returned normal. Approx 2,30 min.for a quick scan and 32 min. for a full scan.
I ask to Symantec if they have released and updated silent, I do not see any update on history, or some information about this problem.
Specs: NIS12 188.8.131.52, Win7 sp1, Intel Core 2 Quad @ 2,6 Ghz, 500 GB HDD, IE9
06-21-2012 08:05 AM
Scans appear to be running for me now but this time the SecurityRisk.FlushDNS test didn't even appear. Will this patch be repaired so that everything appears while using the Norton DNS and run a scan?