New MacBook Professional, unboxed only a few minutes in the past. You’re working Sequoia. Exterior DNS works tremendous and my different gadgets, together with an iPhone and iPad, work tremendous with inner DNS.
I run Pihole internally to get the advantages of advert blocking and likewise present an authoritative DNS server for the assorted purposes I run on my inner community.
I can carry out a seek for inner assets and get the anticipated outcomes, as seen right here:
me@MacBook-Professional ~ % dig storage.dwelling.lan
; <<>> DiG 9.10.6 <<>> storage.dwelling.lan
;; international choices: +cmd
;; Received reply:
;; ->>HEADER<<- opcode: QUERY, standing: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: model: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.dwelling.lan. IN A
;; ANSWER SECTION:
storage.dwelling.lan. 0 IN A 172.16.10.5
;; Question time: 4 msec
;; SERVER: 172.16.10.2#53(172.16.10.2)
;; WHEN: Thu Dec 12 19:58:25 MST 2024
;; MSG SIZE rcvd: 61
However making an attempt to SSH, use an online browser, or ping these inner assets fails. I’ve discovered DNS doesn’t resolve on Mac OS and DNS doesn’t resolve on Mac OS however the try to bounce Discovery and mDNS fails:
me@MacBook-Professional ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Enter/output error
Attempt working `launchctl bootout` as root for richer errors.
me@MacBook-Professional ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Enter/output error
Attempt working `launchctl bootstrap` as root for richer errors.
me@MacBook-Professional ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Enter/output error
Attempt working `launchctl bootout` as root for richer errors.
me@MacBook-Professional ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Enter/output error
Attempt working `launchctl bootstrap` as root for richer errors.
I rebooted for enjoyable, however that did not change something both.
Edit: Simply to be abundantly After all: this additionally impacts internet browsers. Is No only a terminal downside.
I’ve narrowed the issue all the way down to MacOS preferring the general public DNS server. 1.1.1.1 for all DNS queries besides unusually dig. As soon as I set DNS to solely the interior DNS server, every thing works tremendous. I would not contemplate this an answer per se, as you must be capable of use an exterior DNS server in case the interior one failed, however this fastened it.
