I'm about out of hair I've been pulling it out so much. Any help/insight would be appreciated on this one.

Heres the situation
-a reseller account setup on a server with domain.com as main account
everything ran peachy keen - and decided to upgrade and got a secound account on another server but wanted to keep using the same domain so made the second server have www2.domain.com

first server had ns1.domain.com and ns2.domain.com registered and such.
when the second server account was added ns3 and ns4 were registered and added to that server. ips pointing correctly and such.

and now the headaches/hairloss begin.

sites that are created/setup on the second server seem to have a rolling blackout in regards to DNS. Some people can see some people cant. Sometimes no one can. Then it comes back. One person cant see ANY account on the second server - except they can access WHM & 2 domains that are using dedicated ips'
All the other domains/accounts are namebased and he cant see any of them on the second server -

Seems to be a DNS issue maybe? Namebased accounts not binding or something?

Just shooting in the dark there. :eek:

help?
tia

What is the need of ns3 and ns4?

What I understand from above scenario, you do not need ns3 and ns4 for www2. It should be setup in ns1 and ns2.

I don't know if I got you right or not?

Yeah, the site will resolve to the quickest nameserver - It doesn't connect to ns1 for 1 domain name and ns3 for the other domain on the other server, it'll connect to the fastest response from the name server - so effectively they would be connecting to the 2 different servers intermittently from the same domain name.

And you only have 1 virtual host set up on the second machine for www2. - hence 404 errors.
You should just add a zone on your first server to point to the IP on the second server - Using ns1 + ns2

I think that makes sense :-)

You have two options:
1. Consider your 2 accounts as separated accounts with own nameservers and WHM.
2. Consider them as one account with additional diskspaces and IPs
I would go for Option 2.

You mean I dont need seperate nameservers for seperate servers? *pulls out more hair*
ugh!

So when someone types in the domain url how is that domain pulled from the right server? ie how does it know that domaina.com is on server 1 and domainb.com is on server 2?

so in the dns zone for domain.com on server1 i would add a duplicate NS record of NS1.domain.com that points to the ip on the second server?

eh..
Its already been setup as 2 seperate accounts with each having their own WHM and nameservers - so how does that work?

I think running the second account www2 as a sub domain of your original reseller account is a bad idea - If you are just a reseller.

Do you have root access or are you a reseller?
If you are a reseller, then you need a different domain name for your second account and new name servers.

If the box is yours, you need to set up the server name as www2 and run bind on your first server and have server 2 slave off of it.
Then you would just use ns1 + ns2


As stated, if you have ns1 - ns4 for the same domain name - then the site will resolve to the quickest connection.

Originally posted by Buttercup
[B]You mean I dont need seperate nameservers for seperate servers? *pulls out more hair*
ugh!

So when someone types in the domain url how is that domain pulled from the right server? ie how does it know that domaina.com is on server 1 and domainb.com is on server 2?
It depends on the IP you assign to them

so in the dns zone for domain.com on server1 i would add a duplicate NS record of NS1.domain.com that points to the ip on the second server?
Yes, just point domain.com to the IP on the second server

When the second sub-domain www2 came into question, you should have just added an 'A' record to ns1, ns2. That's all you need.

You do not need nameserver on every server.

I will try to clear some things up..

1) Adding an "A" record for WWW2 was fine.. You used the account IP of your account on the second server right? No problem... Its simply an A record, pointing to your second server.

2) The reason you added ns3/ns4 was so you could add accounts on the second server, right? Then, they are pointed there, not the first one. I do this all the time, I have name servers from ns-ns12... Why? Well, think people.. You cant register NS/NS2, and use that for every server you are on - why? because they point to two IP's on server 1, not server2,3,4,5,6 etc.. think!

3) I had the same issue, still kinda do!! I can tracert from anyone in the world, but some people still cannot see it. Here is what to do: edit httpd.conf, and uncomment the name based accounts, it fixed 90% of my problems, but still some people cannot see some sites... I HATE IT!

Anyways hope I helped

Sean

Originally posted by Sean

2) The reason you added ns3/ns4 was so you could add accounts on the second server, right? Then, they are pointed there, not the first one. I do this all the time, I have name servers from ns-ns12... Why? Well, think people.. You cant register NS/NS2, and use that for every server you are on - why? because they point to two IP's on server 1, not server2,3,4,5,6 etc.. think!


NS/NS2 are only nameserver. Wherever they point, does not matter for other domains. They do not need to point to every server :)

I do not understand what you are trying to say.
:(

How I see it is this,

You would need all your name servers set up on the same server and then point to each servers IP for name based hosting.

In that scenario, you would never need to register more than the ns1 + ns2

If you have ns3 + ns4 registered and have them hosted on a second server, how would people get to your site (The original domain that had ns1 + ns2) ?

They would sometimes connect via ns1 and get your first server IP - then again they would sometimes connect to ns3 and that is pointing to server 2 at a different IP - Unless you have identical content on the 2 servers or add an A record pointing back to your main domain on server 1 you have problems with intermittent connection.

If you have root on the server, you can simply run your DNS from one server - again, you do not need ns3 + ns4 if you do that and accounts can be setup using your original ns1 + ns2

If you are a reseller - I think it best to register a new domain name.

Did I miss the point ?

Originally posted by Dotcomsnz
As stated, if you have ns1 - ns4 for the same domain name - then the site will resolve to the quickest connection.

Well, if domainA points to ns1 and ns2 (server1) and domainB points to ns3+ns4 (server2), wouldn't that work?

I have ns1+ns2 for 1 server and accounts setup to point to ns1+ns2
also, the second server has ns3+ns4 and accounts points to them fine.
:confused:

Joana,

Yes. that's fine. they are independent of each other.

But you can not have a few sub-domains on ns1, ns2 (www) and other subdomains (www2) on ns3, ns4.