To get the results above open Console.app, choose your hostname in "Devices" and use a filter mDNSResponder & Cache size: This can easily be tested with the following command sequence: sudo killall -INFO mDNSResponderĭefault 03:54:55.672826 +0200 mDNSResponder Cache size 282 entities 189 in use (73 group, 29 multicast, 87 unicast) 2 referenced by active questionsĭefault 03:54:55.694219 +0200 mDNSResponder Unicast Cache size 1769 sudo dscacheutil -flushcacheĭefault 03:55:52.148629 +0200 mDNSResponder Cache size 282 entities 180 in use (79 group, 19 multicast, 82 unicast) 2 referenced by active questionsĭefault 03:55:52.157180 +0200 mDNSResponder Unicast Cache size 1992 sudo killall -HUP mDNSResponderĭefault 03:56:39.446829 +0200 mDNSResponder Cache size 282 entities 8 in use (4 group, 0 multicast, 4 unicast) 2 referenced by active questionsĭefault 03:56:39.466259 +0200 mDNSResponder Unicast Cache size 121 Sudo killall -HUP mDNSResponder sends a hang up to mDNSResponder, launchd will restart the daemon and the DNS cache will be cleared as spillover effect. Sudo dscacheutil -flushcache does nothing useful related to DNS cache entries - at least in non-LDAP environments and 10.9-10.13.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |