subdomain pointing to aws public hosted zones in google domains

0
votes

I have created .dev domain on google domains and want to point various subdomains to aws route53 hosted zones.

Is it possible to create subdomains

AWS NS records for aws route 53 hosted zone enter image description here

Basically what I want to do is

subdomain1.mydomain.dev => NS for route53 record in VPC1

subdomain2.mydomain.dev => NS for route53 record in VPC2

I tried using "Custom resource records" but it doesn't let me add any name server entries. Also gone through google domain help documentation but was not able to find proper solution for this.

My question is this even possible? If yes, I would appreciate any help with this.

1
amazon-web-servicesamazon-cloudfrontamazon-route53nameserversgoogle-domains
What do you mean by "NS for route53 record in VPC1"? If somebody types subdomain1.mydomain.dev, where do you want it to resolve to -- an IP address, CNAME, ELB, ...? – John Rotenstein
@JohnRotenstein if you check my second screenshot, I have created route53 record for mysubdomain.domain.dev which has 4 NS records assigned to it. I want to point subdomains to those records. Route53 then points to Cloudfront alias for s3 bucket. Let me know if you need more details about it. – prashant
I tried using "Custom resource records" but it doesn't let me add any name server entries. Are you sure about that? Create a custom resource record for the subdomain and choose "NS" from the record type drop-down list. – Michael - sqlbot
@Michael-sqlbot 2 errors "To change NS records for the root domain, edit the Name Servers section" and "Invalid record count" – prashant

1 Answers

0
votes

At last, google domain support team helped me to resolve this issue. Browser extensions were causing it to trigger weird error messages.

I followed below steps

1) disable browser extensions, such as password managers (e.g. Dashlane) or spellchecker applications (e.g. Grammarly), which may be affecting the entries on the text fields of your Google Domains page before making any updates.

2) try the update on a different browser, or device to eliminate any browser or device related issues.