It connects and works even when I change the url from https to http. Not a secure connection then.
It causes some concern when you think you're at channelsdvr.net, but you're not.
Using 192-168-x-x.channelsdvr.net is the same as typing 192.168.x.x in directly. It's a hostname that resolves to the IP, because SSL certificates are based on hostnames.
No one outside your network can access 192.168.x.x using either method.
1 Like
Yes, I knew all that.
Question was how it resolved to my local private intranet IP address.
I'm guessing your server verifies it's me at the user subdomain (############.u.channelsdvr.net) and with proper auth will respond with my local IP.
Just wondering why if my browser was redirected to 192.168.1.3 it doesn't display that in the url.
It's like if you went to https://my.bank.com but were really at https://iownzunow.fool but your browser didn't show that url, you might have reason to be concerned.
Our server is not involved at all. It's simple DNS. I don't know if you're asking me how dns resolution works?
It's like DYN DNS, we essentially created every combination of x-x-x-x as a DNS record and pointed it to x.x.x.x
1 Like
Got it. Thanks.