That is, say DHCP will only cover 192.168.0.100 through 192.168.0.255; this leaves all the other IP addresses from 192.168.0.0 through 192.168.0.99 to be statically assigned to your cameras, your network printers and yes – even your routers themselves.The dynamic IPs can then be assigned to things like laptops & smartphones which don’t actually care about which IP address they get, so long as they get an IP address; INSTALL Camera Admin Software – IF you have any – onto a computer on your LAN; this will be used to find & configure each camera using the camera’s MAC – permanent hardware-based – address, thereby allowing you to easily set a static IP address for it; INSTALL Camera01.Browse directly to the individual admin website that each camera runs using its internal LAN IP address; On my own home installation there was NO Camera Admin Software, so I browsed to the little admin web site on each camera.On my brother’s home installation there was a Camera Admin Software, so I installed it, launched it, got a list of all cameras on the LAN from it, and then selected each camera and manually configured it; BROWSE to and LOG IN to the camera’s admin/control panel.Dyn DNS doesn’t care which of their domains you piggyback off of by adding your own router’s hostname as an A-record to their domain. In fact, for MORE moolah you can update your OWN domain, but since these domains are with a different domain registrar, there is NO guarantee of how long changes to those records will take to propagate (seconds, minutes, hours or even DAYS), so that’s the value proposition DDNS service providers offer – they can GUARANTEE your hostname records will update in as little as 60 seconds… The router enables the IP cameras’ individual video streams to be accessible through it (the router) via “Port Forwarding”.The very name itself implies that the streams are differentiated by the PORT# each camera operates on – NOT the internal (LAN) IP address of each camera; This may seem like a lot of conceptual points to grasp, but I’m hoping it – A camera generates a video stream on (say) port 8001, using HTTP (note how I don’t mention the internal IP address because it doesn’t matter what it is, so long as it has one and it’s static – you don’t need ANOTHER changing IP in this equation); – The router has a Port Forward rule permitting HTTP (you can use TCP) traffic on port 8001; – As soon as this camera is running and this router rule is active, you CAN see the video stream from the public internet; you’ll simlpy be accessing it via the external (WAN) IP of the router AND the port# of the stream; – You get to access this video stream via a “vanity” URL by leveraging your DDSN service provider account; that’s where you create a “hostname record” which maps or “resolves” the vanity domain back to the (invariably-changing) external (WAN) IP address of your router.REPEAT for Camera02, but with Port Forwarding Settings of “Camera02 | port 8022-8022 | 192.168.0.22 | enable Go try it.
So, if I picked “PURPLEZONE” for the hostname of my brother’s router, and “DYNDNS. WS SAVE settings Your router’s DDNS service is now configured.
A DDNS client monitors for a change in a hostname’s IP address; when/if the IP address changes, the DDNS client has all the details (e.g.
URL, username, password, hostname, new IP address) to auto-connect to the DDNS service provider, log-in, and actually edit the associated A-record for that hostname.
Both of these records use the same Dyn DNS domain “dyndns.ws”, but it was NOT required.
It could just has easily been 2 different domains Dyn DNS owns, like “dyndns.ws” and “dyn-homeip.org”.
CONFIGURE Home-base LAN with ip addresses 192.168.0through 220.127.116.11 (sound familiar?