1

I'm running OS X 10.10.1 and keep getting thousands of lines like the following in the system console log.

12/16/14 2:57:02.937 PM dnsextd[9384]: ConnectToServer - 10 failed attempts.  Aborting.
12/16/14 2:57:02.937 PM dnsextd[9384]: UpdateSRV: ConnectToServer failed
12/16/14 2:57:02.937 PM dnsextd[9384]: main: SetUpdateSRV - Socket is not connected
12/16/14 2:57:02.938 PM com.apple.xpc.launchd[1]: (com.apple.dnsextd[9384]) **Service exited with abnormal code: 1**
12/16/14 2:57:02.945 PM dnsextd[9447]: dnsextd starting
12/16/14 2:57:02.945 PM dnsextd[9447]: main: setrlimit - Invalid argument
12/16/14 2:57:02.945 PM dnsextd[9447]: Using default file descriptor resource limit
12/16/14 2:57:02.945 PM dnsextd[9447]: started_via_launchd
12/16/14 2:57:02.946 PM dnsextd[9447]: ConnectToServer: connect - Socket is not connected
12/16/14 2:57:02.946 PM dnsextd[9447]: ConnectToServer - retrying connection
12/16/14 2:57:03.809 PM dnsextd[9447]: ConnectToServer: connect - Socket is not connected
12/16/14 2:57:03.809 PM dnsextd[9447]: ConnectToServer - retrying connection
12/16/14 2:57:05.447 PM dnsextd[9447]: ConnectToServer: connect - Socket is not connected
12/16/14 2:57:05.448 PM dnsextd[9447]: ConnectToServer - retrying connection

It seems dnsextd is always exiting with error code 1. Has anybody had the same issue? Any ideas on how to fix this? I've tried rebooting, stopping/starting dnsextd from launchctl, but had no luck.

8
  • dnsextd is intended for certain DNS query functions. See man dnsextd in Terminal. Have you checked that your DNS entries in your network settings are valid and reachable?
    – douggro
    Dec 16, 2014 at 15:39
  • Yes, this happens on at least 5 different networks and happens all the time.
    – Brethil
    Dec 16, 2014 at 15:55
  • I'm somewhat stumped. It may be related to some Bonjour activity that's failing for whatever reason.
    – douggro
    Dec 16, 2014 at 16:16
  • @Brethil Do you use any DDNS services like DynDNS or is your Mac member of an Active Directory domain?
    – klanomath
    Jan 9, 2015 at 16:21
  • I'm not using any DDNS services. I'm not part of any Active Directory Domain that I know of. How would I go about in checking this?
    – Brethil
    Jan 10, 2015 at 11:59

1 Answer 1

1
+50

As the man page says "dnsextd is a daemon invoked at boot time, running alongside BIND 9, to implement two EDNS0 extensions to the standard DNS protocol."

My guess is that you are getting these errors because dnsextd is running on your Mac and trying to talk to BIND, but BIND is not running. You can check this by running the following command. If it comes back blank, then BIND is not running.

pgrep named

I think the solution to this problem is to just turn dnsextd off using the below command. Unless you are running this Mac as a DNS server for other devices then I'm not sure why you'd need either running.

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.dnsextd.plist
2
  • Indeed BIND is not running, pgrep named returns nothing. My Mac isn't really being used as server (apart from file sharing with AFP and screen sharing with ARD/VNC), but isn't dnsextd part of the default daemons?
    – Brethil
    Jan 16, 2015 at 2:59
  • 1
    Nope, it just runs as an addition to BIND. And BIND doesn't run by default either. Jan 16, 2015 at 6:28

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .