Domain Name Registration

[b4u]

Hi,

I have a simple question regarding Domain Names Registration.

Say I have a home computer connected 24/7 to the internet. It's a Win2000 Server, and I created an ASP web page.

Let's imagine my IP address is 215.54.23.120 (for example).

My questions:

[1] Can I access it using the address http://215.54.23.120/[/i]web_project[/i] (in the same way it works locally with http://localhost/[/i]web_project[/i])

[2] To register a domain, like www.my_home_page.com, I need to register it, pointing to my IP address, right? It has to be a fixed address, right?

[3] What entities do that registrations? How does it work?


PS: This are simple questions, and I know there is a lot of information around. I've read some of it, but there are still something "basic" lacking to make that "click" in my mind 🙂


Thanks

 

[labgeek]

1) yes you can access your computer by ip address if it is not being blocked by your isp or your own router if you use one.

2) When you register a domain name, you specify the domain name servers for the domain not the website's ip address. And you'll need at least 2 of them. Thier ip addresses must be static and registered as nameservers. Unless you're planning on doing your own dns serving you'll want to contract dns out. Since you're talking about a single ip address probably connected by cable or dsl line, I'd look into a dynamic dns service. There are several of them out there, some are free. They will give you the names and ip addresses of the namesevers to use when you sign up.

3) ICANN is the overseeing body. However many registrars that can do domain name registration for you. Way too many to name - but some ones off the top of my head - godaddy, namecheap, opensrs, network solutions, registerfly, enom (and like opensrs it's many resellers)... Do some serious looking around. Ask for opinions, I've used enom, opensrs, godaddy and network solutions. The only one I'd say not to go with is network solutions - too expensive, and poor service.

Edit - BTW, many ISPs have Terms of Service (TOS) statements that do not allow servers to be run. You'll want to check it out. Also if your IP address can change (most DSL and cable setups can and do change the customers ip address periodically), you need to use a dynamic dns service or be prepared to update by hand often, and suffer from outages while changes take place.

 

[b4u]

Originally posted by: labgeek
2) When you register a domain name, you specify the domain name servers for the domain not the website's ip address. And you'll need at least 2 of them. Thier ip addresses must be static and registered as nameservers. Unless you're planning on doing your own dns serving you'll want to contract dns out. Since you're talking about a single ip address probably connected by cable or dsl line, I'd look into a dynamic dns service. There are several of them out there, some are free. They will give you the names and ip addresses of the namesevers to use when you sign up.

Can you give me an example to ilustrate? I have WinXP Pro with Cable connection, dynamic IP. I made some intranet solutions, and now I just finished constructing one internet solution ... my own (for testing) and need to put it in the air ...


Thanks

 

[labgeek]

Because you're using a dynamic ip address, you will need a dynamic dns service. Go check out dyndns.org for starters. Since you have a dynamic ip and you want to use your own domain name, you'd need there custom dns service. They have a free service for static dns and for just dynamic dns where you use thier domain names. There are other services out there as well.

1) Find a domain name that's available - use the registrar of your choice's tools for this. Typing in a domain name in a browser does not tell you if it's available. A domain name does not have to have a web server attached to it.

2) Sign up for your dyndns server and they will give you a couple/few nameserver names and ip addresses to use.

3) You also need the client software that keeps thier dns server updated when your isp changes it. Load it and check it's working.

4) Go register when asked for the nameservers enter info obtained from step 2.

5) wait for dns to propagate - 24 to 72 hours generally, could be shorter or longer.

 

[AdamSnow]

register the domain with www.registersite.com

they allow you to login to a control panel, and you can do "domain pointing" ... just type in your ip, tell it to point your website there, and bam, your done...

easy for people that arent into the backend stuff.

 

[labgeek]

The only problem with going with a site like this is it doesn't appear to support dynamic ip addresses. Which means that if it changes, he'll have to go manually change the ip address at thier site. The whole since the change the site would be unreachable, or worse pointing at someone else's computer. Which is one reason many ISPs ban running servers. How would you like to startup your computer, connect to the internet, and have you connection start getting requests sent to it, using up bandwidth that you're paying for? Could also be a good way to get your "noticed" by the ISP. Dyndns services have a small utility that sits in the background, that notifies the dns servers when your ip address changes. One local ISP specifically targets people who run servers by frequently changing thier ip address - it's done automatically by monitoring software they're running.


I meant to say thing in the last post, but a much better solution is to host your application on a real webhost somewhere. Go over to WebHosting Talk and look through the offers/request forum. LOTS of really inexpensive hosting options there. And you don't have to worry about "overexposing" your computer by advertising it with a webserver and make it a target for attack.

Edit - come to think about it, were your planning on having email too? You gonna run your own email server? FYI, the number of ISPs that block smtp traffic on thier network to "known" mail servers is increasing.

 

[b4u]

First of all, thanks for the info, and for the links 🙂

Well, I was planning on creating a web page to a small company, with some functionality for the clients who join in. The reason for going to a "private" server, is about maintenance, data privacy, and the $$$.

<edit>
I'm currently developing an intranet solution, so the page would benefict from so much cross-data customer related 😉
</edit>

The company has a Win2000 Server, with SQL Server installed, ADSL connection 24/7, so it would be wise to use their own power to put a site on ... no need to pay for a service with SQL Server.

Creating their own domain, for example www.jogopan.com, and an email server for "@jogopan.com" would be a nice future add ... 🙂 That would bring more power to the solution ...

About email servers: Does it work the same way as registering a domain name? I have no experience with Email servers, I once played with Exchange Server 5, and it was quite a disaster 🙂 (well, not really, I learned something).

Thanks