Sub-subdomain records for public hosted zone in AWS not working

amazon-route53dns-zone

I have added public hosted zone foo.mydomian.io in Route 53 and got my DNS provider to add name-servers for the sub-domain, however any records I create for mapping instances be it Type – A or CNAME don't work. If I run a dig +trace ns I get a response which shows the AWS NS records for my subdomain, but I still reach instances using the names XXXX.foo.mydomain.io

I am not sure how to further troubleshoot this, or whom to seek support in this case, is it my DNS provider or Amazon?

What I also notice in the dig output is something like this in the answer section

foo.mydoamin.io.    3600    IN  NS  ns-1143.awsdns-14.org.mydomain.io.
foo.mydoamin.io.    3600    IN  NS  ns-403.awsdns-50.com.mydomain.io.
foo.mydoamin.io.    3600    IN  NS  ns-1764.awsdns-28.co.uk.mydomain.io.
foo.mydoamin.io.    3600    IN  NS  ns-775.awsdns-32.net.mydomain.io.

I am wondering if the answer should atually be

foo.mydoamin.io.    3600    IN  NS  ns-1143.awsdns-14.org.

only?

Best Answer

Your DNS provider has made an error in setting up the DNS records, by not ending the NS record with a final .

In this context, if the hostname of the record does not end with a ., it ends up thinking that it's a relative record.

I.e. inside the zone mydomain.io, if you make an NS record like:

foo.mydomain.io. 3600 IN NS ns-1143.awsdns-14.org

It will end up resolving as "ns-1143.awsdns-14.org.mydomain.io" whereas if you put in:

foo.mydomain.io. 3600 IN NS ns-1143.awsdns-14.org.

(Note the extra trailing .) you will get the expected results.

Contact your DNS provider and have them repair the records accordingly.

Related Solutions

Route53 only for wildcard subdomain

You would add appropriate NS records for aws.example.com pointing to Route53's name servers. For example:

aws.example.com. IN NS ns-2012.awsdns-59.co.uk.
aws.example.com. IN NS ns-650.awsdns-14.com.
aws.example.com. IN NS ns-102-awsdns-45.org.

How to setup AWS Route53 Alias and CNAME

Using Route 53, setting up DNS records for your EIP isn't any different than for a regular one.

For your records - you need to set up an A record that points to example.com. Keep in mind that Route 53 will not allow you to have a CNAME record pointing to your root domain (example.com). Another caveat is that, once you create a CNAME record for your subdomain, you cannot associate ay additional records with it. For example, you couldn't use mail.example.com as a CNAME record for your email portal, as well as an MX record.

If you just want to set up www.example.com, and have it point to your EIP, just set up an A record pointing to example.com, and configure a CNAME record to point to www.example.com. Here's what my console looks like:

Example

Note - make sure there aren't any forbidden characters in your string. Sometimes the console will throw an error saying that it cannot add that type of record - usually its because you have copy & pasted, and there's a space in there or some other invisible character.

Best Answer

Related Solutions

Route53 only for wildcard subdomain

How to setup AWS Route53 Alias and CNAME

Related Topic