- 最新
- 最多得票
- 最多評論
Can you check because i am able to get the responce here is the screenshot
what tool are you using to get the response? I've double checked the entry and I see no issues. I'm still not seeing propagation on whatsmydns or mxtoolbox
I am using google DNS https://toolbox.googleapps.com/apps/dig/ pls check here
Hello
I think you are adding everything name provided by the provider are you sure you are doing like the example below ?
Easy way you can use google DNS to verify the DNS
Thanks GK
Yes, my record looks like what you've suggested. See below. I put in a dummy value of course in the screen shot
Hi Dan,
This looks to be resolving correctly using external tools. Was there a specific change that you made?
To go back to the root cause, verification of the new cert, I understand that some providers/tools with "rotate" of require a new TXT record value for each validation. If you are still not getting the validation and I would check in certbot (or any other means) to verify that the TXT record value is correct.
相關內容
AWS 官方已更新 1 年前- AWS 官方已更新 3 年前
- AWS 官方已更新 4 個月前
Hi Dan,
Those TXT records should be exposed globally. It is interesting that your A and MX records work as expected. Have you tried adding an additional record and seeing if it propagates properly? e.g. Just adding a custom CNAME or random A record and see if that is globally resolvable.