DNS TXT/CNAME records are still not getting propagate

[noramirkh]

Hi,

I have requested to check and fix any propagation issue for my domain http://www.topdoctors.am/.

Domain is hosted on GoDaddy ns37.domaincontrol.com, but that name server can't see my records.

It has already been 3 days I am raising this topic with GoDaddy. They told it can take up to 72 hours. And that time has passed, but my records still haven't been propagated.

What to do?

[PL281]

@noramirkh 

I see your Office 365 MX record and TXT verification record - what other records are missing - can you send a screen capture of https://dcc.godaddy.com/manage/topdoctors.am/dns

[noramirkh]

I expect to see below records if I use nslookup utility or any online service which shows DNS records.

[TLH]

Hi @noramirkh,

Welcome to the Community!

As your domain is not registered with GoDaddy, you may wish to ask your registrar to reconcile (report) your records to the appropriate Registry. Your website is resolving for us. Are you able to access the DNS in your GoDaddy account?

[noramirkh]

I have deleted my hosted DNS and recreated again.

Added new name servers in my domain registrar.

I can access "some dns editor" by link https://dcc.godaddy.com/manage/topdoctors.am/dns

I have added new records. If I check hosted domains on ns31.domaincontrol.com I can't see topdoctors.am there as of now. Maybe I need to wait more?

I have used following to check that:

https://securitytrails.com/list/ns/ns31.domaincontrol.com

Also this time when I added my domain for DNS management I can see it under Domains:

https://dcc.godaddy.com/domains

What to do next? Wait? Should I expect that this time my records will be propagated to internet?

[PL281]

@noramirkh 

Using https://toolbox.googleapps.com/apps/dig/#A/ I was able to put in your domain / subdomains and confirm the DNS was displaying as you showed

[noramirkh]

Could you please share your screenshot? I am not able to see my TXT and CNAME recorda

[PL281 · Accepted solution]

@noramirkh 

I see you amazon SES record  - the issue is the host should have just been _amazonses

What you created was _amazonses.topdoctors.am.topdoctors.am

 

[noramirkh]

Brilliant. Thanks, it was my mistake.