Results 1 to 16 of 16
-
06-13-2002, 10:55 PM #1Junior Guru
- Join Date
- Mar 2002
- Posts
- 238
Using your own nameservers (newbie question)
Let's say you're host.com
You have:
ns1.host.com (some dedicated IP)
ns2.host.com (another dedicated IP)
which you're using as the domain host.com's nameservers.
Don't you need another nameserver to indicate the existence of ns1.host.com and ns2.host.com?
How can a domain use its own domain as the nameservers?
-
06-13-2002, 10:57 PM #2Web Hosting Master
- Join Date
- Jul 2001
- Posts
- 889
I don't know the technical answer...
but basically, you'd have to register your nameserver with your domain registrar. When you do that, you have to input the name (ns1.host.com) and its IP.
-
06-13-2002, 11:08 PM #3Aspiring Evangelist
- Join Date
- Apr 2002
- Location
- Chicago, Illinios
- Posts
- 391
Yes, you register you're nameservers from your domain registrar using 2 ips.
-
06-13-2002, 11:14 PM #4Junior Guru
- Join Date
- Mar 2002
- Posts
- 238
Ahh, yes. It all makes sense now.
Thanks for the quick answers aragon and mas3000!
-
06-14-2002, 12:13 AM #5Web Hosting Master
- Join Date
- Feb 2002
- Posts
- 956
Note:When you register nameservers it may take over a week
-
06-14-2002, 12:17 AM #6Junior Guru
- Join Date
- Mar 2002
- Posts
- 238
Roly: you read my mind. I was just going to ask that.
So even if my ISP sees the new nameservers after 24 hours, it's not safe to start using them until a week later when I'm sure it's propagated across the net?
-
06-14-2002, 12:21 AM #7Web Hosting Guru
- Join Date
- Feb 2002
- Location
- New York
- Posts
- 285
here we go....
Its a long story but to make it short here is how it works.
its layed out for youWCSWEB.NETWORKS - 24x7 Support We're here to help anytime, day or night!
WCSHOST.Net <- Call us (800) 590-0017 ->
Linux based Cpanel Shared and Reseller premium Hosting with Fantastico & rvskin
Windows based Helm Shared Premium Hosting / Remote Backup solutions
-
06-14-2002, 12:33 AM #8Web Hosting Guru
- Join Date
- Feb 2002
- Location
- New York
- Posts
- 285
time
It all depends at what type you make your takes. But most of the time it takes about 24 hours. generally the max is 24 to 48 hours so that the name servers will propagate globally.
WCSWEB.NETWORKS - 24x7 Support We're here to help anytime, day or night!
WCSHOST.Net <- Call us (800) 590-0017 ->
Linux based Cpanel Shared and Reseller premium Hosting with Fantastico & rvskin
Windows based Helm Shared Premium Hosting / Remote Backup solutions
-
06-14-2002, 12:42 AM #9Junior Guru
- Join Date
- Mar 2002
- Posts
- 238
WCSWEB - thanks for the graphical diagram. Very helpful!
How does virtual hosting on 1 shared IP work? (short, simplified version is OK!)
If the user's machine requests the IP, how's the server supposed to know which domain the user wants? Is additional info sent along with the IP request to indicate that domain1.com is wanted?
-
06-14-2002, 01:40 AM #10Web Hosting Master
- Join Date
- Feb 2002
- Posts
- 956
Originally posted by kreativ
Roly: you read my mind. I was just going to ask that.
So even if my ISP sees the new nameservers after 24 hours, it's not safe to start using them until a week later when I'm sure it's propagated across the net?
-
06-14-2002, 04:53 PM #11WHT Addict
- Join Date
- Jun 2002
- Posts
- 146
Re: here we go....
Originally posted by WCSWEB
Its a long story but to make it short here is how it works.
its layed out for you
-
06-14-2002, 04:54 PM #12WHT Addict
- Join Date
- Jun 2002
- Posts
- 146
Re: here we go....
Double post (server real slow)
-
06-14-2002, 05:04 PM #13Web Hosting Master
- Join Date
- Feb 2002
- Posts
- 2,120
don't forget that you need IP per each domain name service record (ns5.name.com with Internic for example). Also remember that it should have A record and should not have CNAME record for example :>
-
06-14-2002, 05:14 PM #14Web Hosting Master
- Join Date
- Apr 2002
- Location
- AU
- Posts
- 1,049
1, you dont NEED an A record, but it makes life easier
2, you dont NEED to dedicate IP's just as nameservers (they dont need reverse delegation)
3, you CAN use the same IP for an unlimited amount of nameservers
4, a nameserver is a sticky record, so you cant just make an A record and make it work, they have to be made thru your registrar's control panel
5, initial delegation of a nameserver takes about 24 hours
6, re-delegation of a nameserver can take up to and over 72 hours
7, its a good idea to get a friend to act as your secondary nameserver on a different server (if you dont have two) for availability
-
06-14-2002, 05:15 PM #15Junior Guru
- Join Date
- Mar 2002
- Posts
- 238
Originally posted by apollo
don't forget that you need IP per each domain name service record (ns5.name.com with Internic for example). Also remember that it should have A record and should not have CNAME record for example :>
primarydomain.com. NS ns1.primarydomain.com.
primarydomain.com. NS ns2.primarydomain.com.
ns1.primarydomain.com. A 10.1.1.1
ns2.primarydomain.com. A 10.1.1.2
Is that right?
I think I've got it now.
(Why are these records needed? If ns1.mydomain.com and the IP are already registered with the registrar, isn't that all that's needed? I assume people are just querying the IP for DNS data).Last edited by kreativ; 06-14-2002 at 05:27 PM.
-
06-14-2002, 08:14 PM #16Junior Guru
- Join Date
- Jun 2002
- Location
- Sherbrooke, Québec
- Posts
- 184
"How does virtual hosting on 1 shared IP work?"
Here is the short, non technical reply:
When you browser sends a request for a web page to the web server, it passes the domain name in the request as part of the HTTP protocol header. The web server uses that information to find what website you want to see.
As you understand, if that information wasn't passed with the request, you would need a dedicated IP for each websites.
This information is also used to see what host you want to see (the www or other, before the domain name)