Have a server at http://xxx.xxx.xxx.xxx:8000 and want http://myname.mydomain.com:8000

R

RavinDJ

Supreme [H]ardness
Joined
Apr 9, 2002
Messages
4,446
Have a server at http://xxx.xxx.xxx.xxx:8000 and want http://myname.mydomain.com:8000

Basically, I have a DVR system with a local IP address of 192.168.1.175 serving http web access on port 8000. So, locally, I can view the DVR on http://192.168.1.175:8000 but I want to be able to do it remotely.

I already have set up port forwarding on my router and our ISP allows serving.

I want to be able to have http://mydvr.mydomain.com:8000 point to http://xxx.xxx.xxx.xxx:8000 where xxx.xxx.xxx.xxx is our public, static IP address.

I know it has to do something with DNS. Our domain is with www.1and1.com and I just don't know what DNS settings to set up. There's A, C, ANAME, and other crap (obviously I'm not too good with DNS).

Any help will be greatly appreciated. Thanks!!!
 
I'm not the best with it either but you're gone need an A Record. Make it whatever.yourdomain.com and point it to your home ip address. This will work assuming you have a static ip address.
 
Have you registered your DNS name yet? "mydomain.com"
Once done...what I do when I want a custom name..such as "office.mydomain.com" or "vpn.mydomain.com"..or in your case...dvr.mydomain.com...those are CNames you'd make.

If you have a dynamic IP account..you'd want to sign up with a dynamic DNS service such as dyndns.org
 
Wait a minute stonecat, maybe you could help me understand this better. I thought cnames pointed to A records. Why would you use cnames in this situation? I've always used A records for stuff like this. I would understand if you had multiple names pointing to your home ip but for just this one....
 
They're always flexible...and like most things with Windows....6 different ways of doing the same thing. I've usually done CNames for remote services for my clients..they'll have their website at a webhost somewhere....their MX record point to either that or their WAN IP, but I'll make a CNAME for an easy to remember name that points to the WAN IP of their office network..so they can easily remember how to get to their remote web workplace portal, or VPN to their router. remote.theirdomain.com or vpn.theirdomain.com
 
Just go and use a service like No-IP. Their free service probably would suite you just fine, but if you want to actually register your own domain, it's very simple through them and cheap.
 
He already has a domain through 1&1. I've heard nothing but bad reviews about them. I prefer peer1. But that's off topic.
 
You don't have to point to it through DNS just to access it remotely.

You can just access it through your static public IP.
DNS is just for the convenience of giving numbers names.
 
That's kinda obvious. :p But can you remember your ip? (pls don't say yes :D)
 
jbog91 said:
That's kinda obvious. :p But can you remember your ip? (pls don't say yes :D)
Click to expand...

Once you make a bookmark/favorite there is no need to memorize it.
But to answer your question, yes. I can remember a lot of critical static IPs I use.

EDIT: Also the OP said, "So, locally, I can view the DVR on http://192.168.1.175:8000 but I want to be able to do it remotely."
and he also said he has a static IP. DNS is not required for what he needs, and he may not realize that.
 
True dat. I don't know about his situation but I couldn't bookmark my ip since I have to access it from different computers at my school's network and else where. That's why dns comes in handy for me.

I assumed that he knew that he didn't need dns. But we all know what assuming does.:rolleyes:
 
Yep, it all depends on if this is just simple personal use or if he's setting it up for public access.
If it's meant for a lot of people then setting up DNS makes sense.
 
I didn't hear anyone ask the most important question yet... do you have a static or dynamic IP from your ISP?

If static, yeah... just go ahead and setup an A record through your registrar.

If dynamic, you need to get a little tricky. You can setup a dynamic dns account (I used to use dyndns.org but that was a long long time ago) and use setup an A record subdomain and use URL forwarding to point toward your dyndns URL. This should work with specifying a port other than 80, but I've honestly never tried it. Let me know how you make out.
 
Yep. Set up an A record and works wonders!

P.S. Static all the way :D
 
You must log in or register to reply here.
Back
Top