1

I have some devices on a network and an administration tool that relies on bonjour for device discovery. The devices are set to use DHCP. Example scenario as follows (let's assume really short DHCP leases, and ICMP echo response available)

Initially, one device (DeviceA.local) gets 192.168.1.1 and another (DeviceB.local) gets 192.168.1.2.

I then ping both devices by name and it resolves correctly.

Then I unplug DeviceA.local from network and plug it back in. DeviceA.local now gets assigned 192.168.1.3. I'm fairly certain DeviceA.local gets that IP by checking arp cache (arp -a) and comparing MAC address.

However, when I ping DeviceA.local, it resolves to 192.168.1.1 instead of 192.168.1.3.

This is bonjour service running on Windows 7. I've tried stopping and then starting bonjour service but it doesn't clear the situation. So my questions are:

  • Does bonjour cache resolved hostname-IP mapping somewhere? If so, where?
  • How do I clear the cache and force rediscovery?
Improve this question
2
  • Normally "rediscovery" is forced by the device re-announcing itself. Can you check with Wireshark whether Bonjour (mDNSResponder) is at least sending queries? Can you try the low-level dns-sd tool as well? (It talks to Bonjour directly, while ping goes through Winsock instead.)
    – grawity_u1686
    Commented Jul 8, 2016 at 8:55
  • @grawity Thanks for the suggestion, howere oops... turns out one of the device failed to switch back to DHCP and was still stuck with a static IP (that does conflict for testing purposes). =) Would still like to know the answers to my two questions though, thanks.
    – hg lim
    Commented Jul 11, 2016 at 13:32

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .