Pageok given by puppet instead of subdomain files hosted on godaddy

Question 1

I'm managing the e-commerce website for a retail store in Los Angeles, and use a subdomain hosted on GoDaddy as a fileserver to augment our Online Webstore CMS, which won't take large files (and honestly is an outdated and cumbersome system for managing files, but it's attached to our point of sale system, so the word on high is to make it work).

The trouble is that a week or two ago, files.abc.com stopped serving files publicly. Instead, abc.com is full of broken image links. Attempts to load any html files that exist in the root or to follow image urls makes the browser load a white page which says pageok with the following source code:

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

FileZilla has no problem accessing these files with my ftp credentials, but browsers can't get it.

While researching an answer, I saw someone who might have had the same problem was referred to Server Fault, but I found no questions under "pageok". I searched for general subdomain issues with goDaddy and found this article,

so I tried to compare our set-ups to figure out if it's a problem with the DNS, but I'm in over my head, perhaps.

GoDaddy says nameservers are:

@ (Informational) ns51.domaincontrol.com (Informational) 
@ (Informational) ns52.domaincontrol.com (Informational)

In this context, what does "informational" indicate? Other DNS info:

For my a records, "*" and "@" map to 209.117.231.3
"blog", "files", and "livechat" map to 50.63.45.1, where you can see the pageok error.

I have the following cname records:

e
email
ftp
imap
mail
mobilemail
pda
pop
smtp
webmail
www

Question 2

It may sound too late for this one. But just in case someone else experiences it, here's how I get it through:

Open your account on GoDaddy and check the server IP
Do a traceroute on your domain. you can use http://network-tools.com or something similar other than your own route.
If the ip's do not match, update your DNS entry for that domain and use the server IP specified on your GD account.
Let your DNS propagate, which may take some time, and check the route again.

If it fails, continue looking for a solution.

Best of luck.