Custom Domain DNS setup changed, probably

[Kaan Soral]

I have a domain/app that's 3-4 years old, I didn't make any modifications recently

This was one of the domains that experienced the whois privacy violation, I also received a $10 courtesy credit recently

I've noticed today that my naked domain isn't accessible, I remember setting up the DNS/Domain to handle the naked domain, yet when I look at the ruleset now, the solution I applied isn't there (I even forgot what it was, it was a long time ago)

Anyone else experiencing a similar issue?

Basically, my naked domain was working, now it isn't

[Adam]

This domain is hosted on Google's Cloud DNS?

[Kaan Soral]

No, I don't remember Cloud DNS existing back in my day, it's ENOM registered by Google Apps, the DNS is ENOM too, if I'm not mistaken

[Paul Canning]

I was under the impression naked domain don't work now.

I recently setup app engine and added a custom domain. The naked domain doesn't work alone, and I had to add the "www" sub domain.