问题原文
原帖链接 · CoderJK · CC BY-SA 3.0
I recently transferred a domain (superteachertools.net) from GoDaddy to AWS. The domain was running on a dedicated server with GoDaddy in the Plesk environment. That server is now shut down.
It's been about a week, but the DNS records I've set up at AWS on Route 53 do not seem to be propagating.
What am I missing?
已采纳解答
原帖链接 · Esa Jokinen · CC BY-SA 3.0
You are using the same domain name in your NS records but you are missing glue records.
superteachertools.net. 172800 IN NS ns2.superteachertools.net.
superteachertools.net. 172800 IN NS ns1.superteachertools.net.
dig: couldn't get address for 'ns2.superteachertools.net': no more
Your domain is registered at Amazon, you should add them there:
Domain Name: superteachertools.net
Registry Domain ID: 1835524431_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: https://registrar.amazon.com
Updated Date: 2017-06-12T02:37:24.255Z
See Route 53 documentation, Adding or Changing Name Servers and Glue Records for a Domain.
You can also use this procedure to specify glue records (IP addresses) when you're configuring white label name servers—name servers that have the same domain name as the hosted zone. For more information about configuring white label name servers (also known as vanity name servers or private name servers), see Configuring White Label Name Servers.
Probably you have transferred your domain on 2017-06-12 to Amazon and it has just copied your
Name Server: ns1.superteachertools.net
Name Server: ns2.superteachertools.net
without adding the glue records automatically. Add glue records or change DNS servers as needed on the Amazon Route 53 console > Registered Domains > superteachertools.net > Add/Edit Name Servers > Edit Name Servers.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
