Official moOde 7.6.0 support thread

[TheOldPresbyope]

Prolly due to the command used by moOde to parse out the DNS address. It gets the address from the 3rd line in the /etc/resolv.conf file. Maybe when there are both primary and secondary addresses in resolve.conf the secondary address is in the 3rd line. 

See below.

Code:

pi@rp1:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain home
nameserver 192.168.1.1

pi@rp1:~ $ cat /etc/resolv.conf | awk 'NR==3 {print $2}'
192.168.1.1
pi@rp1:~ $

Errm, resolv.conf can vary. 

For example, for a moOde player configured for DHCP with Xfinity/Comcast as my ISP and no local DNS service on the router (e.g., all comcast nameservers)

Code:

# Generated by resolvconf
domain hsd1.md.comcast.net
nameserver 75.75.75.75
nameserver 75.75.76.76
nameserver 2001:558:feed::1
nameserver 2001:558:feed::2
nameserver <an IPv6 address within my subnet>

When I reconfigure the player for static IP with Google as primary (8.8.8.8) and CloudFlare as secondary (1.1.1.1) nameservers, the resolv.conf file reads

Code:

# Generated by resolvconf
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 2001:558:feed::1
nameserver 2001:558:feed::2
nameserver <an IPv6 address within my subnet>

e.g., no "domain" line.

I think it would be better for worker.php to search explicitly for the first line beginning with "nameserver". I'll post an issue to the repo.

Regards,
Kent