简体   繁体   English

为什么公共托管区域 DNS 记录无法查找?

[英]Why could Public Hosted Zone DNS records fail lookup?

I have a Route53 public hosted zone containing the normal CNAME/A/etc records for using an S3 bucket to host a static website, yet "nslookup" on these records fails, and I don't know why.我有一个 Route53 公共托管区域,其中包含使用 S3 存储桶托管 static 网站的正常 CNAME/A/etc 记录,但这些记录上的“nslookup”失败,我不知道为什么。 The domain remains unavailable on the inte.net, presumably because these DNS records fail lookup.该域在 inte.net 上仍然不可用,大概是因为这些 DNS 记录无法查找。

One of the AWS troubleshooting guides recommends using "nslookup" to check the hosted zone records, but it doesn't say what to do if it does fail.其中一份 AWS 故障排除指南建议使用“nslookup”来检查托管区域记录,但它没有说明如果失败该怎么办。

My question specifically is: since "nslookup -type=A my_domain" fails for one particular hosted zone, what can I try to resolve it?我的具体问题是:由于“nslookup -type=A my_domain”对于一个特定的托管区域失败,我可以尝试如何解决它? I can see the records there in the hosted zone.我可以在托管区域中看到那里的记录。

(I have another hosted zone which works fine - it uses a S3 bucket to host a static website. The website is publicly available and "nslookup" on the hosted zone records succeeds. I've tried to make the troublesome hosted zone equivalent to the working one, but to no avail.) (我有另一个运行良好的托管区域 - 它使用 S3 存储桶托管 static 网站。该网站是公开可用的,托管区域记录上的“nslookup”成功。我试图让麻烦的托管区域等同于工作一个,但无济于事。)

在此处输入图像描述

在此处输入图像描述

I already:我已经:

  • confirmed the hosted zone is public.确认托管区域是公共的。
  • confirmed the NS records of the hosted zone match those of the registered domain确认托管区域的 NS 记录与注册域的记录匹配
  • tried ipconfig /flushdns试过 ipconfig /flushdns

The NS and SOA records do exist, they were auto-created by AWS (are clipped from the screenshot). NS 和 SOA 记录确实存在,它们是由 AWS 自动创建的(从屏幕截图中截取)。

Edit: The response from nslookup is:编辑:nslookup 的响应是:

Server: cache1.service.virginmedia.net Address: 194.XXX.X.100服务器:cache1.service.virginmedia.net 地址:194.XXX.X.100

*** cache1.service.virginmedia.net can't find bXXXXXXXXXXe.com: Server failed *** cache1.service.virginmedia.net 找不到 bXXXXXXXXXXe.com: 服务器失败

Credit to kdgregory who got to the bottom of it, "nslookup" was not working because of some config with my ISP/router, the relevant comments are repeated here:感谢 kdgregory 深入了解,由于我的 ISP/路由器的某些配置,“nslookup”无法正常工作,相关评论在此处重复:

"This appears to be a problem with cache1.service.virginmedia.net. I tried looking up my personal website using it, waited for what seemed like 30 seconds or more, and got the message "connection timed out; “这似乎是 cache1.service.virginmedia.net 的问题。我尝试使用它查找我的个人网站,等待了 30 秒或更长时间,然后收到消息“连接超时; no servers could be reached". My next guess is that Virgin Media is your ISP, and your router is configured to use their nameserver by default"无法访问任何服务器”。我的下一个猜测是 Virgin Media 是您的 ISP,您的路由器默认配置为使用他们的名称服务器”

"You can try another nameserver, such as Google or CloudFlare, to verify that your hosted zone is set up correctly. Run nslookup without any command-line arguments, enter server 8.8.8.8 as the first interactive command (this is Google's service), then enter your hostname as the second command. Ctrl-D or Ctrl-C to exit" “您可以尝试使用其他名称服务器,例如 Google 或 CloudFlare,以验证您的托管区域是否设置正确。运行 nslookup,无需任何命令行 arguments,输入服务器 8.8.8.8 作为第一个交互命令(这是 Google 的服务),然后输入您的主机名作为第二个命令。Ctrl-D 或 Ctrl-C 退出”

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 如何找到私有区域中托管的 GCP Cloud DNS 服务器的内部 IP 地址 - How to find the Internal IP Address of GCP Cloud DNS server hosted in Private Zone 我无法在 Google Cloud DNS 中创建 DNS 区域 - I cannot create a DNS zone in Google Cloud DNS AWS 网络负载均衡器:为什么内部 NLB 会有公共 DNS 名称? - AWS Network Load Balancer: why would an Internal NLB have a public DNS name? 将私有 DNS 区域添加到 VPC 是否会导致任何问题 - Will adding a Private DNS zone to a VPC cause any issues Angular:firebase托管的网站登录失败 - Angular: the website hosted on firebase fail to log in 如何在 GCP 上设置托管区域? - How do I set up a hosted zone on GCP? 到 Route 53 私有托管区域的客户端 VPN 连接 - Client VPN Connection to Route 53 Private Hosted Zone VPC 对等 - DNS 解析为公共 IP - VPC Peering - DNS resolves to public IP 有没有人设法在 GCP 上创建一个反向 DNS 区域? - has anyone managed to create a Reverse DNS Zone on GCP -? 使用 Terraform 在 Route 53 中跨账户子域/托管区域委派 - Cross-account subdomain/hosted zone delegation in Route 53 with Terraform
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM