Only Verizon FIOS won't connect to a Startingly.com website
The user has a website hosted at Strikingly.com Yesterday, they noticed that they couldn't reach the site when their ISP was Verizon. I have a different ISP, and can connect. I tried connecting from two locations in another state, and they were able to connect.
When I had the user disconnect from Verizon Wifi, and connect their phone with AT&T, they were able to connect to the site.
I checked the DNS records at strikingly.com I moved the DNS from DreamHost to Oracle an hour ago.
Verizon support says that there is no known problem with Verizon. Strikingly says that the hosting settings are fine at Strinkingly. As mentioned, I changed the DNS
What could be causing this problem that seems to be at a regional Verizon only?
How can it be resolved?
Thank you.
ASKER
The original DNS wasn't changed. I will see if the relocated DNS helps the issue.
Are there known issues of why Verizon, and just Verizon, would suddenly have trouble making connections?
Some ISPs (Verizon and Cox, in my experience) are notoriously slow in updating. They have a captive audience, plus they use their DNS system to inject ads so they have little incentive to do anything quickly.
Are you supposed to have two a records with two different IPs?
https://mxtoolbox.com/SuperTool.aspx?action=mx%3aStrikingly.com&run=toolpage
ASKER
Scott - Strikingly chat checked their settings.
Is having two IP addresses some form of redundancy?
I'll chat with them again.
It is probably a fail over.
But do a tracert https://tools.keycdn.com/traceroute and see what you get.
Either does not look good from my local pc
It may be a DNS issue on the local computer. Run nslookup <web address> on computers that can reach the site as well as those that cannot. You should get the same IP address in both cases.
You can also try manually setting the DNS on the local computer to a general one, such as 1.1.1.1 in both cases and see if that makes a difference.
ASKER
I cleared the DNS cache, and even set the DNS to 8.8.8.8 Which does not make a difference
The site does not connect from other computers in the area.
ASKER
Yesterday, I switched DNS from DreamHost to Oracle. Today, visitors to the site connecting through FIOS and Verizon Wireless are starting to get access again.
Did the DNS switch to Oracle 'provoke' Verizon to update something?
Like I said initially, DNS changes take time to propagate among servers. Some people may have seen the change within hours, for others it may take days.
One can change the time-to-live for a DNS record to a short value - say 3 hours - prior to a DNS move, which will cause other DNS servers to update that record more frequently. This avoids the delay you're experiencing. As more DNS servers update their records for your domain, more people will get the right IP address.
ASKER
Why would Verizon have a DNS problem. The user didn't make any DNS changes.
There is no telling why there is an issue with one and not the other. Something could have changed or gone out temporarily. It's not the user, it is the route traffic takes to get to the user.
It takes time for DNS changes to propagate - I've seen it take 3 days for DNS to catch up among some providers.
This can be shortened by shortening the TTL for the record some time before making the change. The causes other DNS servers to flush the old record faster.