Why is the Route 53 Alias record for an Elastic Load Balancer not working or resolving?
Why is the Route 53 Alias record for an Elastic Load Balancer not working or resolving?
For more details see the Knowledge Center article with this video: https://repost.aws/knowledge-center/e…
Vanit shows you why Route 53 Alias record for an Elastic Load Balancer is not working or resolving.
Content
0.38 -> [Music]
11.559 -> hello I invented one of the clouds about
14.389 -> engineers here at the a SS office in
17 -> Bangalore India sometimes customers ask
19.939 -> me why their alias record to an elastic
22.58 -> load balancing DNS did not resolve as
24.89 -> expected today I will review one of the
27.5 -> possible answers for this Amazon route
30.29 -> 43 offers alias records to route traffic
33.11 -> to selected aww services such as elastic
36.559 -> load balancing CloudFront s3 buckets and
39.05 -> so on Alysse records can behave
41.57 -> similarly to a cname record but the key
43.67 -> difference is that cname record
44.87 -> redirects queries for a domain name
46.699 -> regardless of record type whereas the
50.03 -> alias records follows the pointer in
52.67 -> that alias record only when record type
54.71 -> also matches now let's see how a small
57.35 -> miss configuration can cause this DNS
59.3 -> resolution to fail and then how to fix
61.519 -> the missed configuration first let's
65.03 -> check the response we are seeing from
66.8 -> Amazon route 53 name server using a
69.14 -> terminal if you get a refused response
72.2 -> when queried directly to any route 53
74.45 -> provider main server then you are likely
76.939 -> seeing the record mismatch on your alias
79.25 -> record
80.92 -> after logging into the AWS management
83.38 -> console navigate to Amazon route 53
86.44 -> console
91.369 -> navigate to hosted zones using the left
94.04 -> pane and then select the hosted zone for
97.07 -> your domain
99.21 -> select the route 53 illness record for
101.82 -> your domain
105.2 -> as we can see when we check the record
108.02 -> type is cname this is incorrect and
110.119 -> should be of type a as an elastic load
113.93 -> balancing DNS resolves to an IP directly
116.39 -> change the type from C name to a
123 -> save the record check
125.67 -> the DNS changes should be propagated
127.38 -> soon let's test if the DNS resolution
130.11 -> works
136.569 -> thanks for watching and happy cloud
138.4 -> computing from all of us here at AWS
141.85 -> [Music]
145.58 -> you
Source: https://www.youtube.com/watch?v=YPNzeuNd-lA