CNAME Creation on domain

[jacob.w...@avn.co.uk]

Using transaction based adding via gcloud SDK, I get the following error

The resource record set 'entity.change.additions[1]' is invalid because the DNS name 'nakeddomain.com.' may have either one CNAME resource record set or resource record sets of other types, but not both. (code: 400)

I have TXT, SOA and MX on the naked domain - trying to point naked domain to a loadbalancing record

[Terrance]

Hi Jacob,

Unfortunately you can not create a CNAME record if you already have a TXT, SOA, or MX record. You can have a CNAME or other record but not both. You can find out more about in one of the DNS rfc docs( RFC 2181 Section 10.1 ). Additionally Google Cloud DNS does not support creating creating CNAMEs at the root of a domain.

If you have anymore questions or do not understand feel free to reply back and I will try to help you more.

Best,

Terrance

[BITTU BITTU]

So how to solve this problem when it shows like the attached file

 want to connect my domain[wdlaoo.com, that was bought from godaddy.com]  with my google cloud instance[where my website is existed]

For this I am trying to follow the procedure

First enabled Cloud DNS API
Secondly completed as per  1.png screenshot
but for CNAME RECORD  IT shows according to CNAME.png, CNAME ERROR.png



ERROR SAYS
"Managed zone may have either one CNAME resource record set or resource record sets of other types, but not both."

Tracking Number: d2428049978772817
 
Send feedback


and also if I SEARCH www.wdlaoo.com  shows according to server ip not found.png screenshot

What does it mean and How can I solve these?

Note:

My FIRST STATIC IP during free tier was  [35.203.16.189].But my present static IP IS
[35.215.36.131]   which IP and where  I have to insert these IP , IT'S not clear to me


If any other information is needed for you  please let me know

Your support will be highly appreciated

Thanks

[BITTU BITTU]

 THIS PROBLEM HAS BEEN SOLVED BUT NEW PROBLEM HAS ALSO CAME.

On Thursday, May 21, 2015 at 5:18:58 PM UTC+6, jacob.w...@avn.co.uk wrote:

[Raynel Alfonso Santana]

Thanks for opening this discussion, however, it seems like you are reporting issues with Cloud DNS that require further troubleshooting. Google group is a discussion forum, where you would likely find information like service status updates and release notes, and ranging from book recommendations to creative shortcuts[1]. Considering this, it might not be the right platform to report this type of scenario.

In case you want to further troubleshoot this behaviour, you can:

1. Post this question in Server Fault [2] 

2. If you think this is related to an issue with Cloud DNS, you can report it by going to the attached link at the bottom of this message [3].

3. Create a Support case with GCP if you already have the support package [4]

Before concluding I would like to mention that the IP included in your Cloud DNS is available when querying your domain wdlaoo.com (indicating the screenshot may be a local network issue):

$ dig wdlaoo.com +short

35.215.36.131

All that being said, if you still face this issue I would recommend reaching out to Server Fault[2] for further assistance.

Footnotes

[1] Google Groups: https://cloud.google.com/support/docs/community#discussions_google_groups

[2] ServerFault:  https://serverfault.com/

[3] Report a Cloud DNS Issue:  https://issuetracker.google.com/issues/new?component=187241&template=1162897

[4] Google Cloud Platform Support plans:  https://cloud.google.com/support/