09-12-2019, 10:52 AM
(09-12-2019, 08:15 AM)rb0135 Wrote: 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).
Answer: There is nothing else using 130, this is the 1st time I've ever used this number on my network. Moode was 135 in the past and I 1st installed pihole on the same hardware, when I moved pihole to its own hardware, since all my other devices had been set to use 135 for DNS, it was just easier to change Moode's IP.
A suggestion:
Set the Moode PI to DHCP and see if you get the same result
Answer: I will try this in the future. Waiting for the etc/hosts change to see if it makes any diff.
Some Questions:
1) Is your router a Linksys EA7300 Max-Stream? YES
2) How is your PI connected (Cable or Wireless)? ETHERNET
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.
Answer: I'm using pihole as both DNS, and DHCP the domain is set to "lan"
A quick fix is to put ea7300.home.linksys.com entry and point this to 192.168.1.1
Answer: I've did this a few hours ago, and am waiting to see result.....so far no change.
The proper fix though is to fix the domain name of your internal network.
Answer: as mentioned previously it is lan, set in pihole, looking at the routers setup, its DHCP is turned off and according to it this is its info:
Current Router Time:
Thursday, 12 September 2019 05:48:00 (GMT -05:00)
Current Browser Time:
Thursday, 12 September 2019 05:48:01 (GMT -05:00)
Internet MAC Address:
24:F5:A2:00:AF:CE
Server Name:
AE7300router
Host Name:
AE7300router
Domain Name:
hsd1.tn.comcast.net.
