domain mapping / We were unable to verify that … is pointing to Wo

  • Author
  • #160991


    I’m trying to get domain mapping setup for my blog. I setup the CNAME over 24 hours ago and continue to get the following message:

    Possible problem with

    We were unable to verify that is pointing to If you own this domain, follow the directions below to get it ready for your blog. If you don’t own it, try a different name to see if something else is available. If the domain is available, you may be able to register it with another registrar and then map it to your blog.

    Every DNS server I’ve tried has resolved properly for the last 18 hours at least. Any idea how I can proceed?


    I think this may be something you will have to take up with staff when they open in the morning.

    Contact support Mon-Fri 9am-5pm Pacific time at: , or using the “support” button in the upper right of your dashboard.



    I sent mail and got email back at 10am this morning asking if I had credits.. Replied immediately saying I never got that far. Haven’t heard anything back yet. Is there anything I can do?



    If you want to map to your blog, you need to change the namservers at your registrar to point to our nameservers. You only need a CNAME entry if you wish to map a subdomain. It is all explained in the FAQ entry here:



    barry: I’m trying to get (the subdomain) to map. It is setup as a CNAME and has been for over 48 hours now. I continue to get the error message about being unable to verify despite every dns server I can find being able to resolve it.




    sppavlov, when I click I end up at the homepage.



    Provided the change of the namservers at your registrar to point to nameservers has been correctly done, it can take up to 72 hours for the repointing of a domain to be completed.



    reference: You will find this mentioned here



    Still no response from support…
    Still unable to give my money :(

    I’d really like to get this working. Anyone?

    fwiw, the TTL on my DNS entry is 2 hours — 72 hours is pretty excessive for DNS changes to go through (especially given that every dns server i’ve tried resolves it properly, although we’re coming up on that soon…). The only thing I could think of is that has some caching DNS server that is ignoring TTLs that will hopefully expire sometime soon. I would be nice to hear from the support folks saying something like this at least.



    Your DNS change hasn’t propagated yet.

    $ dig ns @L.GTLD-SERVERS.NET

    ;; AUTHORITY SECTION: 172800 IN NS 172800 IN NS

    ;; ADDITIONAL SECTION: 172800 IN A 172800 IN A



    thanks for the response. Hopefully things will go through soon. Wanted to make sure my responses hadn’t gotten forgotten or lost.


    When I transferred my domain it took nearly 4 full days (96 hours) before it was stable. Sometimes I could get to the site, and sometimes I was directed back to the “under construction page at network solutions.



    I have to wait usually long periods of time for all my domains that are not .com for some reason. It should be coming through soon if others are able to see it (provagating a little anyways)


The topic ‘domain mapping / We were unable to verify that … is pointing to Wo’ is closed to new replies.