Timeline for macOS keeps reverting to static DNS IP addresses
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2019 at 18:50 | review | Low quality posts | |||
| Aug 29, 2019 at 21:35 | |||||
| Aug 13, 2019 at 14:43 | comment | added | Prado | @JesseP. Yes, I have very good news and I am sure it will be essencial for you to find and fix this problem, I will post it as an answer here in about 1 hour. | |
| Aug 12, 2019 at 13:24 | comment | added | Jesse P. | @Prado Any luck with your testing? I'm close to reinstalling macOS to see if that fixes the issue, but I don't want to have to go through that headache yet. | |
| S Aug 11, 2019 at 1:32 | history | mod moved comments to chat | |||
| S Aug 11, 2019 at 1:32 | comment | added | Monomeeth♦ | Comments are not for extended discussion; this conversation has been moved to chat. | |
| Aug 11, 2019 at 0:14 | comment | added | Jesse P. |
@Prado So, at home, my search domain (DNS suffix) is not customizable in my router. It's not statically set on my laptop, either. I added the resolv.conf output while at home, to the original post so you can see the difference. Also, my exact macOS version is 10.14.6 (18G87). As you can see, it's NOT anything .local so, that shoots that theory out of the water (unless I missed something).
|
|
| Aug 10, 2019 at 22:55 | comment | added | Prado | Thank you @JesseP. I am putting effort on it and later I post more updates here on this topic | |
| Aug 10, 2019 at 22:37 | comment | added | Jesse P. | @Prado Great. It's 10.14.6 with all of the current public updates. I can't look at the moment. I can't change my domain suffix at work but I can at home to test as well, if I even use .local at all (I can't recall at the moment) | |
| Aug 10, 2019 at 22:21 | comment | added | Prado | What is the exact MacOS version number that you are using? I have a good setup here and I will try to replicate your scenario and see if I can prove my theory | |
| Aug 10, 2019 at 22:15 | comment | added | Prado | Yes, it is for sure relatad to some new issue about the macOS update, I am assuming it from the beginning, because you were very clear on telling this happend after the update. :) | |
| Aug 10, 2019 at 22:14 | comment | added | Prado |
Considering that it changes depending on the connection you're using, and considering that devices using a .local domain can auto-configure itself and send parameters replicating the configuration to others, a conflict on this mixed scenario could be making you macOS accept messages from other mDNS device and assign a parameter (such the DNS) to interface en0 because it is configured with .local replacing the DNS server received via DHCP. That is what I am suggesting that could be happening.
|
|
| Aug 10, 2019 at 22:07 | comment | added | Jesse P. | @Prado Unless that became an issue in the last 2 macOS updates, that's not the issue. Also, that wouldn't have anything to do with the issue of the DNS server IP addresses themselves - the problems caused by that are all related to problems with improper resolution and such (at least that I can find). Can you provide any more "proof" to back your theory that it causes issues such as mine? | |
| Aug 10, 2019 at 22:00 | comment | added | Prado |
@JesseP. I know they can be even real TLDs; it can be almost anything, except .local which is reserved for mDNS in RFC 6762. Microsoft, Cisco, Apple, Ubuntu, since years reported DNS conflicts/misconfiguration if the .local was assigned to local/internal network.There is more info at en.wikipedia.org/wiki/.local with references from vendors explicitly warning to never use .local along with misconfiguration problems that can happen. Considering your situation is auto-misconfiguring itself I think it can be related. I'm just trying to add something positive here to help solving it.
|
|
| Aug 10, 2019 at 20:48 | comment | added | Jesse P. | @Prado That has nothing to do with the issue. The search domain (DNS suffix) is solely for short name lookup requests, to assume the FQDN. It is dynamically set via DHCP, not statically set, and is there on ANY connection (including your own). It changes depending on the connection you're using, and can be literally anything (such as .internal, .lan, even real TLDs such as .com, .net, etc.). | |
| Aug 10, 2019 at 20:38 | comment | added | Prado |
There is something on your results, and may be the cause. The search domain is set as "TCC.local" when it should not include .local on it. Where this setting coming from? My guess: from the DHCP server (?). MacOS cannot have a .local domain assigned via DHCP, because it already uses this special domain for mDNS queries (Bonjour) Multicast DNS which has capabilities of auto configuration, and a behaviour is to ignore DNS config received by DHCP servers. It looks like a conflict situation and it is making your DNS server changes. @JesseP. Can you change that local to any other word?
|
|
| Aug 9, 2019 at 13:30 | comment | added | Jesse P. | The outputs have been added to the question. The "networksetup -getdnsservers" command outputs were all empty, so I left that out. | |
| Aug 9, 2019 at 11:12 | history | answered | Geoff Nixon | CC BY-SA 4.0 |