blocks|key|291939|text|旧的IP地址可能正在被您查询的服务器缓存。首先，检查两个新的权威域名服务器是否都发布了正确的地址，方法是直接使用dig查询它们：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|291940|dig+@ns1.newnameserver+domain.+a
dig+@ns2.newnameserver+domain.+a|code-block|syntax|javascript|291941|假设这些查询给出了正确的答案，挖掘其他一些不是这样的服务器：|291942|dig+domain.+a+++++#+Use+the+system's+default+resolvers
dig+@8.8.8.8+domain.+a+++++#+Use+Google's+public+resolver
dig+@some.other.ip.address+domain.+a|291943|如果它给出了旧的答案，看看TTL。这是答案中列出的数字字段，紧跟在名称之后和"+in“之前。这是在您查询的服务器丢弃其缓存数据并再次查询权威服务器之前，您必须等待的秒数。|291944|问问那些相同的域名服务器，他们认为“域”在哪里。是委派的：|291945|dig+domain.+ns+++++#+Use+the+system's+default+resolvers
dig+@8.8.8.8+domain.+ns+++++#+Use+Google's+public+resolver
dig+@some.other.ip.address+domain.+ns|291946|您希望看到"domain.“的两个NS代码，一个指向"ns1.newnamserver”，另一个指向"ns2.newnameserver"，但解析程序同样会缓存这些信息，以便它们仍然具有旧的名称服务器。如果是这样，也可以查看这些NS记录上的TTL。如果这些记录上的TTL比A记录上的TTL长，那么这些解析器可能仍然会去旧的名称服务器获取“domain.”的A记录，即使它们当前缓存的副本过期了……所以您可能需要等待该TTL首先过期，然后等待实际A记录上的TTL再次过期！|291947|你可以做的另一件事是向一些权威的域名服务器查询你的域的父域，看看他们是否真的把它委托给了"ns1.newnameserver“和"ns2.newnameserver”。这将验证DNS中的委派是否与WHOIS中的委派相匹配。|291948|dig+com.+ns++++++#+If+your+domain's+parent+domain+is+"com."
dig+@<one-of-the-servers-that-resulted-from-that-query>+domain.+ns|291949|同样，您希望看到"domain.“的两个NS代码，一个指向"ns1.newnamserver”，另一个指向"ns2.newnameserver“。|291950|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

The old IP address is probably being cached by the server you queried. First of all, check that BOTH your new authoritative nameservers are publishing the correct address by querying them directly with dig:

<pre><code>dig @ns1.newnameserver domain. a
dig @ns2.newnameserver domain. a
</code></pre>

Assuming those queries give correct answers, dig some other servers that aren't:

<pre><code>dig domain. a # Use the system's default resolvers
dig @8.8.8.8 domain. a # Use Google's public resolver
dig @some.other.ip.address domain. a
</code></pre>

If it gives the old answer, look at the TTL. That's the numeric field listed in the answer just after the name and before "IN". That's how many seconds you have to wait until the server you queried discards its cached data and will query the authoritative servers again.

Ask those same nameservers where they think "domain." is delegated:

<pre><code>dig domain. ns # Use the system's default resolvers
dig @8.8.8.8 domain. ns # Use Google's public resolver
dig @some.other.ip.address domain. ns
</code></pre>

You want to see 2 NS reocrds for "domain.", one pointing to "ns1.newnamserver" and the other one to "ns2.newnameserver", but the resolvers likewise cache that information so they might still have the old nameservers. If so, look at the TTL on those NS records too. If the TTL on those records is longer than the TTL on the A records, those resolvers may still go to the old nameservers to get "domain."'s A records even when their currently cached copy expires... so you may need to wait for that TTL to expire first, and then for the TTL on the actual A record to expire again!

Another thing you can do is query some of the authoritative nameservers for the PARENT domain of your domain to see if they are indeed delegating it to "ns1.newnameserver" and "ns2.newnameserver". This will verify that the delegation in DNS matches what's in WHOIS.

<pre><code>dig com. ns # If your domain's parent domain is "com."
dig @&lt;one-of-the-servers-that-resulted-from-that-query&gt; domain. ns
</code></pre>

Again, you want to see 2 NS reocrds for "domain.", one pointing to "ns1.newnamserver" and the other one to "ns2.newnameserver".

blocks|key|117557|text|如果旧名称服务器仍在运行，请执行以下任一操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|117558|117559|确保它们没有安装，或者|ordered-list-item|117560|确保他们也安装了新的区域data|117561|117562|有些人仍然会与旧的名称服务器交谈，除非他们停止回答或给出正确的答案，否则他们不会从父专区学习新的名称服务器。|117563|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

If the old nameservers are still running, either:

<ol>
<li>make sure they aren't, or</li>
<li>make sure they've also got the new zone data</li>
</ol>

Some people will still be talking to the old nameservers, and until they either stop answering or give the right answer, they won't learn the new nameservers from the parent zone.

I setup a couple of nameservers and updated my domain to use them, and as far as I can tell everything went fine and the nameservers have been updated, or so says every whois and dnstools type site ive used, (intodns, who.is etc are all saying the same thing: the new nameserrvers are in effect, and the site points to the new ip just fine). Problem is that The site is not showing up, and dig tells me that the old ip/nameservers are still effective.

In my DNS Records I have:

<pre><code>domain. A IN NS ns1.newnameserver

domain. A IN NS ns2.newnameserver

ns1 IN A newipaddress

ns2 IN A newipaddress

domain. IN A newipaddress
</code></pre>

I'm very short on time and haven't found anything on the interweb, so any help would be much appreciated

BIND config error in ip/nameserver

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我设置了几个域名服务器，并更新了我的域名来使用它们，据我所知，一切都很好，域名服务器已经更新了，或者说每个我使用过的类型站点都是这样说的，(intodns，who.is等都在说同样的事情:新的域名服务器生效了，站点指向新的ip就好了)。问题是该网站没有出现，而dig告诉我旧的ip/名称服务器仍然有效。在我的DNS记录中...

问ip/名称服务器中的绑定配置错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ip/名称服务器中的绑定配置错误EN