"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You can't use DNS to specify ports. You would have to configure the cameras to listen on port 80 or 443 so that when http:// or https:// is used in the client browser a port number will not be required.

Another solution would be to use some other unused port like 8080 for each camera. You would still need to put the port into your browser but at least it will be easy to remember.

Both of those solutions assume you have separate IP's for each cam, if not then using and remembering different port numbers is the only option.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

If you have a home set up with a linksys router you can do port forwarding, but then you need a different IP for each camera because each DNS name is going to hit port 80, so you'll need different IPs to distinguish between camera's.

The other thing you can do is have the set up you have now with the camera:port, but have a web server (could be an XP machine, or something you are not using) then have that server redirect you by using host headers to the correct camera.

Lastly, you can have your hosting solution take care of redirecting you. I use 1and1.com and I'm able to redirect using their site. So for this solution you would have something like http://cam1.mydomain.com redirecting to http://cam1:8099 (or whatever) and so on.

Not sure what you can do with DynDNS, but you may want to find out what they can offer. The last two solutions would remove the requirement of having a separate IP for each Cam.