I'm going to be offline for the next 2 hours.
This is not the recommended setup. Let your hubs use DHCP to gain their network configuration. And then set DHCP reservations on your router for each hub.
1 Like
May be a wording issue, but I think he may have meant that he set DHCP reservations on the router? Not uncommon for folks to refer to them as "fixed."
2 Likes
Makes sense. Then @John-Celek needs to ensure that their router is providing a valid list of DNS servers to the hub. Because the DNS server currently provided via DHCP configuration is returning an incorrect address of 172.16.1.1 for FQDNs.
2 Likes
I tried one more idea today before leaving the site. I took an old C7, did a "soft reset" on it and installed it. The system came up and I was able to register it and configure it with the web backup. This again, makes me think there is something wrong with the C8. If so, this would be the 3rd C8 I have had problems/failure with. My next test will be to use the C8 I have running at my home installation. I plan to replace that unit with a C8 Pro this week.
FWIW, the data you've posted clearly indicates a network misconfiguration on your C-8. There's no indication of any hardware issues.
2 Likes
Hi Salyar, I have looked at every item under "Network Setup" they are all blank. I have done the network reset by pushing the button on the back of the C8, I have done a soft reset. The configuration of the C8 that does not work and the C8 that is working on the network is identical for everything I can see. You might be right, but I don't know where else to look or what else to do to resolve this C8 network misconfiguration.
I don't see it mentioned anywhere above... have you tried setting a static IP with known good public DNS servers on the C8?
I had a different DNS issue on my C8 Pro. It loses the ability to look up local hostnames after it renews it's DHCP lease. It's fine on the initial connection, but after the lease expires it can only look up public IPs. I had to set it to static IP to get it to work. My C7 is fine on DHCP. That's not the same issue you're having, but it shows there might be some differences between the hubs when it comes to DHCP and DNS.
The issue may not be on the hub itself, could be on your LAN. If you have any sort of firewall of VLAN setup you possibly made holes for the other hubs and need to do the same for the new one?
Given that FQDNs like www.hubitat.com are resolved to a private IP address (172.16.1.1), if I had to guess, the OP has a DNS blocker/redirector on their LAN. Something like a Pi-Hole.
3 Likes
First, thank you all for your comments and suggestions!! Let me try to give a clearer picture of my setup. I have two hub installations: Home & Cabin
Home: C8, 146 devices, 4 Hubduinos, 74 WebCore pistons
Cabin: C8, two C7s, 216 devices, 7 Hubduinos, 100 WebCore pistons
I started with C5s migrating up to C8s.
LAN configuration: router does a map of MAC to an IP. No other router changes. No "pin holes" in the firewall. Hubitat's "Network Setup" tab is unchanged from default. I have not used this tab.
Overall, the systems runs. I had a spare C8 as two of my initial C8's failed. I tried to replace one of the C7 with my backup C8 but have not been able to. I have a C8 Pro which I'm going to replace my home C8 with today. I am then going to take my home C8 and try again to replace one of my C7's at the Cabin later this week or next as I know my home C8 works.
With all that being said, there still could be a C8 DNS "sensitivity" that I don't understand. Unless I can find where to look and exactly what to change, this is a C8 failure to me (based on my ignorance).
You can manually set the DNS on the hub in the network settings, overriding the DHCP settings. You can do that without setting a full blown static IP.
Maybe just try it like the example as a test?
Then you could go to the ping test and try to ping again, see what IP it resolves to now.
3 Likes
Did you read the Hubitat documentation on Network Setup that I linked to earlier:
I will try overriding the DNS settings. Any thoughts on why this is not an issue with my two working C8?
Something on your network most likely. The hub is getting some sort of a DNS from DHCP, and it is resolving, but to an internal LAN IP (which responds to ping). As suggested, seems like some sort of DNS blocker and it is just resolving everything to the same IP to "block" them.
1 Like
Or an overly zealous network provider ...... but this is way less likely.
I have returned to my cabin. I have implemented the recommended DNS Override settings in my backup C8 and then again tried to replace one of my C7's. Still did not work.
Next, I replace my main hub (C8) with a C8 Pro. That process worked. I then took the replaced C8 and used it to replace my C7. That worked with no changes to the network DNS settings. At this point, I view my backup C8 as defective.
I want to thank everyone for your time and great suggestions on this issue!!
I view this issue as closed.
3 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
