mDNSResponder is also in control of Bonjour advertisement and unicast DNS resolution. So killing mDNSResponder is a good way to clear your cache in the same way that throwing your computer out a window is a good way to turn it off.
Why not continue to use "sudo dscacheutil -flushcache" like we always have? It still even works in 10.7+.
As Linc indicated, the command recommended by Apple is:
sudo killall -HUP mDNSResponder
This restarts the process; it doesn't kill it. In 10.7 and 10.8 the mDNSResponder daemon caches DNS query results, so even if you flush the other cache, old results can still crop up. Restarting the mDNSResponder daemon clears that cache.
Regards.
As Linc indicated, the command recommended by Apple is:
sudo killall -HUP mDNSResponder
This restarts the process; it doesn't kill it. In 10.7 and 10.8 the mDNSResponder daemon caches DNS query results, so even if you flush the other cache, old results can still crop up. Restarting the mDNSResponder daemon clears that cache.
Regards.
Killing mDNSResponder is not the recommended method of clearing the DNS cache. Sending it a HUP signal is the recommended method.
Why is killing mDNSResponder the recommended method of clearing your DNS cache in 10.7+?
