Norton DNS failing to resolve 12-31-17 approx. 7:35 am AZ time. ISP's DNS works fine.
Norton DNS seems to be working again. 12-31-17 approx. 11:10 am AZ time.
Way too many Norton DNS issues lately. I changed to my ISP DNS servers, at this point I have zero interest in changing back to Norton's
I'm sorry you are having so many Norton DNS issues. I have not had any, lucky I guess. Eventhough, I have my Core setup to Norton DNS, dnsleaktest.com actually says that I'm using Neustar DNS servers and that could be the reason I didn't lost connection. I never did a test before now, so I don't know if that is how it always has been for me and the reason I didn't have an outage last week. I also changed to Neustar Advantage and it showed Level 3. Parental controls worked with both of the above settings eventhough i don't use them I just did it to test. I think parental controls also worked with Google DNS.
I changed to Google DNS several days ago. I am still having intermittent Norton Core router problems.
So, I am going back to my old router. Perhaps they can let us know when they get these issues fixed reliably over a period of a month or so.
Bye for Now. I'd live to keep on keeping on, but there are just too many issues for now.
I, too, have Neustar showing on dnsleaktest.com but I have random, intermittent outages (as, apparently, do many others).
This may be due to the interface between the Core and Neustar as I used Norton Connect Safe on other routers and PCs for years with no issues (assuming Connect Safe was/is also provided by Neustar, never checked).
The DNS outages came and go, so some of this may be timing...
In the dog house again.
Such a disappointment. Updated Core last week and put it back in service after a few months of watching firmware and function updates and forum posts. It was working well until today. Couldn't connect to web sites on the internet. Service was up and down. All my "customers" were not happy that I had switched from the old router. Swapped Core out and old router in and everything is fine again. Core is relegated back to paper weight status until the Core infrastructure is ready for prime time. If I put it back in service I will be sure to change the DNS server to the one my ISP provides. It's been rock solid for years.
Too bad, because Core in fast and gives me better wireless coverage than my old router. But if you can't connect to web sites, what good is speed and coverage.
Move over Snoopy.
I have sent you private messages. Could you please check your inbox when you get chance? Thank you.
In response to the private messages, I'm sure we probably all received the same one:
"Can you please send your logs after reproducing the issue? To create and send logs:
1. Launch the Norton Core app.
2. Perform the action that gets the issue to occur. Once the problem happens, shake your mobile device.
3. In the alert that appears to report the issue, tap Email Logs. Please include the link of the forum thread in the log description. Tap Send.
4. Reply to this message with your Norton Core Serial Number. Screenshots would help too.
There's no way I can think of to "perform the action" that gets the issue to occur as the problem seems to lie with Norton's DNS server. I can't exactly force the server to go down on command.
There has not ever been an alert to report the issue. Many of us spent spent hours upon hours troubleshooting only to discover later that the problem was with the DNS server and there is nothing we could do about at the consumer level except change servers once we could open the Core app settings on our phones. That is a crazy design limitation by the way.
I no longer have my DNS server pointed to Norton and have so far been problem free since changing to my ISP server, but if Norton ever figures out the issue with their own server it would be nice if an update was posted somewhere so I can change back to Norton's servers without worrying whether it works or not.
I don't think the issue is the DNS servers themselves - they are Neustar servers and Neustar provides services for many other customers, if Neustar was having problems seems as if we would see info on it all over the web.
I suspect, but don't know, that the issue is the Norton Core/Core infrastructure interface to the Neustar DNS servers.
Regardless, from our perspective, it's a Norton Secure DNS issue...and it's up to Norton to fix it and provide the services we're paying for.
Folks. I had said this once before most likely in another related post somewhere. Norton moved/migrated a large portion of its infrastructure onto the Microsoft Azure Cloud. The interfaces with those services is where I personally believe the heart of the issues with Core lie. On a side note, Intel has an MAJOR issue with most modern CPU's which Microsoft will be patching on their Azure services on January 10th. Going to be watching all things Core on that date to see if the theory validates itself or not. Just a shot in the dark when we don't really have an answer.
All: Core firmware is now version 226. Did the update resolve your issues?
This may be resolved, not because of version 226, but because I think the change from Neustar to level 3/NTT has fixed things. I have not had any failure to resolve problems with "Norton Secure DNS" since I noticed the Level3/NTT switch.
However, I think Norton needs to verify that we are still getting the benefits of Norton Secure DNS from Level3/NTT before we close the issue.
garlen I have presented that question to the Core Admin. I hope to have an answer for that ASAP.
If you are experiencing an issue that needs urgent assistance please visit our customer support area:
There are currently 4 users online.