Site can't be reached

[vv0001]

Hello, I seem to be having a problem when my site is accessed a "site can;t be reached" message flashes just briefly before the site is loaded. Same thing happens with mobile or desktop. Is there a fix for this? 

[MrVapor]

Hey there @vv0001 

That almost sounds like a redirect in the .htaccess or something. Have you made any code customizations anywhere in your files?

It would also help if we knew the URL for your site.

[vv0001]

Thank you Joe! I have two sites, authenticvintageposters.com and authenticurbanart.com

I have not made any custom changes, everything has been through the web builder. It seems to happen only occasionally (on both sites), and like I said, only for a brief second, and once the site has been reached, it doesn't happen again for a while (maybe an hour or so). 

Thank you for your help! 

[MrVapor]

@vv0001 

That looks like a DNS relay issue. It's brief to the point that, as a visitor to your website, I wouldn't really care about it. I'm not sure what actually causes that. Maybe someone on here can give a better answer, but I'm not sure.

[vv0001]

Thanks, yeah it resolves quickly but still a bit of an issue I think. Thanks for your input!

[johnstonf]

I am having same issue.  I spoke to support, and was told they couldn't see the problem.  I suspect it's how it's being redirected on GoDaddy end.

My example is http://fredstips.com

[spiringwriter]

Is this ??

[johnstonf]

Sooooo, update... the VERY NEXT DAY, everything started working fine... on ALL my GoDaddy sites that redirect!!!... so i'm POSITIVE someone in I.T. at GoDaddy reset or changed something.  I did do a video of the problem, so you can see it if you have this problem too... see it at https://youtu.be/WL6zGKsgQIU

I changed NOTHING on my end, and it was doing it from several sites and several platforms (Windows, OSX, Linux).  Anyways, i'm happy it's now working, but wish that GoDaddy wouldn't have told me there wasn't an issue, and be more honest when they do fix something.

Fred

[MrVapor]

It's possible it was some sort of server latency issue that they managed to pin down and correct.

[johnstonf]

Exactly