09-12-2019, 08:15 AM
Just chiming in here.
It is not moode causing this but a mis-configuration of the network/Pi-Hole or something that has been installed alongside Moode on the same IP address (maybe duplicate IP).
A suggestion:
Set the Moode PI to DHCP and see if you get the same result
Some Questions:
1) Is your router a Linksys EA7300 Max-Stream?
2) How is your PI connected (Cable or Wireless)?
I am guessing that you have the router mentioned and it is connected via wireless.
The problem is most likely you are using the external linksys domain on your internal network and since PI-Hole is you DNS server (and not the router) it will try and resolve externally. Your equipment (and the Moode PI would do this too) is probably doing a standard broadcast request to all devices on your network (standard operations on a network), and because you have an external domain running on a local network (internal to your network), the DNS server (PI-Hole) will forward the packet out from the internal network to external network, rather than resolving locally.
You need to change the domain on your DNS server and your DHCP server (usually in a home setup these are the same) to something as simple as HEMIRICK or HEMIRICK.LOCAL or some other name not associated with an external address that is in use now.
I saw you mentioned you have this in you DNS:
my etc/hosts file includes a line ea7300router 192.168.1.1 and that you say "When I ping ea73000router it works fine."
But, that is not what is being looked for for resolving. A quick fix is to put ea7300.home.linksys.com entry and point this to 192.168.1.1
The proper fix though is to fix the domain name of your internal network.
If you used a wizard to configure the router, then it would have picked ea7300.home.linksys.com.
As Tim mentioned, this isn't really the place for Network Support and how fix the settings, but I don't mind answer a few questions provided Tim is OK with this thread continuing.
Regards,
Rob
It is not moode causing this but a mis-configuration of the network/Pi-Hole or something that has been installed alongside Moode on the same IP address (maybe duplicate IP).
A suggestion:
Set the Moode PI to DHCP and see if you get the same result
Some Questions:
1) Is your router a Linksys EA7300 Max-Stream?
2) How is your PI connected (Cable or Wireless)?
I am guessing that you have the router mentioned and it is connected via wireless.
The problem is most likely you are using the external linksys domain on your internal network and since PI-Hole is you DNS server (and not the router) it will try and resolve externally. Your equipment (and the Moode PI would do this too) is probably doing a standard broadcast request to all devices on your network (standard operations on a network), and because you have an external domain running on a local network (internal to your network), the DNS server (PI-Hole) will forward the packet out from the internal network to external network, rather than resolving locally.
You need to change the domain on your DNS server and your DHCP server (usually in a home setup these are the same) to something as simple as HEMIRICK or HEMIRICK.LOCAL or some other name not associated with an external address that is in use now.
I saw you mentioned you have this in you DNS:
my etc/hosts file includes a line ea7300router 192.168.1.1 and that you say "When I ping ea73000router it works fine."
But, that is not what is being looked for for resolving. A quick fix is to put ea7300.home.linksys.com entry and point this to 192.168.1.1
The proper fix though is to fix the domain name of your internal network.
If you used a wizard to configure the router, then it would have picked ea7300.home.linksys.com.
As Tim mentioned, this isn't really the place for Network Support and how fix the settings, but I don't mind answer a few questions provided Tim is OK with this thread continuing.
Regards,
Rob
Pi 4B 2GB, HiFi Berry Digi+, Original 7" Raspberry Pi Screen, Ethernet Connected, Sandisk Ultra10 SD card, 5amp power supply (Drives the PI and Screen separately) streaming audio via NFS shares from QNAP NAS.
