Copy Additional Validated with airSlate SignNow

Renew validated field

[Music] hello i'm anub a cloud support associate here at the aws office in northern virginia today i'm going to show you how to use cname records to validate ownership of domains and how to correctly add or edit the cname records in the dns configuration let's get started as you can see i'm logged into my aws management console and have opened the acm console to showcase the first scenario where you face this issue because the cname record isn't added to the correct dns configuration i'll request a new public certificate for my domain when prompted to select a validation method i'll choose dns validation as soon as i confirm my request domain acm generates a cname record for each domain name in my certificate you can also view the cname record after creating the certificate by navigating to the acm console choosing the certificate and then selecting the required domain name in the domain section like so to confirm if the cname record was added correctly to your dns configuration i'll use the dic command in my terminal the drip command is included in most linux and mac os installations by default via the terminal so first i'll copy the name of the cname record and then switch over to my terminal to use the dick command like so this dick command returns the value of the cname record if the cname record was added to the correct dns configuration and propagated successfully however as we can see this command returns no output now i'm switching over to the acm console to resolve this issue because i'm using amazon route 53 to host my domain i'll use this convenient option in acm to automatically create the cname record in route 53. if you're using a different dns provider to host your domain add the cname record according to the guidelines from your dns provider we can use the same command again to confirm whether the changes are propagated or not so now i'll be switching over to the terminal because the value of the cdm record is returned we can be assured that the cname record was correctly added after the dns provider propagates your record update acm can take several hours to validate the domain name and issue the certificate during this time acm continues displaying the validation status as pending validation but after validating the domain name acm changes the validation status to success now one way to determine which dns configuration to add the senior record to is to check the name servers of the dns configuration for the domain name to do this i'll use the following deck command in my terminal so if and when adding the cname record to the dns configuration make sure that the dns configuration includes an ns record with the name servers provided in the output of the previous command another reason why a certificate may be stuck in pending validation state is because the cname record in your dns settings has additional characters or his missing characters switching over to the acm console for this scenario let's consider the certificate which is stuck in pending validation status here note the name of the cname record as i copy the value of the senum record into my clipboard if i search the dns records in my route 53's hostess zone according to the value of the cname record then i can see that a record set indeed was created but as you can see the name in the cname records name field is missing a character that is it's missing an underscore at the beginning so i'll edit the cname record's name field to add the missing character and save it by doing so acm successfully performs the validation of the certificate now before i switch to my terminal to show another reoccurring scenario let me copy the name of the cname record i'll be using to showcase the scenario i'll be switching over to the acm console in some cases despite adding the cname record to the correct dns configuration a certificate can be stuck in pending validation status if the dns provider automatically adds the bare domain to the end of its dns records to explain further i'll use a cname record from a similar scenario i set up in my account switching over to the terminal this is the correct name of my senior record but this is how the dns provider has stored the name of my senior record to determine if your dns provider automatically added the pair domain to the end of the cname record you can use the deck command like so if the value of the cname record is returned in the output just like here then it's an indication that the dns provider has added the pair domain to the end of the name of the cname record in the dna settings to resolve this you must edit the name of the cname record and remove the pair domain switching over to the route53 console so i'll navigate over to my domain's dna settings which in my case is the hosted zone in raw 53 and then i'll select the erroneous cname record here i'll choose this pencil icon to edit the name of my cname record now i'll remove the pair domain from the editable part after i save this the name of the cname record appears as the expected name this is because when the dns provider adds the bare domain there is only one bare domain present this way acm can successfully validate the certificate thanks for watching and happy cloud computing from all of us here at aws [Music]