09-12-2019, 02:15 AM
@HemiRick
Sorry for my confusion, I was trying to read the thread and write a post on my cell phone while sitting in a waiting room. I misread some IP numbers from Tim's post as being from you.
Bottom line: I believe you entered this FQDN while configuring moOde. (My guesses include during static IP config and or during the creation of a new source, since you said the router was a Samba server). If you don't know how you did or where it lives now, I'd suggest you just install a fresh copy of moOde and set its static IP config appropriately (using only dotted IP address notation).
---the rest of this is tangential to the above---
Out of curiosity driven by the thought I might find a Pi-hole useful in a future environment, I installed it this evening on a spare RPi.
For reasons that aren't relevant here, I can not disable DHCP service (which I have, however, restricted to handing out IPs in the range 192.168.1.100 to 192.168.1.200) on my ISP's router nor can I change its primary/secondary DNS providers. This means I can't test Pi-hole with my entire LAN depending on it.
Nevertheless, I just reconfigured moOde 6.2.0 on an RPi0W to use a static IP address (not relevant, but it's 192.168.1.21), to use the Pi-hole (configured to be 192.168.1.20) as its DNS server, and to use my ISP's router (192.168.1.1) as the gateway.
As I expected, this partial test "just works", in the sense that this particular moOde player is able to communicate with hosts out on the Internet using their FQDNs. The Pi-hole logs the DNS requests and filters them against its blacklists.
Of course this moOde player and other hosts on my LAN can communicate with each other only by using their IP addresses in this test because they don't share common DNS.
I don't see in all this where I would ever need to enter either the hostname or the FQDN of my router.
Regards,
Kent
Sorry for my confusion, I was trying to read the thread and write a post on my cell phone while sitting in a waiting room. I misread some IP numbers from Tim's post as being from you.
Bottom line: I believe you entered this FQDN while configuring moOde. (My guesses include during static IP config and or during the creation of a new source, since you said the router was a Samba server). If you don't know how you did or where it lives now, I'd suggest you just install a fresh copy of moOde and set its static IP config appropriately (using only dotted IP address notation).
---the rest of this is tangential to the above---
Out of curiosity driven by the thought I might find a Pi-hole useful in a future environment, I installed it this evening on a spare RPi.
For reasons that aren't relevant here, I can not disable DHCP service (which I have, however, restricted to handing out IPs in the range 192.168.1.100 to 192.168.1.200) on my ISP's router nor can I change its primary/secondary DNS providers. This means I can't test Pi-hole with my entire LAN depending on it.
Nevertheless, I just reconfigured moOde 6.2.0 on an RPi0W to use a static IP address (not relevant, but it's 192.168.1.21), to use the Pi-hole (configured to be 192.168.1.20) as its DNS server, and to use my ISP's router (192.168.1.1) as the gateway.
As I expected, this partial test "just works", in the sense that this particular moOde player is able to communicate with hosts out on the Internet using their FQDNs. The Pi-hole logs the DNS requests and filters them against its blacklists.
Of course this moOde player and other hosts on my LAN can communicate with each other only by using their IP addresses in this test because they don't share common DNS.
I don't see in all this where I would ever need to enter either the hostname or the FQDN of my router.
Regards,
Kent
