domain-name-system – 名称服务器适用于除.org之外的所有TLD

前端之家收集整理的这篇文章主要介绍了domain-name-system – 名称服务器适用于除.org之外的所有TLD前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我最近建立了一个私人名称服务器(ns1.mediamechanic.net / ns2.mediamechanic.net),它似乎适用于除.org域名之外的所有内容(请参阅obapps.org).

据我所知,失败发生在请求进入我们的服务器之前,因此我们的注册商(eNom)可能会出现问题.

当我对工作TLD(.com,.net)进行跟踪时,我得到了这个:

===================================================
Sending request to "e,gtld-servers.net" (192.12.94.30)
===================================================
Received referral response - DNS servers for "iclaimpreview.com":
-> ns1.mediamechanic.net (216.114.240.114)
-> ns2.mediamechanic.net (208.115.254.250)
===================================================
Sending request to "ns1.mediamechanic.net" (216.144.240.114)
===================================================
Received authoritative (AA) response:
-> Answer: A-record for iclaimpreview.com = 216.114.240.114
-> Authority: NS-record for iclaimpreview.com = ns2.dallas-idc.com
-> Authority: NS-record for iclaimpreview.com = ns2.dallas-idc.com
===================================================

一个.org产生这个:

===================================================
Attempting to resolve DNS server name "ns1.mediamechanic.net" (details not logged)
===================================================
Failed to resolve DNS server name - error: No such host is known
===================================================
Attempting to resolve DNS server name "ns2.mediamechanic.net" (details not logged)
===================================================
Failed to resolve DNS server name - error: No such host is known
===================================================
Failed to resolve - no more DNS servers left to try
===================================================

似乎对于.org来说,它甚至无法找到名称服务器,这没有多大意义,所以我不知所措.

解决方法

问题中的错误消息实际上说明了一切,问题只是NS记录中引用的名称ns {1,2} .mediamechanic.net此时无法解决.

对于.com / .net来说,尽管有一个明显的问题,它仍然“有效”,因为许多解析器只使用收到的胶水而不查找权威记录.这两个TLD都位于同一组域名服务器上,因此在这两种情况下都提供了粘合剂.

在.org的情况下,TLD是一组完全不同的名称服务器,所以那里没有粘合剂.然后解析器将尝试查看这些名称,这是目前不可能的.

猜你在找的HTML相关文章