Using AWS DNS with Godaddy ( Nameservers now point to AWS provided Name Servers ) - MX SRV CNAME not propagating.
So, I was initially using the default DNS from godaddy and with the same there were some MX records etc. and the emails were also getting exchanged.
Now, I have changed the DNS records in godaddy because My Hosting Zone is in AWS Route 53 for this domain and I have also created the required -
TXT, SRV, MX, CNAME
Records in Rout53.
It has been more than 24 hours now - but still if I run the dig tnpnews.in command it doesn't reflect any of the records rather it just shows NS and SOA records there.
My emails are also not working - any ideas here ?
--- EDIT 1 ----
Here is my Route53 Config
- Le plus récent
- Le plus de votes
- La plupart des commentaires
I would look again at your config in Route 53. I agree that there are no MX records showing publicly based on dig.
Once you update them in the Public Hosted Zone, you should be able to see them pretty much immediately using dig against one of your specified name servers using the following syntax. In this syntax the @ sends the dig lookup to the specified host and since you are sending to the NS that you are updating in Route 53 this avoids any TTL caching and lets you look at the raw record.
dig tnpnews.in -t MX @ns-65.awsdns-08.com
You can substitute any of the AWS NS servers listed for the Public Hosted Zone after the @ symbol.
Hope this helps!
Contenus pertinents
- Réponse acceptéedemandé il y a un an
- demandé il y a 2 mois
- demandé il y a 7 mois
- demandé il y a 10 mois
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a 2 ans
Thanks for the response.
So, I tried with all of my NS servers with the command that you have suggested, but there is same out put for all (though the NS servers in each response are different, ofcourse ).
e.g. dig tnpnews.in -t MX @ns-1628.awsdns-11.co.uk
; <<>> DiG 9.10.6 <<>> tnpnews.in -t MX @ns-1628.awsdns-11.co.uk ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34859 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tnpnews.in. IN MX
;; AUTHORITY SECTION: tnpnews.in. 900 IN SOA ns-1628.awsdns-11.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
;; Query time: 5 msec ;; SERVER: 205.251.198.92#53(205.251.198.92) ;; WHEN: Thu Aug 24 12:14:14 IST 2023 ;; MSG SIZE rcvd: 126
Also, I have edited my post to include the Route53 Config.
Remove the '@.' from your MX entry record name. The record name should be 'tnpnews.in' just like your NS and SOA record names.
thanks, it has started showing up - does it mean I need to remove @ from the other places as well - actually the godaddy guys asked to do it this way.
Yes, I would remove the '@.' from each. I think that may have been something specific to GoDaddy's system however when you are putting in Route 53 that way you are actually creating a record for a subdomain called @ rather that the base domain.