Mar 2 12:14:36 My-MacBook-Pro.local mDNSResponder: 18: Adding FD for uid 501 $ tail -f system.log | grep mDNSResponder Let’s turn on logging in the responder according to the man page. $ sudo launchctl load -w /System/Library/LaunchDaemons/ $ sudo launchctl unload -w /System/Library/LaunchDaemons/ I’ve tried clearing the cache, bouncing the DNS responder, and I know that the host and dig commands don’t go through the sameĬhannels as other commands. Tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 65535 bytes
Won’t even ask why ssh needs an MX record.) $ sudo tcpdump -i en0 -vnnt "udp port 53" Hangs for a while and eventually times out. They go out andĬorrect responses come back immediately! Yet, the ssh command still I tried tcpdump to see if the requests were going out. In case you’re wondering, the IP address is reachable from this laptopīut if you know anything about this problem then you’ll know that this Ssh: Could not resolve hostname : nodename nor servname provided, or not known
Resolved through public DNS but I’ve changed the domains for privacy. Through a Tunnelblick VPN have stopped working. I’m not aware of any updates to the OS or anything IĭNS works in general but certain private addresses that I can access This started sometime during the day on March 1, 2016. Given up for the moment after spending too much time on this issue. Out most of the time after a little bit of digging.
#Tunnelblick resolving domain name pro
DNS on my MacBook Pro has been a mystery to me.