Eu alterei o nome do host no arquivo avahi-daemon.conf
em /etc/avahi
, de forma que o host-name=osmc
e ele não esteja completo. Quando eu faço um sudo systemctl status avahi-daemon -l
eu recebo o seguinte:
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled)
Active: active (running) since Fri 2016-03-18 23:21:31 GMT; 9h ago
Main PID: 1298 (avahi-daemon)
Status: "avahi-daemon 0.6.31 starting up."
CGroup: /system.slice/avahi-daemon.service
├─1298 avahi-daemon: running [osmc.local
└─1300 avahi-daemon: chroot helpe
Mar 18 23:21:31 osmc avahi-daemon[1298]: New relevant interface eth0.IPv4 for mDNS.
Mar 18 23:21:31 osmc avahi-daemon[1298]: Network interface enumeration completed.
Mar 18 23:21:31 osmc avahi-daemon[1298]: Registering new address record for 192.168.0.13 on eth0.IPv4.
Mar 18 23:21:31 osmc avahi-daemon[1298]: Registering HINFO record with values 'ARMV7L'/'LINUX'.
Mar 18 23:21:32 osmc avahi-daemon[1298]: Server startup complete. Host name is osmc.local. Local service cookie is 1330739464.
Mar 18 23:21:33 osmc avahi-daemon[1298]: Service "osmc" (/services/udisks.service) successfully established.
Mar 18 23:21:33 osmc avahi-daemon[1298]: Service "osmc" (/services/ssh.service) successfully established.
Mar 18 23:21:33 osmc avahi-daemon[1298]: Service "osmc" (/services/sftp.service) successfully established.
Mar 19 08:58:24 osmc avahi-daemon[1298]: Files changed, reloading.
Mar 19 08:58:52 osmc avahi-daemon[1298]: Files changed, reloading.
Eu posso ping -c 3 osmc.local
e obter 0% de perda. No entanto, quando tento acessar um serviço, por exemplo, nzbget ou transmissão por meio de um cromo no meu dispositivo Android, o DNS não pôde ser resolvido. Funciona bem no meu PC Ubuntu e no meu Chromebook, alguma ideia?
Tags dns android google-chrome avahi