在名称服务器打开 whois 记录之前,DNS 服务器不响应是否正常?

发布于 2024-07-13 22:43:56 字数 336 浏览 5 评论 0原文

有人告诉我,DNS 服务器只有在 whois 记录更新为指向其 DNS 服务器后才开始响应。 这是正常行为吗? 或者 DNS 服务器应该在更新 whois 记录之前做出响应吗?

另外,一旦域处于活动状态(因此在添加域之后或在更新 whois 记录之后,具体取决于上述问题的答案)名称服务器应开始响应多久?

我不是指在互联网上传播所需的时间,而是指域的名称服务器上的时间。 我也不关心互联网的其他部分何时看到更改,只是想知道在使用以下命令时 DNS 服务器何时应响应:

 nslookup www.example.com ns1.dnsserver.com

I have someone telling me that DNS servers only start responding after the whois record is updated to point at their DNS servers. Is this normal behaviour? Or should a DNS server respond before the whois record is updated?

Also, once the domain is active, (so either after the domain is added or after the whois record is update, depending on the answer to the above question) how long till the name servers should start responding?

I'm not referring to the time that it takes to propagate acorss the internet, but just the time on the name server for the domain. I am also not concerned with when the rest of the internet sees the change, only wondering when that DNS server should respond when using a command such as:

 nslookup www.example.com ns1.dnsserver.com

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

帅哥哥的热头脑 2024-07-20 22:43:56

为了找到您所说的 DNS 服务器,whois 记录必须知道在哪里可以找到它们。
严格来说,whois 记录不仅仅包含域的 DNS 服务器,但我们不要挑剔。

假设您的 DesktopA 需要连接到 example.com,则将联系以下服务器(假设您的 ISP 的 DNS 或本地计算机尚未缓存答案)。

  • DesktopA 具有指向 ISP 的 DNS 设置,因此 DektopA 会询问 ISP 的 DNS 服务器是否知道 example.com. 所在位置(其 IP)。

  • ISP DNS 服务器不知道,因此它将联系根域数据库以获取com.(所有完全合格的域名均以.,尽管我们一般不会显式使用它,但您可以尝试将其插入到网络请求中,它应该可以正常工作)。
    全局根服务器的引导列表通常由操作系统定期更新。
    根服务器将知道每个全球域要联系哪个顶级域 TLD 服务器,例如 .com.org.uk 等.
    在我们的示例中,ISP 将询问根哪个服务器查询 com 域。
    根服务器使用 .COM TLD 服务器之一的 IP 地址进行应答。

  • ISP DNS 服务器现在将联系 .COM TLD 服务器并询问它在哪里可以找到示例。
    example.com 的 .COM 数据库记录将包含与域名 example.com 一起注册的 2 个(或更多)DNS 服务器。 这些是您的 whois 记录的一部分。

  • ISP 现在拥有 example.com 的 DNS 服务器的 IP 地址(如 whois 中的设置)。 它将查询第一个(如果第一个不可用,则查询第二个)并询问它:“example.com”的 IP 是多少?

  • example.com 的 DNS 服务器将查找其记录,并返回为 example.com 域定义的 A 记录,IP 1.2.3.4<例如 /code>。

  • 您的 ISP 的 DNS 服务器将在预定的时间 (TTL) 内缓存此信息,并将 IP 1.2.3.4 返回到 DesktopA。

  • 桌面 A 现在可以直接通过其 IP 联系 example.com 服务器。
    DesktopA 可能会将此信息缓存一段时间,以便快速查找。

对于 www.example.comjohn.people.example.com 等子域来说也是如此。 域 example.com 之前的所有内容都必须在您的 DNS 服务器中声明,以便当有人查询其地址时,您的 example.com DNS 服务器可以查找定义并给出答案它们(如果需要的话,它也可以将它们传递到另一台服务器)。

结论

因此,回到您的问题,您的 whois 记录必须使用您的域的正确 DNS 记录进行设置,然后任何人都可以使用该域名访问它们。

For the DNS servers to be found what you call the whois record must know where to find them.
Stricly speaking, the whois record contains much more than just the DNS servers for a domain, but let's not nitpick.

Say your DesktopA needs to connect to example.com, the following servers will be contacted, assuming the answer wasn't already cached by your ISP's DNS or the local machine.

  • DesktopA has DNS settings pointing to the ISP, so DektopA will ask the ISP's DNS servers if they know where example.com. is located (its IP).

  • ISP DNS server doesn't know, so it will contact the root domain database for com. (all Fully Qualified Domain Names end in a ., even though we generally don't use it explicitly, but you can try insert it in web requests, it should work fine).
    This bootstrap list of global root servers is usually updated by the OS regularly.
    The root servers will know which Top Level Domain TLD server to contact for each global domain such as .com, .org, .uk, etc.
    In our example, the ISP will ask the root which server to query for com domains.
    The root server answers with the IP address of one of the the .COM TLD servers.

  • The ISP DNS server will now contact the .COM TLD server and ask it where to find EXAMPLE.
    The .COM database record for example.com will contain the 2 (or more) DNS servers registered along with the domain name example.com. These are part of your whois record.

  • The ISP now has the IP addresses of the DNS servers for example.com as setup in the whois. It will query the first one (or the second one if the first isn't available) and ask it: what's the IP of 'example.com'?

  • The DNS server for example.com will look in its records and return the A record defined for the example.com domain as IP 1.2.3.4 for instance.

  • Your ISP's DNS server will cache this information for a predetermined amount of time (TTL) and return the IP 1.2.3.4 to DesktopA.

  • Desktop A can now contact the server for example.com directly by its IP.
    DesktopA may cache this information for a little while for fast lookup.

Tis would be the same for subdomains such as www.example.com or john.people.example.com. Everything before the domain example.com must be declared in your DNS server so when someone query for their address, your DNS server for example.com can look up the definitions and answer them (it could very well pass them on to another server as well if necessary).

In conclusion

So, to go back to your question, your whois record must be set with the proper DNS records for your domain before anyone can access them using that domain name.

我ぃ本無心為│何有愛 2024-07-20 22:43:56

DNS 服务器完全独立于 Whois 服务器运行。 Whois之后DNS更新速度的关系完全取决于注册商。 注册商或网络主机可能会在客户在控制面板中进行更改后的一两秒内更新 DNS,或者如果他们以批处理模式进行更新,则可能需要几分钟或几小时。

理想情况下,客户请求的所有 DNS 更改都应该在 DNS 服务器上非常快速地发生(几秒钟内),但正如您所注意到的,在更改通过互联网传播之前可能会有延迟。

DNS Servers operate completely separate from the Whois server. The relation of how fast DNS is updated after Whois depends completely on the registrar. A registrar or web host may update DNS within a second or 2 of a customer making a change in the control panel, or it may take minutes or hours if they make updates in batch mode.

Ideally all DNS changes that a customer request should happen very quickly on the DNS server (within a few seconds), but as you note, there may be a delay until changes propagate across the internet.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文