Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: Name resolution doesn't work, DHCP issue?
#1
Hi all, 
I need some help to fix an issue with the name resolution 

I use moode 8.1.2
I have initially set up the device in Germany, connected it to a Fritzbox router (German brand) and everything was working fine.
Now I moved the device incl. the moode installation into
the UK and connected it to a Virgin cable router.
I changed the country, timezone and keyboard layout in the settings.
However entering moode in the browser doesn't work, the name resolution seems not to be available or broken.
Access only works via IP address. 

In the moode config 
Address Assignment is set to DHCP
and DHCP v4 is also enabled in the Virgin Media router settings. 
Host name in moode (General config) is still set to "moode" and untouched. 

Any idea why the name resolution (putting "moode" in the browser) it is not working?
Reply
#2
Post the Network section of the moOde startup log.

Code:
moodeutl -l
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#3
Thanks Tim, here is the network section:

20220813 093445 worker: -- Network
20220813 093445 worker: --
20220813 093445 worker: eth0 adapter exists
20220813 093445 worker: eth0 y (GB)
20220813 093445 worker: wlan0 connected SSID is (VM0739653)
20220813 093445 worker: IP addr (192.168.0.99)
20220813 093445 worker: Netmask (255.255.255.0)
20220813 093445 worker: Gateway (192.168.0.1)
20220813 093445 worker: Pri DNS (194.168.4.100)
20220813 093445 worker: Domain  ()
20220813 093445 worker: wlan0 power save disabled
20220813 093445 worker: --
Reply
#4
The name server configured for the client by the Router is

Code:
0220813 093445 worker: Pri DNS (194.168.4.100)

The Router is responsible for handling name queries from the client to this DNS. When the name "moode" is submitted  the Router should ask 194.168.4.100 for the IP address and if it fails to resolve then it should look in its table of local (LAN) addresses and return the IP address for "moode" if it exists.

It seems as if the Router is not doing LAN address lookup when primary DNS lookup fails. The only alternatives in this case are to use host name moode.local or IP address.

There may also be Router settings that control how its DNS handles local lookup.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#5
@Gromit


Just to be clear, this is a problem only your ISP can resolve (pun intended Tongue) given the current values returned to a DHCP query. There’s not even a default DOMAIN defined.

Similar to your situation, my ISP-provided router does not resolve local hostnames. I use only mDNS (.local) addresses as a workaround and it works fine.

As Tim hints, I don’t suppose there’s an available setting in your Virgin router for the DNS server address it returns (currently 194.168.4.100)? If so, you could run a local DNS server and use its address in the router settings. 

G**gle is your friend here since there’s lots of HowTos out there on various DIY solutions. Pi-hole seems a very popular packaged solution these days but all the software components have been available in Linux distros for years. Even a moOde player could be pressed into service, but I wouldn’t recommend it for a variety of reasons.

Regards,
Kent

PS - my ISP has locked down all the settings I’d want to muck with. There’s alternative solutions but I don’t want the fuss and bother.
Reply
#6
Thank you both Tim and Kent for your support.

It basically means the ISP router is crap,
the possible settings are quite limited.

However as mentioned moode.local works fine and is sufficient as a workaround for me.

Again thanks for your support.
Reply


Forum Jump: