Difference between revisions of "CNAME"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
* [[aliases]] in <code>[[aws_cloudfront_distribution]]</code> Terraform resource | * [[aliases]] in <code>[[aws_cloudfront_distribution]]</code> Terraform resource | ||
* [[Using alternate domain names and HTTPS]] | * [[Using alternate domain names and HTTPS]] | ||
| + | * [[A]] | ||
== See also == | == See also == | ||
Revision as of 15:46, 11 February 2024
aws route53 list-resource-record-sets --hosted-zone-id /hostedzone/ZXXXXX31 --output text | grep CNAME
To add an alternate domain name (CNAME) to a CloudFront distribution, you must attach a trusted certificate that validates your authorization to use the domain name. For more details, see: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html#alternate-domain-names-requirements
Related
- aliases in
aws_cloudfront_distributionTerraform resource - Using alternate domain names and HTTPS
- A
See also
dig, host, nslookup, delv, axfr, resolvectl query, dig -t NS, dig -t MX, dig -t TXT, dig -t SOA- DNS: Linux DNS, IP,
systemd-resolve,/etc/hosts,whois, Domain registrar,dig,host,nslookup,scutil --dnsdnsmasq,bind,delv,.local,.internal, .onion, FQDN, TTL,/etc/resolv.conf,/etc/systemd/resolved.conf,dscacheutil(macOS),hostname, hostnamectl,bind,resolvectl status, DNS sinkhole, Domain name server, LLMNR, Resource records:MX, TXT, NS, CAA, SSHFP, Apex, CNAME, Wildcard DNS records, Subdomain, /etc/nsswitch.conf,1.1.1.1,8.8.8.8, CoreDNS, dnsPolicy:, Google Public DNS, DNS caches, Kubernetes ExternalDNS, DNS forwarding, IDNA2008, DNS-1035, Domain name registrars, Split-view DNS, Pi-hole, NextDNS
Advertising:
