Timeline for macOS keeps reverting to static DNS IP addresses
Current License: CC BY-SA 4.0
36 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 27, 2023 at 2:48 | answer | added | Kushal K | timeline score: 0 | |
| Dec 29, 2020 at 10:08 | answer | added | Xiang | timeline score: -1 | |
| Sep 11, 2020 at 11:00 | history | edited | Jesse P. | CC BY-SA 4.0 |
added 220 characters in body
|
| Sep 11, 2020 at 3:59 | answer | added | CiscoJoe | timeline score: 3 | |
| Sep 5, 2019 at 19:14 | history | edited | Jesse P. | CC BY-SA 4.0 |
Added Edit 10
|
| Aug 29, 2019 at 19:20 | vote | accept | Jesse P. | ||
| Aug 29, 2019 at 18:13 | history | edited | Jesse P. | CC BY-SA 4.0 |
Added Edit 9
|
| Aug 29, 2019 at 17:11 | history | edited | Jesse P. | CC BY-SA 4.0 |
Added Edit 8
|
| Aug 28, 2019 at 21:13 | history | edited | Jesse P. | CC BY-SA 4.0 |
Added Edit 7
|
| Aug 28, 2019 at 18:05 | answer | added | Prado | timeline score: 5 | |
| S Aug 14, 2019 at 15:03 | history | bounty ended | CommunityBot | ||
| S Aug 14, 2019 at 15:03 | history | notice removed | CommunityBot | ||
| Aug 11, 2019 at 3:01 | history | tweeted | twitter.com/askdifferent/status/1160385764531888128 | ||
| Aug 11, 2019 at 0:15 | history | edited | Jesse P. | CC BY-SA 4.0 |
added 602 characters in body
|
| Aug 9, 2019 at 13:30 | history | edited | Jesse P. | CC BY-SA 4.0 |
Added outputs of requested commands
|
| Aug 9, 2019 at 11:12 | answer | added | Geoff Nixon | timeline score: 2 | |
| Aug 6, 2019 at 13:58 | history | edited | Jesse P. | CC BY-SA 4.0 |
added 119 characters in body
|
| Aug 6, 2019 at 13:56 | comment | added | Jesse P. | @benwiggy I've tried that. This problem affects whichever location I'm on at the time. If I were using static DNS IP addresses at all times, in each physical location, that would be a workaround, but I'm not (for numerous reasons, such as that would prevent me from being able to connect/disconnect from various networks without also having to worry about which DNS servers I'm using and whether or not they're allowed through the edge router/firewall, etc. | |
| Aug 6, 2019 at 13:48 | comment | added | benwiggy | Would using "Locations" help, by having different sets of Network prefs for home, office, and Elsewhere...? | |
| S Aug 6, 2019 at 13:47 | history | suggested | ruohola |
added a tag
|
|
| Aug 6, 2019 at 13:43 | review | Suggested edits | |||
| S Aug 6, 2019 at 13:47 | |||||
| S Aug 6, 2019 at 13:23 | history | bounty started | Jesse P. | ||
| S Aug 6, 2019 at 13:23 | history | notice added | Jesse P. | Draw attention | |
| Jul 24, 2019 at 22:37 | comment | added | Jesse P. | I deleted all of the interfaces listed under Network Preferences, and re-added them, but that didn't help anything | |
| Jul 24, 2019 at 20:47 | comment | added | Jesse P. | @historystamp Public DNS at work is not a viable solution for numerous reasons, nor is it a solution to the actual issue. | |
| Jul 24, 2019 at 20:45 | comment | added | Jesse P. |
@historystamp No, it wouldn't hurt anything, and I understand the definition of "bug". On the odd chance you're correct that it's related, I cleared the cache via sudo dscacheutil -flushcache;sudo killall -HUP mDNSResponder. And, no, it didn't resolve the bug.
|
|
| Jul 24, 2019 at 20:07 | comment | added | historystamp | Have you thought about setting a static address? 8.8.8.8 and 8.8.4.4 are goggles. Works well for me. Work might not like it. | |
| Jul 24, 2019 at 20:05 | comment | added | historystamp | Would resetting the DNS cache cause you some problem? No. Try it. Bugs can be weird. | |
| Jul 24, 2019 at 17:32 | history | edited | Jesse P. | CC BY-SA 4.0 |
added 157 characters in body
|
| Jul 24, 2019 at 15:33 | history | edited | Jesse P. | CC BY-SA 4.0 |
added 347 characters in body
|
| Jul 24, 2019 at 15:21 | comment | added | Jesse P. | @MelvinJefferson That is not relevant to this issue. That would be a solution to an IP address or FQDN resolving incorrectly or to an outdated record. I don't have an issue with resolution (other than macOS trying to use DNS servers because they are being statically set instead of dynamically, that are now unreachable because I'm no longer on the work or home network). | |
| Jul 24, 2019 at 14:59 | comment | added | Melvin Jefferson | Have you tried resetting your DNS cache to ensure macOS is using the new DNS server’s records and not cached results from a previous DNS server? | |
| Jul 24, 2019 at 14:42 | comment | added | Jesse P. | @MelvinJefferson At work, DHCP assigns 192.168.6.97, and 192.168.6.96; at home, DHCP assigns multiple public DNS servers (such as 1.1.1.1, 1.0.0.1, 75.75.75.75, etc). Obviously that will change if I go to another location (like a coffee shop or hotel). Those assignments, when provided by DHCP, are shown in the Network Preferences/Advanced/DNS tab but are grayed out (to signify they are dynamic). When this bug happens, those addresses are instead shown in black (statically set) and the preferences.plist file also shows they are static rather than saying "DHCP". | |
| Jul 24, 2019 at 14:38 | comment | added | Melvin Jefferson | What DNS server addresses do you have? | |
| Jul 24, 2019 at 14:32 | history | edited | Jesse P. | CC BY-SA 4.0 |
added 652 characters in body
|
| Jul 24, 2019 at 13:58 | history | asked | Jesse P. | CC BY-SA 4.0 |