This afternoon, while we were testing robot stuff, I noticed that our Windows driverstation was able to resolve roborio-1418.local, and our OSX machines were not able to do so. This struck me as strange, as I hadn't had problems with resolving the address in the past.
However, tonight while looking around for other things, I found this message in the logfile '/var/log/messages':
Code:
Jan 10 21:43:38 roboRIO-1418 nimDNSResponder: Local Hostname roboRIO-1418.local already in use; will try roboRIO-1450.local instead
After seeing this, I decided to look at my local mDNS settings, and lo and behold I found my roborio as 'roboRIO-1450.local' instead! I suspect there's a bug in the NI mdns responder.. or at least some unanticipated behavior. Any thoughts?