I just replaced an older R-Pi with a new R-Pi-v2. In the process I assigned (reserved) a new IP Address (so I could have both systems running for a while) and then moved all my apps to the new hardware and updated my services links.  After testing I removed the old hardware completely, but for consistency I kept the old name for the new system.

I.e. wb6tae-svcs.local.mesh was 10.0.0.1 and is now 10.0.0.2

After rebooting my node, all works well locally. But, none of the other nodes in our mesh see the new address. They still resolve wb6tae-svcs.local.mesh to 10.0.0.1.

So, my question: Is there a way too force a network wide update of the DNS data or do we have to resort to rebooting every nice on the mesh?

I have confirmed with Conrad that there is a bug in OLSR and a report has been filed. 

Conrad notes that until the issue has been addressed the best way to force an update to go out would be to turn off the node advertising the details for around 5-10 minutes (gives the rest of the network time to purge the details) and then power it back up.