LFMc Posted July 25, 2019 Posted July 25, 2019 While on vacation, i started getting a "no isy found" or similar error message when trying to login to my ISY while on the road using the ISY portal. But, I was able to open up a VPN PPTP tunnel to my router and connect directly to the ISY from remote. When arriving home, I realized my server that runs my DHCP server had crashed and DHCP was not working. But my ISY has a fixed private IP address and works without access to DHCP. Upon restarting the server with DHCP, it now responds to the portal connection. As a rule of thumb, all critical equipment I have has a fixed, private IP address. I am a bit confused as to what caused the portal to fail, because without DHCP, I would think the problem would be reversed and my remote device using the VPN wouldn't get a DHCP private IP assigned to it and the portal should continue to work directly. The VPN is being handled by my Mikrotik router. Also the down DHCP server was also handling internal DNS. Thoughts? I would like to make sure my ISY portal access is independent of most other network services other than the internet, router and ISY being up.
bmercier Posted July 25, 2019 Posted July 25, 2019 I believe the problem is the DNS that was not working.The ISY tries to connect to ISY Portal, but if DNS is not working or misconfigured, it won’t connect.BenoitSent from my iPhone using Tapatalk
LFMc Posted July 25, 2019 Author Posted July 25, 2019 Thanks, I wasn't considering the ISY going outbound to the portal. Good point. It's DNS setting was to the internal server, so I changed it to an external DNS. I can't imagine that not having access to internal DNS would cause it any issues, but I could be wrong. It would be nice if the ISY had a secondary (fail over) DNS setting like PC's have. Leon
paulbates Posted July 25, 2019 Posted July 25, 2019 2 minutes ago, LFMc said: It would be nice if the ISY had a secondary (fail over) DNS setting like PC's have. Typically the router provides the secondary dns function. I’m trying to remember the last time I had a router that didn’t.
LFMc Posted July 25, 2019 Author Posted July 25, 2019 I understand, but my ISY DNS wasn't pointed to my router, just a down server. I am in the process of moving dns and dhcp services to the router as I simplify my network.
pmarcos Posted December 28, 2020 Posted December 28, 2020 I just ran into this lack of secondary DNS support as well when I noticed that my Ecolink Z-Wave device seemed to have stopped responding. I thought it was maybe a dead battery (it wasn't), but then I realized that a month or two ago I had been fiddling with pointing my router at a local DNS server running AdGuard. I eventually ditched that but forgot to set the primary DNS on my router back to 1.1.1.1. Everything else on my home network seemed to fall back to the secondary DNS with zero problem, but my ISY effectively went offline. Once I went and tested the email notifications I have set up I found the DNS errors showing up and that reminded me about the router DNS setting. Fixing that up cleared everything up. My ISY does get its config via DHCP from my router, but obviously isn't handling a down primary DNS server gracefully. I'd consider that a bug. 1
Recommended Posts