DNS issues in SoCal

[mrballcb]

---

@bwren wrote:

Everything working fine for me as well.  Would be nice if we could get some acknolwedgement from Verizon that there actually was an issue and some confidence that they consider a three day outage unacceptable.  Glad this over the weekend or I would have been working out of the local coffee house all week.

---

Three days?  Most of the people here have been unable to reliably log in to their banking or MLS websites for almost 4 weeks now.  It hit me a little under 4 weeks ago but has been clear since then.  The issue is, was, and always will be with large companies that there was no way for the people who could reliably produce the troubleshooting info to be connected to the people who could diagnose and fix it.  And until enough people started making a stink about it, VZ wouldn't do anything to fix it because it's just not in the best interests of their bottom line to fix it unless more than X% of customers are complaining.

[BenM1]

---

@bwren wrote:

Everything working fine for me as well.  Would be nice if we could get some acknolwedgement from Verizon that there actually was an issue and some confidence that they consider a three day outage unacceptable.  Glad this over the weekend or I would have been working out of the local coffee house all week.

---

Same here. Back to normal as of Monday afternoon.

[tns]

Note some of those having issues with logon's to banking sites,etc., starting 4 weeks ago are hitting the some problem introduced by a Microsoft security fix that  also caused verizon logon's to not work for awhile.  I.e., for those problems its necessary to either temporarily backoff the fix, or get the site in question to fix it.  

The DNS issue can be fixed by using one of the other popular DNS services instead of Verizon.  Other issues such as routing not working between certain network are a different question, sometime being Verizon and often one of the connecting networks having problems.

[frnkblk]

---

@tns wrote:

Note some of those having issues with logon's to banking sites,etc., starting 4 weeks ago are hitting the some problem introduced by a Microsoft security fix that  also caused verizon logon's to not work for awhile.  I.e., for those problems its necessary to either temporarily backoff the fix, or get the site in question to fix it.  

The DNS issue can be fixed by using one of the other popular DNS services instead of Verizon.  Other issues such as routing not working between certain network are a different question, sometime being Verizon and often one of the connecting networks having problems.

---

@tns: What are "verizon logons"?  

In regards to the Microsoft security fix, while discussed in this thread, I don't recall it resolving anyone's issues accessing secure sites (i.e. https://).

Not one person has demonstrated that there was an issue with Verizon's DNS servers.  What did happen is that using a different DNS server would result in different DNS records returning (due to geo-DNS or something similar).  But that doesn't mean that Verizon's DNS issues had a problem.

[Scottage]

---

@tns wrote:

The DNS issue can be fixed by using one of the other popular DNS services instead of Verizon.  Other issues such as routing not working between certain network are a different question, sometime being Verizon and often one of the connecting networks having problems.

---

A few people mentioned that switching to alternate DNS helped them immediately, indicating that it might be a DNS server issue. (though it's definitely possible they just tricked their particular problem site into giving a different IP to route to) Others, such as myself, tried multiple DNS servers (default, Google DNS, OpenDNS) and it made absolutely no difference, indicating that it was definitely not a DNS server issue. It's possible

Perhaps there are two separate problems going on here for separate groups of users, with the same apparent end-result, but totally different causes? I know those are always the most annoying IT issues to troubleshoot, since you can't get all the symptoms to point to the same cause properly.

As of right now I'm on the third IP address I managed to pull via leaving the router off for a few hours. The first one I got when it was installed would not let me go to a number of sites. The second was nearly as bad, but with a slightly different list of sites that I could spot (listed a few pages ago) and eventually getting even worse. Now my third IP address seems to work perfectly (at least among the sites I've tried), but I'm afraid to touch anything now in fear of accidentally losing this one magical good IP that I magaged to get by what appears to be pure luck-of-the-draw.

[melboogz]

I have the same issue over here in ny to switch your dns to google dns fixes it 8.8.8.8 

[TheMick1]

Thank you for this forum.  I am also in SoCal and when I try to go to Costco.com, I am redirected to Costco.com.mx (Mexico).  This is the only website I have a problem with.  Costco says its Verizon's problem, but after reading this stream of comments, I feel that it's hopeless to contact Verizon.  I am just letting you know that this problem still exists.  Was there ever a "bottom line" to this problem?

[CaptainSTX]

When you suspect a DNS server problem there is a simple solution.

Just look up the public IP for the site that you want to connect manually on the Internet using numerous tools and sites and then type the IP number into your browser.    Failing that call the company using a telephone and ask them what IP you should use.  Not perfect and perhaps not convient but it is better than not being able to reach some site.

Just like  the old days when people used to use phone books instead of dialing 411 and then being auto connected.