Really? Could you try again?

I don't see an issue in accessing the site.

yep, the DNS doesn't seem to have propagated out to me.

http://laktek.com.s3-website-us-east-1.amazonaws.com/ works though

Wonder whether its a problem with some DNS servers.

http://www.downforeveryoneorjustme.com/laktek.com

seems like it just isn't recodnized on comcast's DNS system

⚓ ~ dig laktek.com @75.75.75.75 +short ⚓ ~

google is working though

⚓ ~ dig laktek.com @8.8.8.8 +short laktek.com.s3-website-us-east-1.amazonaws.com. s3-website-us-east-1.amazonaws.com. 205.251.242.139 ⚓ ~

may want to contact comcast if that still fails after 24 hours of a creation/change

Their DNS is broken. They have a CNAME at the root of their zone, which is forbidden. If you're using the "Unbound" DNS resolver (I am), and it's in DNSSEC validation mode, then it will SERVFAIL when it comes across broken DNS like this (even if the zone isn't using DNSSEC).

I don't know about other DNS resolvers, but IIRC didn't Comcast switch to using resolvers which support DNSSEC for their customers recently?

[edit] - Can you see http://imgur.com/ on Comcast? That (well known) site has the same problem. I tried to alert them to this fact a few weeks ago but never heard back. I'd be surprised if Comcast users can't access that site.

Strangely, laktek.com does not seem to have a SOA record, nor NS records.

How is something like this even possible? Does whoever runs .com these days create direct cname entries without delegation?

Puzzled.