Down then up then down....

[drprm1]

Was wondering about this 

Have domain through Dyndns and have what is called a “Health check” feature. Not quite sure what it does or what it checks on.

So it points to my ISY ( http://xxxx.com:80) 

All day it will go down then come back up 

Know 

Just wondering why this is happening and if I need to change something

 

thanks!

[paulbates]

When you get a host name for your network from dyndns, it redirects the URL back to your home network. 

The purpose of the message is for dyndns, the service, to validate that there is a clear path to the target, your home network. If you are getting errors, its not able to resolve that it can contact the configured devices in your home... That leaves 2 possibilities for the message:

1. Your home network, or the path to it, is unreliable... (I don't accept this one in 2018, but its possible)
2. Firewall rules, dyndns configuration or something else is preventing dyndns service from seeing the dyndns client on your network

Let's assume its 2 for the moment.

• How is the dyndns client setup in your house? Does your router provide a dyndns client, or are you running it on a pc or something?
• How did you configure the service? Can you post a pic of  the config (masking the sensitive parts?)

Paul

 

[oberkc]

Is the possibility of having multiple devices on port 80 a potential cause of this error?  I think I would try a different port for the ISY and point your dyndns URL to that new port.

[drprm1]

As far as I know I never set up anything at my house, using this domain name, on my router or computer. 

As far as multiple devices on port 80, I’ve only specified ISY to use 80 through port forwarding on my router.

Here are the settings

 

[paulbates]

Dyndns requires a client on your network to publish your local internet IP address to dyndns. That client informs the the dyndns service so that your unique DNS name resolves to your house. Most routers have the client in them today and that's where it gets setup.. but it doesn't have to be. It has to be somewhere though.

What services are you exposing to the internet? Having http exposed to the internet is not a good security practice. Its more likely that you are exposing https to the internet for things like mobilinc, etc. If that is the case, you're getting the message because your local network never responds to http... which is actually a good thing from a security perspective.

Try changing it to https on the dndns health check app and give it a day or so and see if it resolves. I'm not sure if mobilinc (if that's what you're using) uses the default path or something else.  Let's start with changing it to https

Paul

 

 

[drprm1]

Roger that. I’ll change and report.

Thanks,

[drprm1]

Went to dyndns to change and realized I have two health checks one http and one https. Again only http://xxx.com/80 is up and down

 

[paulbates]

Traffic on http:// is not encrypted and travels open across the internet. I believe this applies to authentication as well, meaning your id and password travel the internet un-encrypted when you remotely access your ISY.

If you have firewall rules forwarding the internet via http:// port 80 to your lan, those rules should be removed and another way found (https://) to accomplish the same function.

Paul

 

[drprm1]

Understood.

Thanks for the info and help