So changing the DNS server on the MBP might still be effective, but you won't know for sure if you don't flush the cache.Īlso, some housekeeping questions to help avoid overlooking something else: Sorry I'm a little fuzzy on the details about how Macs choose/behave when different DNS servers are configured in multiple settings.Īlso, did you follow steps to flush the MBP DNS cache? Simply clicking Apply in System Preferences > Network won't actually flush the cache, it just tells the system to adopt your changes. You might need to login to your router and make the change there.ĭid you note what DNS server your MBP showed in System Preferences > Network? It may have been pointing towards your router and letting your router determine which DNS server is actually in use. The reason I mention all of this is that changing DNS on the MBP might not bypass the problem if the router is still using a problematic DNS server. Unless it is connected directly to a modem, it's likely the MBP is connected to a router via ethernet or WiFi.ĭepending on your hardware config, your modem+router might be combined in a single device (for instance if you are renting from your ISP) but the signal chain is still the same modem first, then router. How is your MacBook Pro connected to the internet? If this doesn’t fix your problem, it’s just as easy to change the DNS back to what you had originally and carry on.Īnd if it does the trick, well then huzzah! To get the correct commands for your OS (Mojave, High Sierra, etc.)

MacOS mojave use terminal to reset dns cache

If you prefer to use Terminal, search the internet using something similar to If you use the OnyX app (from titanium software) it can be done from the Maintenance tab. change your DNS server(s) to something different from what you have nowįlushing the DNS cache is done a little differently in each major release of macOS.If your problem is ultimately because of inability to download hk keys from hkdatastore.tk then it should be pretty easy to try his solution: The two of you are not describing identical diagnostics, but fundamentally the problem is similar - unexpectedly you can no longer read blu-ray discs. This may be a long shot, but in a post today by user iliveinabox05 he also found reference to SDF in his debug file. I notice in your debug log there are lines referencing “No SDF”.

Makemkv linux no disk