......OK DONE HOW WOULD I DELETE THIS MESSAGE

0

......OK DONE HOW WOULD I DELETE THIS MESSAGE

4 Answers
1

Hi Amir,

I posted answers to your orignal question https://repost.aws/questions/QUzB_E0TFTQ8S9i7UWC7DKhg/regret-full-decision-to-chose-amazon-still-issue-with-dns-verification-cname-mx-records-gives-an-error-while-adding-to-domain-registart#ANmaMIdjMHTB-aLx03GIPU-g

Your domain is pointing to the wrong name servers/your adding your DNS Records into the wrong Zone. You need to either update the glue records for the domain or update the correct DNS Zone to include the correct DNS Records.

Update the name servers via your registrar to point to the correct name servers or create the DNS Records in the correct zone.

Also from your screen shots, you are creating DNS records in name.com when route53 is authoritive for domain and you have also provided a screen shot from route53 with DNS records in which do not match your GLUE Records.

You need to decide where you want to host your DNS Servers.

You have 3 webstechnologys.com Domains hosted in 2 different DNS services from your oringal screen shots :-

  1. Name.com
  2. Route53

To recieve updates from posts, please ensure your notification settings are correct in your profile.

Gary

profile picture
EXPERT
answered a year ago
  • what should I do? My domain is on Name.com what does it mean? as I have hosted website on amazon light sail due to this I have already added name servers but the issue with name server.

    what should I do? My only aim is to get web email 📧

    provide concise steps to follow thanks

0

Hi,

I'm sorry to hear you're experiencing problems with configuring your domain. When using LightSail, LightSail will be set as the authority on your domain. This why your domain does return an A record for your website. So to configure WorkMail you will need to add all your domain records to LightSail in the same place as your A record for your website is set.

Once you have done that you might need to click Retry in the AWS SES console for your domain as verification is only attempted for 4 days. After that you need to restart that process.

Kind regards, Robin

AWS
EXPERT
answered a year ago
0

It looks like NS records are now set to be pointing at R53 correctly for the domain.

There are currently no MX or TXT records for the domain - these need to be added to the R53 HostedZone for the domain.

As previously mentioned by Robin, the screenshot showing the errors for adding MX record (https://drive.google.com/file/d/1up7CcJFvBja96FwtxOW2cTA_9hnRg-63/view) is due to including '10 ' in the entry you're pasting into the record field - remove this (and be sure to remove the leading spaces as well) & the error should go away.

The error while adding the TXT record (https://drive.google.com/file/d/1kioNapC9kADq9tCD-9y7S6TExHS5hGst/view) is a similar issue - you have a '.' at the end of the entry you're pasting into the record field - remove this & it should be fine.

At this point, you should no longer need to make any changes to your name.com configuration, as it appears to be correctly pointing to R53 now.

AWS
Greg_H
answered a year ago
profile picture
EXPERT
reviewed a year ago
0

Hi there, I have added some records still domain verification show failed or pending

please resolves this issue

Thanks Amir Ali

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content