2 or 4 nameservers

[dpyers]

Way back when the earth was new and dinosaurs roamed my driveway chomping on my dsl, I was told that as a new account, I should only use ns2 and ns3 name servers as ns and ns1 were pre-Jurassiac and us pre-Cambian troglodytes would have no use for them and would not have new domain info placed there.

With the new ip's, is this still the case? I noticed that If I do a nslookup using the new ip's for ns or ns1 I now see my domains there.

Should I update my registrar info to use all four name servers instead of just ns2 and ns3?

[generic]

if nobody else answers, i would say YES.

cant hurt, and your covered if hsphere ever sets up a site of yours to use ns and ns1 some day.

[princessangry]

well mines always ns2 and 3.... oddd

[Vantage]

Uggg Assumptions BAAADD.....
This troglodyte says look at what the control panel gives you each time.

More than likely it will be ns2 + ns3 for the forseable future..
You dont want to rely on that though, as from time to time we may switch over to ns and ns1 during maintenance or durring a flurry of signups the load on ns2 and ns3 might get high enough for us to want to start loading the other servers again...
You never can predict the future.....

[princessangry]

yep u got that right.....

[cambodia]

Originally Posted by princessangry

well mines always ns2 and 3.... oddd

i'm always give ns2 ns3 to new sign up too what ns4 use for ?

[princessangry]

one site had an ns10!!!!

[dpyers]

With the old IP's. I didn't have any domain info on ns and ns1. With the new IP's, I do.

My control panel says ns2 & ns3 and in the past, when I did a nslookup through the ip's for ns and ns1, I didn't get any hits for my domains. Using the new ip's for ns and ns1 I do get hits.

So it sounds like I should be using ns2 ans ns3 as primary and secondary, with ns and ns1 as third and fourth for back-up purposes if ns2 and ns3 are down for maintenance.

If ns2 and ns3 go down in an "unscheduled manner", will ns and ns1 be current?

[Brangwyn]

Don't add any nameservers to your domain that isn't listed in the control panel .. Vantage spelled that out best I think

If your domain is listed in the CP as being on ns2 or ns3 then it's not going actually going to be in ns or ns1 zone files (it may resolve if they forward to each other perhaps, but they certainly won't be authoritive) at least thats how i understood they were setup some time ago.

The IP's changing shouldn't have changed anything, perhaps they are now forwarding to each other but I'd really recommend you just use what the CP tells you to and nothing else.

[princessangry]

now that'd be nice if I can have 10 tho... hehhe..... (odd huh)

[dwhite]

Originally Posted by Brangwyn

Don't add any nameservers to your domain that isn't listed in the control panel .. Vantage spelled that out best I think

If your domain is listed in the CP as being on ns2 or ns3 then it's not going actually going to be in ns or ns1 zone files (it may resolve if they forward to each other perhaps, but they certainly won't be authoritive) at least thats how i understood they were setup some time ago.

The IP's changing shouldn't have changed anything, perhaps they are now forwarding to each other but I'd really recommend you just use what the CP tells you to and nothing else.

Interesting to note that for my service domain, the ns and ns1 are authoratative, the ns2 and ns3 are not. However, that is not the case on all of the client domains. I've had trouble with some forwarding domains resolving lately. It took some head scratching and research to determine exactly which ns to use for authoritative.

[dpyers]

Originally Posted by Brangwyn

Don't add any nameservers to your domain that isn't listed in the control panel .. Vantage spelled that out best I think

Actually, it was Vantages' comment that from time to time they might switch over to ns and ns1 that made me think I should be including them

[dwhite]

Hmm, just went to DNS reports and checked the service domain. Received two FAIL errors for ns2 and ns3.

ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
216.157.145.12
216.157.145.13

ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns2.ewebheads.net.
ns3.ewebheads.net.

I've checked at my registrar, and all 4 are located and resolve to the correct IP. In the CP, some of my sites are on ns & ns1, other sites are the opposite, so I'd say that it definitely not set in stone that they are on ns2 & ns3.

If it is possible that they may switch from time to time, is there any harm in including all of them?

[Brangwyn]

All older domains (9+ months or so) are on ns & ns1, ns2 & ns3 are relatively new, pretty much all new domains go on ns2 & ns3 unless for some strange reason Votech had them locked off at the time your customer signed up. You may have a few domains on ns1/ns2 as well becuase ns3 wasn't brought online till a few weeks after ns2 iirc.

You should NOT have all 4 listed on any domain, hence the lameservers error your getting thats what Vantage and I have been trying to explain

I think Vantages comment was regarding switching them off within HSphere for signups and reverting back to using ns & ns1 for signups to help balance the load, not that they would "switch off" the nameservers physically.

[princessangry]

yah vortec told me about this yesterday.....