[{"data":1,"prerenderedAt":41},["ShallowReactive",2],{"$f2444e9cl1818k":3},{"title":4,"seoTitle":5,"description":6,"route":7,"kind":8,"toolKey":9,"intro":10,"indexable":11,"sections":12,"related":38},"NS 查询","NS 查询 | nslookup.online","查询域名 NS 记录及域名服务器 A\u002FAAAA 地址，区分递归响应、权威查询与父区委派，不输出未经验证的一致性结论。","\u002Fzh\u002Fns-lookup\u002F","tool","ns","查看递归解析器返回的域名服务器及补充地址。",true,[13,20,26,32],{"id":14,"title":15,"paragraphs":16,"code":19},"read-answer","读取域名服务器记录",[17,18],"NS 记录指定负责某个 DNS 区域的域名服务器。输入要检查的区域名称，注意子域与父域可能由不同服务器管理。","结果来自所选公共递归解析器，可能有缓存，不代表本工具已经直接询问列出的每个权威服务器。","example.com.  86400 IN NS ns1.example.net.\nexample.com.  86400 IN NS ns2.example.net.\n\n文档示例 — 非实时 DNS 响应",{"id":21,"title":22,"paragraphs":23},"addresses","补充查看服务器地址",[24,25],"为最多八个不同 NS 目标补充 A\u002FAAAA 查询。保留成功的 NS 结果，地址查询故障单独显示。","递归查到的地址不能证明父区 glue 完整、委派一致或服务器可从任意网络访问。",{"id":27,"title":28,"paragraphs":29},"delegation","NS 响应不等于委派验证",[30,31],"注册商或父区的委派与区域内部的 NS 数据属于不同观察点。本工具未直接对照父子区，因此不声称委派一致。","若刚修改域名服务器，应同时核对注册商、DNS 提供商与旧缓存的 TTL，不要仅以一次响应判断变更已全球生效。",{"id":33,"title":34,"paragraphs":35},"questions","遇到失败时如何排查",[36,37],"区分 NXDOMAIN、SERVFAIL、REFUSED 和 HTTP 超时。无 NS 记录也可能是查了并非独立区域的主机名。","需要第二视图时手动切换解析器。解析器对照不是全球探针；持续故障应结合提供商状态和权威工具进一步核验。",[39,40],"\u002F","\u002Fguides\u002Fnslookup-command\u002F",1792661399249]