KevlerS
06-23-2002, 02:04 PM
Hello,
I’m currently using the name servers ns1.emegaweb.net and ns2.emegaweb.net to point to my current server. I just purchased an additional server and need to create name servers for that as well. Can I use ns1 and ns2 for this as well, or do I have to create ns3.emegaweb.net and ns4.emegaweb.net and point them to the new server’s IP addresses? Or would I have to purchase an additional domain name and setup ns1.domain.com and ns2.domain.com for the new server? Could someone please provide some assistance in setting this up? I’m using the Plesk control panel. Thanks in advance.
SoftWareRevue
06-23-2002, 02:51 PM
I don't remember how to set up name servers in Plesk.
But, you will need to create ns3.emegaweb.net and ns4.emegaweb.net because your ns1 and ns2 already point to IPs that are on your current server.
Besides helping out your servers know the difference, it makes it easier for you to keep track where things are. :)
hmmm . . . . . maybe I should go look at our Plesk servers and tell you better.
KevlerS
06-24-2002, 12:15 AM
Ok, I did the following items on the new server and my test domain (eingress.com) still doesn’t seem to be loading:
I added ns3.emegaweb.net and ns4.emegaweb.net to my domain host information with my registrar. They are both pointing to the new server at this point.
I added a DNS record (A type) for ns3 and ns4 to my main server (where the emegaweb.net domain name is residing) and pointed them to the new server’s IP addresses.
I did an address lookup on the test domain and it seems to point to the correct location:
Canonical name: eingress.com
Addresses: 66.227.26.41
However, the page still does not seem to load through the browser.
Any help would be appreciated!
SoftWareRevue
06-24-2002, 12:45 AM
Looks like you did it right to me. :)
==============================================
This is the placeholder for domain eingress.com. If you see this page after uploading site content you probably have not replaced the index.html file.
This page has been automatically generated by Server Administrator.
==============================================
KevlerS
06-24-2002, 01:41 AM
Thanks for checking it out SoftWareRevue. I’m still getting this:
The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.
Etc.
Also take a look at this domain: 3-corners.net
I am unable to get them to load. I’m trying this out from New Jersey. Any suggestions on what might be wrong? Or do I simply have to wait for everything to process?
SoftWareRevue
06-24-2002, 10:37 AM
When I go to 66.227.26.41, I get:
==============================================
This is the Server Administrator™ default page.
If you see this page it means:
1) hosting for this domain is not configured
or
2) there's no such domain registered in Plesk.
For more information please contact support@emegaweb.net
==============================================
However, 3-corners.net doesn't display. But, that could be because of propagation. As eingress.com comes up fine.
Have you tried clearing your browser cache?
prime
06-24-2002, 10:39 AM
Hmm... not too clear on what you're trying to do, but I guess it could be done with only 2 name servers.
I’m currently using the name servers ns1.emegaweb.net and ns2.emegaweb.net to point to my current server. I just purchased an additional server and need to create name servers for that as well.
Name servers are used with domains. You need 2 name servers for each domains. They can be both on the same machine, or ideally, in separate data centers. You do not need to set up name servers inside each domains (ie, you do not need ns1.domain1.com for domain1, and ns1.domain2.com for domain2. domain2 can use the domain1 name servers without any big problems; it's just another zone).
But you definitely don't need to add name servers when you add a server, especially not if it's on the same domain name (www1.domain1.com was your current server, and the new one is www2.domain1.com). But it would be very good in that case to put ns1.domain1.com on the same server as www1, and ns2.domain1.com on the same server as www2. That way if a server goes down your network (what's left of it) can still be reached.
Could someone please provide some assistance in setting this up? I’m using the Plesk control panel.
I don't think Plesk can manage slave zones yet, so if you split your name servers you'd have to set up the slave zone manually on the 2nd server. But it's quite easy... just a few lines to add here and there and reboot of named and you're set. But I don't know enough about your current setup to get into this now (for example, are your 2 name servers on the same server? Do you want to split them?).
I am unable to get them to load. I’m trying this out from New Jersey. Any suggestions on what might be wrong? Or do I simply have to wait for everything to process?
Now your setup should be working, but it sounds a bit complicated to me for what you're trying to do...
Suggestions? Name servers have a cache. When you tried to access a site the first time, the site info was probably loaded in your ISP's cache. So when you try to access your site again, it won't even look it up. SoftWareRevue's lookup probably worked because his name server had never heard of that site and went to the source to get the address. So go in your your computer configuration, and set it to use your name servers and not your ISP's one. This will get the cache issue out of the way. But keep the old info, you may want to get back to it in the future.
BTW, your site wasn't responding 2 mins ago when I tried.. dig and nslookup didn't return anything either.