1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

mDNS name drifting on ZenWiFi XT8

Discussion in 'ASUSWRT - Official' started by toaruScar, May 22, 2020 at 4:47 PM.

  1. toaruScar

    toaruScar New Around Here

    Joined:
    Tuesday
    Messages:
    7
    I've got this issue where the mDNS name of my router keeps changing or -should I say- increasing.

    What do I mean by "mDNS name"?
    One of my router's hostname is set to `ZenWiFi_XT8-Main`, so it's reachable at `zenwifi_xt8-main.local`, and this ".local" name is the mDNS name.

    What is the problem?
    As time goes by its mDNS name will gain a suffix like "-2" or "-3" and it keeps increasing slowly, so in order to reach it I need to access `zenwifi_xt8-main-2.local` and so on. (However the hostname `ZenWiFi_XT8-Main` is still accessible thanks to NetBIOS).

    Also the following is in the log:
    Code:
    avahi-daemon[1924]: Host name conflict, retrying with ZenWiFi_XT8-MaBedroom-2
    avahi-daemon[1924]: Host name conflict, retrying with ZenWiFi_XT8-MaBedroom-3
    avahi-daemon[1924]: Host name conflict, retrying with ZenWiFi_XT8-MaBedroom-4
    This keeps going on until the suffix reaches "-14".

    Using a Bonjour browser, I can see that at this moment 2 of my 4 ZenWiFi XT8 are having this issue: the "Main" one and the "MaBedroom" one.
    [​IMG]

    This is problematic for me because I use the router as a Time Machine backup server, and if the mDNS name changes, my Macs can't backup to the router.

    Scope of this problem
    This problem only occures on asus routers (currently on 3.0.0.4.386_25224-g3c383a4). Other devices in my LAN (including a printer, Macs running macOS Catalina, iOS devices running iOS 13.4) do not have this problem.


    Workaround
    One quick fix I can find is ssh into the router and run this command.
    Code:
    service restart_mdns
    Is there a way to fix this once and for all?