edited tags

Link

edited Dec 14 at 20:51

nohillside ♦

104.5k
42
222
275

How to fix DNS not resolving - brand new Mac - Sequoiain browsers and Terminal

edited body; edited tags

Source Link

edited Dec 14 at 19:25

h4ckNinja

135
5

me@MacBook-Pro ~ % dig storage.home.lan

; <<>> DiG 9.10.6 <<>> storage.home.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.home.lan.      IN  A

;; ANSWER SECTION:
storage.home.lan.   0   IN  A   172.16.10.5

;; Query 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

me@MacBook-Pro ~ % dig storage.home.lan

; <<>> DiG 9.10.6 <<>> storage.home.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.home.lan.      IN  A

;; ANSWER SECTION:
storage.home.lan.   0   IN  A   172.16.10.5

;; Query 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

me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

I've narrowed the problem down to MacOSmacOS is preferring the public DNS server 1.1.1.1 for all DNS queries except for oddly dig. Once I set the DNS to just the internal DNS server, things work fine. I wouldn't consider this a fix per se as I should be able to use an external DNS server should the internal one fail, but this addressed it.

me@MacBook-Pro ~ % dig storage.home.lan

; <<>> DiG 9.10.6 <<>> storage.home.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.home.lan.      IN  A

;; ANSWER SECTION:
storage.home.lan.   0   IN  A   172.16.10.5

;; Query 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

me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

I've narrowed the problem down to MacOS is preferring the public DNS server 1.1.1.1 for all DNS queries except for oddly dig. Once I set the DNS to just the internal DNS server, things work fine. I wouldn't consider this a fix per se as I should be able to use an external DNS server should the internal one fail, but this addressed it.

me@MacBook-Pro ~ % dig storage.home.lan

; <<>> DiG 9.10.6 <<>> storage.home.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.home.lan.      IN  A

;; ANSWER SECTION:
storage.home.lan.   0   IN  A   172.16.10.5

;; Query 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

me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

I've narrowed the problem down to macOS is preferring the public DNS server 1.1.1.1 for all DNS queries except for oddly dig. Once I set the DNS to just the internal DNS server, things work fine. I wouldn't consider this a fix per se as I should be able to use an external DNS server should the internal one fail, but this addressed it.

terminal mac macos network launchd dns

Rollback to Revision 2

Source Link

edited Dec 14 at 19:23

h4ckNinja

135
5

Why is DNS not resolving on- brand new MacBook Pro running macOSMac - Sequoia?

Brand new MacBook Pro - unboxed just a few minutes ago. It's running macOS Sequoia. DNS to external works just fine, and my other devices, including an iPhone and an iPad, work just fine with internal DNS.

I'm able to perform a digdig for internal resources and get the expected results, as seen here:

me@MacBook-Pro ~ % dig storage.home.lan

; <<>> DiG 9.10.6 <<>> storage.home.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.home.lan.      IN  A

;; ANSWER SECTION:
storage.home.lan.   0   IN  A   172.16.10.5

;; Query 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

me@MacBook-Pro ~ % dig storage.home.lan

; <<>> DiG 9.10.6 <<>> storage.home.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.home.lan.      IN  A

;; ANSWER SECTION:
storage.home.lan.   0   IN  A   172.16.10.5

;; Query 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

me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

I've rebooted for funsies but that didn't change anything either.

Edit: Just to be abundantly clear - this also affects web browsers. It is not just a terminal problem.

I’ve rebootedI've narrowed the problem down to MacOS is preferring the public DNS server 1.1.1.1 for funsies but that didn’tall DNS queries except for oddly dig. Once I set the DNS to just the internal DNS server, things work fine. I wouldn't consider this a fix anythingper se as I should be able to use an external DNS server should the internal one fail, but this addressed it.

Why is DNS not resolving on brand new MacBook Pro running macOS Sequoia?

Brand new MacBook Pro - unboxed just a few minutes ago. It's running macOS Sequoia. DNS to external works just fine, and my other devices, including an iPhone and an iPad, work just fine with internal DNS.

I'm able to perform a dig for internal resources and get the expected results, as seen here:

me@MacBook-Pro ~ % dig storage.home.lan

; <<>> DiG 9.10.6 <<>> storage.home.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.home.lan.      IN  A

;; ANSWER SECTION:
storage.home.lan.   0   IN  A   172.16.10.5

;; Query 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

me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

Edit: Just to be abundantly clear - this also affects web browsers. It is not just a terminal problem.

I’ve rebooted for funsies but that didn’t fix anything.

DNS not resolving - brand new Mac - Sequoia

Brand new MacBook Pro - unboxed just a few minutes ago. It's running Sequoia. DNS to external works just fine, and my other devices, including an iPhone and an iPad, work just fine with internal DNS.

I'm able to perform a dig for internal resources and get the expected results, as seen here:

me@MacBook-Pro ~ % dig storage.home.lan

; <<>> DiG 9.10.6 <<>> storage.home.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55954
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;storage.home.lan.      IN  A

;; ANSWER SECTION:
storage.home.lan.   0   IN  A   172.16.10.5

;; Query 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

me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Password:
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
me@MacBook-Pro ~ % sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.

I've rebooted for funsies but that didn't change anything either.

Edit: Just to be abundantly clear - this also affects web browsers. It is not just a terminal problem.

I've narrowed the problem down to MacOS is preferring the public DNS server 1.1.1.1 for all DNS queries except for oddly dig. Once I set the DNS to just the internal DNS server, things work fine. I wouldn't consider this a fix per se as I should be able to use an external DNS server should the internal one fail, but this addressed it.