DNSService error and self expanding console.log file

Question

Just like misskool, I had a problem with self-expanding console.log files. As suggested by roam, I erased the com.apple.iTunes.plist file to fix the issue. Unfortunately, 2 days after, the same problem started again. I noticed it happened soon after I tried (without success) to establish a mac OS 10.3.9 to mac OS 10.4.9 wireless network - either that or the re-activation of AppleTalk on my iBook. The error message in the console.log file is a repeated one-liner :
DNSServiceProcessResult() returned an error! -65537
The original advice from roam worked until I tried to network my two macs. In his idea, iTunes was the probable origin of the problem. Is it ?

Answer 1

The mDNS error message was associated with an iTunes update, though that is not to say it is caused by iTunes though it may well have. The error is from the mDNS service, a system wide network service, which looks for available services on the network.
I don't know what is causing this error but it has been known about since 2005, evidenced by this thread. It is a highly technical discussion,
http://lists.apple.com/archives/Bonjour-dev/2005/Jul/msg00023.html
which talks about the error occurring when two ethernet interfaces are active, but does not err when only with one. It is possible this observation is linked to your experience trying to network two Macs.
Click on the Next Threads on that page to read more.
Another thing to note is that the error code given is general and undescriptive, where one poster writes " Normally when you see that error it means that mDNSResponder (mdnsd) crashed." ... but there is no specific meaning given to the error code as to why it did.
So it's a bug but I cannot explain why it occurs or what role the iTunes update played in bringing it to the fore.
If it continues to be a problem with the same error message printing in the console, open Activity Monitor and mDNS should be active there and kill that mDNS Process.
As i have no iTunes updated, and do not want to try and create this error, I'll leave it up to you to try and determine some causes and effects regarding the renegade process of mDNS.