My domain name (purchased through Google Apps) is still not available, over two days after purchasing. It's not just a DNS propagation issue, the message in the Blogger Settings | Publishing tab readsNow, we've seen these reports before; generally 1 or 2 / week is normal. Not 2 or 3 / day.The DNS record for your domain is not set up correctly yet. If you have just purchased this domain the setup process may take up to a day.
And when we Dig the domain, we see evidence of a new problem.
; <<>> DiG 9.3.2 <<>> @localhost mydomain.com A
; (2 servers found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 523
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;mydomain.com. IN A
;; AUTHORITY SECTION:
com. 900 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1255644227 1800 900 604800 86400
;; Query time: 9 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Oct 16 00:03:59 2009
;; MSG SIZE rcvd: 102
This is not a domain that's improperly setup, this is a domain that was not setup, at all.
If your domain is one involved in this problem, can you please provide details, either here (below), or in your Blogger Help Forum thread. The more precise and complete your details, the more easily Blogger can help you.
- What is the domain URL?
- When (time, date, time zone) did you purchase the domain?
- Did you use "Buy A Domain", or Google Apps?
- Did you get a purchase receipt?
- Did you get a confirming email from Google Apps?
- Was your credit account charged?
- Which registrar did you use (eNom / GoDaddy, and did you choose?)?
(Update 10/16 13:00): We are seeing a sign that this problem is being resolved.
I see that Google finally got things working for me. My domain www.jworktv.com is now working. I just rec'd a email out of nowhere that said thanks for your purchase of the domain, and so I went and checked it, and sure enough-it is showing up online.
(Update 2009/10/15 16:00): Blogger Support is now aware of the problem.
Thanks for the reports on this; we'll investigate what is going on from the Apps side and report back here with an update.