Firefox无效dns缓存 [英] Firefox invalidate dns cache

问题描述

对于访问我在客户服务器上设置的站点来说，我太快了，Firefox现在记得，默认的网站（例如）

  testsite.mycompanyname.com（不存在的子域名，与* .mycompanyname.com相同）
  

是

  www.mycompanyname.dk  - 或者是默认服务器的IP 
  

我以后再设置公共DNS（a-record）来重定向到另一台服务器，但是Firefox会记住默认的IP地址。 / p>

Chrome / IE / Safari - 没有问题，因为他们在DNS踢入之前没有访问过该网站...

我已经设置了这些：config：

  network.dns.disablePrefetch = true 
 network.dnsCacheExpiration = 0 
  

还有什么？

我真的需要firebug来调试该网站的前端....

干杯

解决方案

DNS c麻烦发生在多个级别：
应用程序询问本地系统，
要求本地配置的解析DNS服务器，
要求权威的DNS服务器。

< h3>按应用程序进行缓存有所不同。

• 我发现Firefox的退出和重新启动工作正常。 中的相关设置：config 是 network.dnsCacheExpiration ，可以设置为 0 以禁用缓存。

本地系统的缓存通常为1小时。

• 诊断：ping，像其他应用程序一样，使用本地系统DNS缓存


• 刷新MacOsX 10.8： sudo killall -HUP mDNSResponder （参考）
  
  （可能有所不同对于其他版本）


• 刷新Windows： ipconfig / flushdns （仅当DNS缓存服务 HKLM\\启用\\ SYSTEM\CurrentControlSet\Services\Dnscache ，检查与 net start | findstr / i dns 或 compmgmt.msc ）


• Linux / Unix可能使用 nscd （名称服务缓存守护程序），或 dnsmasq 或两者都可以...

通过本地解析的DNS服务器进行缓存跑几天，依靠在与DNS记录相关的TTL上ng。

• 诊断： nslookup 解决服务器，然后请求地址。


• 刷新BIND： rndc flush 或 rndc flushname DOMAIN.NAME

TTL 代表生活时间用于描述DNS记录被请求的客户端或服务器认为有效的时间的术语。短的TTL意味着请求者被告知不缓存DNS查找太久。 TTL可以从几秒钟（例如DynDNS和类似的）到几天或几周。

I was too quick about visiting a site I set up on a customer server, and Firefox now remembers, that the default site for (example)

testsite.mycompanyname.com (non existing subdomain, same as *.mycompanyname.com)

is

www.mycompanyname.dk - or rather the IP of the default server

I have then later set up the public DNS (a-record) to redirect to another server, but Firefox remembers the default IP adress.

Chrome/IE/Safari - no problem, as they have not visited that site before DNS kicked in...

I have set these in about:config:

network.dns.disablePrefetch = true
network.dnsCacheExpiration = 0

Anything else?

I really need firebug to debug the frontend on that site....

Cheers

解决方案

DNS caching occurs at multiple levels: Application asks local system, which asks locally configured resolving DNS server, which asks authoritative DNS servers.

Caching by Application varies.

• I've found for Firefox that quitting and restarting works. A relevant setting in about:config is network.dnsCacheExpiration, which can be set to 0 in order to disable caching.

Caching by local system is typically 1 hour.

• Diagnostic: ping, like other applications, uses local system DNS cache
• Flush MacOsX 10.8: sudo killall -HUP mDNSResponder (reference)
  (May vary for other versions)
• Flush Windows: ipconfig /flushdns (only if the DNS caching service, HKLM\SYSTEM\CurrentControlSet\Services\Dnscache, is enabled; check with net start|findstr /i dns or compmgmt.msc)
• Linux/Unix may use nscd (name services caching daemon), or dnsmasq, or both ...

Caching by local resolving DNS server may run to several days, depending on TTL associated with DNS record.

• Diagnostic: nslookup first reports address of resolving server, then address requested.
• Flush BIND: rndc flush or rndc flushname DOMAIN.NAME

TTL stands for "time to live" a term used to describe how long a DNS record is to be deemed valid by the requesting client or server. A short TTL means that the requester is told not to cache a DNS lookup for too long. The TTL can range from mere seconds (e.g. for DynDNS and similar) to days or weeks.

这篇关于Firefox无效dns缓存的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！