It happened so far across 3 campaigns and 5 different sites located in two different data centers.
I checked, and there was no (significant, if any) downtime in the recent week or so.
Is it happening to anybody else?
A bit more interesting info, after bashing at this problem since before the sun came up!
If I ping my site with www.example then I get a return showing it decoded to an IP address starting with 65.
If I ping my site with example etc then I get a return showing it decoded to an IP starting 205! (i.e. if I leave out the "www")
The same thing happens with tracert!
Using EasyWhois, the first (65) IP address returns the registrant as myself and my site
Using EasyWhois, the second (205) IP returns a company in USA as the registrant.
Now, I have read elsewhere that Google "doesn't care about the www" in the landing site info on your ad (useful for folks with long names who can't otherwise fit in the 35-letter limit) so I wonder if Google either "assumes", or "strips" the www, and hence gets the wrong landing site in its automatic checking?
I have a head-ache!
Stu
[edited by: eWhisper at 12:15 pm (utc) on Dec. 21, 2008]
It's called modifying the CNAME, and you need to get that fixed so that they point to the same place.
As for your issue, bcc1234 - I haven't had the problem this past week except for one client whose site conveniently went down shortly after we submitted the new ads.