Can't clear my cache / see my site

Head out to springhillmemorialday.com. You should see a webpage that has an American flag and some other things. This is what I see:

screenshot
Here's the source code for that page:

<!-- pageok -->
<!-- managed by puppet -->
<html>
<pre>pageok</pre>
</html>

After google-ing, I found a couple of articles that talk about Godaddy's system not resolving your IP address correctly, but that's not the issue.

I also found articles that talked about how you need to clear your cache on your browser, your computer and your router. I've done that and I'm still seeing "pageok."

On my phone, when I'm running 4G as opposed to defaulting to my home network, I see the same page. I've got users out in town who are seeing this page. I don't know what to do and I'm hoping that the Experts Exchange brain trust can help me out with this. Never seen it.

What do you think?
brucegustPHP DeveloperAsked:
Who is Participating?
 
Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
It sounds like a dns issue to me.  Looking at the godaddy support site, you can make sure the domain is pointed to the  correct place with the A record https://support.godaddy.com/help/article/680/managing-dns-for-your-domain-names?countrysite=us

From the godaddy site
Adding or Editing A Records

An A (host) record connects your domain name to your IP address. A records let users enter your domain name in a Web browser to access your website. They are the most common type of zone record.

To Add an A Record
In the DNS Zone File, click Add Record.
From the Record type list, select A (Host).
Complete the following fields:
Host Name — Enter the host name the A record links to. Type @ to point the record directly to your domain name, including the www.
Points to IP Address — Enter the IP address your domain name uses for this host record.
TTL — Select how long the server should cache the information.
Click Save, and then click Save Changes. The new A record displays in the A (Host) section.
To Edit an A Record
In the A (Host) section, next to the record you want to change, click Edit Record.
Edit any of the following fields:
Host — Enter the host name the A record links to. Type @ to map the record directly to your domain name, including the www.
Points to — Enter the IP address your domain name uses for this host record.
TTL — Select how long the server should cache the information.
Click Save, and then click Save Changes.
0
 
brucegustPHP DeveloperAuthor Commented:
BTW: When I say that the IP address is alright as far as Godaddy, that's based on the fact that I can go out to my account and physically compare IP addresses as far as what is set up and what comes up when you do a search. Also, the Godaddy Help Desk can see the site rather than the "pageok."

I'm at a complete loss...
0
 
strungCommented:
I see "pageok" on both Firefox and Safari using a Mac.

For me, springhillmemorialday.com resolves to 173.201.246.128, which is a GoDaddy IP.

Since I have never visited your site before, it is not a browser cache issue. You need to get back to GoDaddy support and tell them that others see your site the same way.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
strungCommented:
There is a longwinded explanation and solution here:

http://bx.com.au/blog/2013/02/godaddy-hosting-pageok-message/
0
 
strungCommented:
0
 
Dave BaldwinFixer of ProblemsCommented:
On Godaddy shared hosting, your IP address is not unique unless you have an SSL/TLS certificate.  They use 'name-based' hosting to conserve on IP addresses.

Hmm... I just tried several IP addresses less than yours and they all come up with that 'pageok' message.  I think that Godaddy has a server problem.
0
 
giltjrCommented:
I guess this is resolved, as I went to springhillmemorialday.com and www.springhillmemorialday.com and saw a "real web page"
0
 
strungCommented:
I am still getting the "pageok" page in both browsers, even after refreshing.
0
 
Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
strung, it is  dns propegation.  I did see it work for me with www then a few minutes later for the naked domain after I refreshed.
0
 
Dave BaldwinFixer of ProblemsCommented:
I don't see how it could be a DNS propagation issue when I get that same response on every IP address from 173.201.246.122 to 173.201.246.129.  And I get it thru two different ISPs.
0
 
Dave BaldwinFixer of ProblemsCommented:
Here http://blog.brianjohnsondesign.com/pageok-hosting-error-with-godaddy/ is a post about this problem from a year ago.
0
 
Dave BaldwinFixer of ProblemsCommented:
And by the way, 'puppet' is IT Automation software.  https://puppetlabs.com/
0
 
Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
Dave, I meant for the domain name, not the IP.   It seems like the pageok thing goes back many years and must be something to do with how they set up.    

I found on one site that reports dns where that domain name went to http://184.168.221.40.  There could be something stuck in godaddy servers with that ip as that reversed to godaddy.
0
 
Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
So your blog post you found confirms the possible issue where godaddy may have multiple hosting accounts for that domain where one is "old" and one is new.  The "old" hosting account would need to have the domain name removed.
0
 
strungCommented:
Oddly, it is working for me now, but I am at a different location using a different ISP.

Still resolves to 173.201.246.128, same as before.
0
 
brucegustPHP DeveloperAuthor Commented:
Gentlemen!

This morning I got through to one of the Godaddy hosting techs - one tier above the customer service level. I had assembled a spreadsheet of all your comments in order to better substantiate the fact that something was legitimately south of where it needed to be, as opposed to a mere brower issue.

The guy on the other end was both knowledgeable and confident. He said that "pageok" was actually indicative of a DNS propogation issue - that the site had yet to fully resolve - hence the sporadic and inconsistent display of the site's content.

He had me run a script that cleared the cache of my NIC and that made all the difference. He also was able to confirm according to the system log that the site hadn't fully resolved until 4:00 am this morning.

So, there you have it! Thanks for you all your help!
0
 
Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
Thanks for the follow up.  I know on my own ISP when I change dns via godaddy it happens almost instantly.  But dealing with godaddy  hosting takes time.
0
 
Dave BaldwinFixer of ProblemsCommented:
Now I can see your site instead of the 'pageok'.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.