![]() ![]() ![]() This is NOT a resolution issue, in that an IP address or FQDN is being resolve incorrectly or being overridden by a static hosts file entry. Once you remove the static entries, you are left with the dynamically received entries. ![]() ![]() When this happens, macOS still receives DHCP option 6 (DNS server IP addresses) - it just doesn't use them (it overrides them) and forces the use of the DNS server IP addresses that it has now statically set. What's happening is that instead of those assigned IP addresses dynamically being set and removed at each connection/disconnection, macOS receives the assignments initially and then, instead of leaving them as DHCP assigned entries, converts them to statically set entries in the ist, so that each time the interface is used, it will try using them again, rather than using whatever DHCP is assigning. The reason this is a problem is when switching networks (for example, between home and work), where when I get home, it will have my work network's IP addresses in it and won't work, and the inverse happens when I've used it at home and then come to work.įor the sake of clarity, to those that are not network engineers or are just confused, DHCP assigns DNS server IP addresses to clients via option 6, and they are whatever the server/system/network engineer wants them to be. I've gone as far as editing the file rather than deleting it, but that didn't last. The only way I've been able to get it to behave for at least a day or two, is by deleting the ist out of /Library/Preferences/SystemConfiguration. When this happens, I can delete the entries and let it revert to whatever IP addresses it received via DHCP, but the next time the computer brings up the interfaces (either during a boot process or just because I told it to disconnect from the network by some means), the static entries come back. The DNS IP addresses for all interfaces (at least, the WiFi and Ethernet interfaces) are being statically set, rather than being assigned via DHCP each time. I have a strange issue that only started occurring recently (within the last 2 public OS update releases). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |