hostname ubo-xx.local is not propagated and recognized sometimes

[zytegalaxy]

Happening on V1.0.0.

I believe we addressed this issue previous which was caused by race condition during the first-time boot: if the unique hostname ubo-xx.local was generated with delay (since it is generated during boot time based on device serial number), it did not properly propagate to the router. Usually this gets addressed after a restart.

This is however still happening sometime and we need to have a recovery mechanism for it.

➜  ~ ping ubo-4g.local
ping: cannot resolve ubo-4g.local: Unknown host

➜  ~ ping 192.168.1.222
PING 192.168.1.222 (192.168.1.222): 56 data bytes
64 bytes from 192.168.1.222: icmp_seq=0 ttl=64 time=7.841 ms
64 bytes from 192.168.1.222: icmp_seq=1 ttl=64 time=2.497 ms
64 bytes from 192.168.1.222: icmp_seq=2 ttl=64 time=2.638 ms
^C
--- 192.168.1.222 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.497/4.325/7.841/2.487 ms