So here's a weird new problem. If I am outside of my network and I put in my dynamic name server address and port number, in my browser, ui3 comes up every time. Rock Solid, quick, and reliably.
However, in the blue iris app, if I use that same domain name and port number, select http, it will Spin and spin and eventually say that it cannot connect to the server. If I replace the dynamic domain name with the actual IP address, it will connect.
If I am on another public ip, for example at walmart, or mcdonald's, it works 100% using the dynamic domain name service in the app.
Likewise, if I connect to my VPN Home Server, it will Connect using the dynamic domain name server (I am leaving the lan portion with the local IP blank).
So for some reason the dynamic domain name service does not work on my Verizon service. It works from Wi-Fi both on my land or on a public wi-fi. And it also works on Verizon when I'm using my VPN to connect to my home. I am stymied. It doesn't make sense that ddns doesn't work in One path but on all others it does
However, in the blue iris app, if I use that same domain name and port number, select http, it will Spin and spin and eventually say that it cannot connect to the server. If I replace the dynamic domain name with the actual IP address, it will connect.
If I am on another public ip, for example at walmart, or mcdonald's, it works 100% using the dynamic domain name service in the app.
Likewise, if I connect to my VPN Home Server, it will Connect using the dynamic domain name server (I am leaving the lan portion with the local IP blank).
So for some reason the dynamic domain name service does not work on my Verizon service. It works from Wi-Fi both on my land or on a public wi-fi. And it also works on Verizon when I'm using my VPN to connect to my home. I am stymied. It doesn't make sense that ddns doesn't work in One path but on all others it does