Probably only a select few will encounter this problem as it would only affect those setting up DomainsAtCost as a Domain registrar and DNS manager, in combination with Google Apps. However, there are many posts stating folk are unable to configure Google Apps with this registrar as Google cannot verify the domain ownership due to it not recognizing the necessary DNS Txt  record. Perhaps the few having problems ‘resolving’ this issue may find it helpful.

Before Google will activate your new Google Apps account it understandably needs to verify domain ownership. There are several ways to do so relating to your web site but if you do not have a website for your domain, you are limited to adding a DNS record with whomever manages DNS for your Domain. In the past Google requested you create a Host [A} record, but a year ago they switched to using Txt records. The Google instructions are simple and straight forward, you just enter a lengthy 68 character text string in the “Text” box and then either leave the “Host” box empty or enter an @ symbol.  (see: )image

However if you are with DomainsAtCost and using their Advanced DNS Management the @ symbol is the catch. Their site instead requires you manually enter the domain name in the Host field. Doing so will very quickly update DNS and allow Google apps to verify your domain ownership. The DomainsAtCost site will accept the @ but it will not be resolvable by internet based DNS servers. i.e. it doesn’t work. You can test if your Txt record has propagated to public DNS servers by entering  in the MX lookup box at

Once domain ownership has been verified by Google you can continue the set up by adding your MX records to your DomainsAtCost DNS configuration. It is interesting though that in the DomainsAtCost Host field for the MX record, which does require the domain name, if you insert the @ character when you save it it will automatically convert to the domain name. This does not happen in the Txt record Host field.

Comments on: "Google Apps and DomainsAtCost Registrar" (3)

  1. Hi,

    My name is Rob Villeneuve and I am the CEO of We have taken note of the @ symbol replacement issue in the Advanced DNS TXT Host field and will provide an update shortly.

    Thank you for pointing this out.


  2. I wonder how hard it would be for DomainsAtCost to be a listed registrar on GoogleApps with instructions for verifying a domain, or am I just dreaming? I’m a big fan of DAC, so thanks for bringing the issue to light so DAC can fix the problem.

    • As per the comment prior to yours, the CEO of DomainsAtCost responded within an hour of my post and said they are going to try resolve the issue so that the Google standard instructions will apply to their service as well. I was very impressed that DomainsAtCost is that “tuned in”. Hopefully it will be resolved soon for others that follow.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Tag Cloud

%d bloggers like this: