hmmm should i say night mare?
i had my main domain hosted on my servers and my subdomain pointed to their name servers, it was working fine for a bit and then suddenly one day it stopped. Since then it has been 5 days and they keep arguing that main domain and subdomains have to be hosted or pointed to same name servers. I know for sure it doesn't have to be that way as i have subdomains with other resellers. Website is live and my billign software (WHMCS) is installed on the subdomain but now its not working!!! driving me crazy!
Added to this...they change ip address on the account with no notice...so all the licenses either they give free or i installed stopped working, websites were always down!
i am a reseller there and i am running out of patience...their support is stupid or am i just stupid not able to understand/fix the subdomain issues!

hmmm should i say night mare?
i had my main domain hosted on my servers and my subdomain pointed to their name servers, it was working fine for a bit and then suddenly one day it stopped. Since then it has been 5 days and they keep arguing that main domain and subdomains have to be hosted or pointed to same name servers. I know for sure it doesn't have to be that way as i have subdomains with other resellers. Website is live and my billign software (WHMCS) is installed on the subdomain but now its not working!!! driving me crazy!
Added to this...they change ip address on the account with no notice...so all the licenses either they give free or i installed stopped working, websites were always down!
i am a reseller there and i am running out of patience...their support is stupid or am i just stupid not able to understand/fix the subdomain issues!
Hi,
What is the ticket ID related to this post? If you're using third party DNS for your main domain you will have to update the A record to the new IP. We have a thread on our forums about all server migrations when they are completed and the new IP's are always available within Reseller Central.

well i understand that..and i udpated it 3 days ago. Check your ticket history, i keep getting asked the same question again and again..looks like every time a support person picks up the ticket i have to start on page 1. Here is the ticket ID: HCT-895707

Yes,
Was actually working on that ticket before your post was made. To our defense your first post was a bit misleading to our techs as the way you said it you were using our name servers:
You Posted on: 03 Jan 2009 03:18 PM
can you tell me why this website is down? its pointed using name server, which are pointed to your servers pointed to below ip address
x.x.x.x
x.x.x.x
We Posted on: 03 Jan 2009 03:40 PM
Hello,
That domain is not pointed to our services.
Domain Name: <edited>
Registrar: 1 & 1 INTERNET AG
Whois Server: whois.schlund.info
Referral URL: http://REGISTRAR.SCHLUND.INFO
Name Server: NS1.NEXSCORP.NET
Name Server: NS2.NEXSCORP.NET
Status: ok
Updated Date: 02-jan-2009
Creation Date: 21-sep-2008
Expiration Date: 21-sep-2009
my.<edited>is not a top level domain and does not have the option to have nameservers configured for it. Only tld domain such as <edited> does.
Please point the subdomain my from <edited> to the ip address listed in your welcome email.
You Posted on: 03 Jan 2009 03:55 PM
<edited> is hosted by another server, not yours. I never had any problems working with subdomains, for example <edited> is hosted by 1and1 and the subdomains clients.<edited> and secure.<edited> are hosted on a different server. Can you update the DNS entries for the my.<edited> on my hosting account?
You Posted on: 03 Jan 2009 08:43 PM
no, the DNS records are pointing to ns3 and ns4.<edited> which are pointed to your name servers, i don't need to contact hem, i have many subdomains which are pointing to different name servers than the main domain and they work fine. If you are willing to provide me with WHMCS license, i can host it on my other server.
So i can prove my point plus i will get out of your hair.
You Posted on: 03 Jan 2009 09:20 PM
good lord. <edited> and my.<edited> are two different domains. <edited> is hosted by <edited>, but i pointed my.<edited> name servers to your name servers, but since the main domain is pointing to some where else i am asking you to udpate my.<edited> A record to point to yours, so my sub domain will start working again.
We Posted on: 05 Jan 2009 04:58 AM
Im showing that <edited> is pointed to the following nameservers.
nserver: ns1.<edited> 208.101.10.33
nserver: ns2.<edited> 74.53.46.114
Please point this domain to either ns1.speedydns.net/ns2.speedydns.net or the following ip addresses to resolve this.
x.x.x.x
x.x.x.x
You Posted on: 05 Jan 2009 11:57 AM
this is so freaking stupid, who in the world told you guys that the main domain and the subdomains have to pointed to same name servers? for crying out loud you don't know what you are doing? this is freaking ridiculous. I always had <edited> pointed to ns1 and ns2 of <edited>, why did it work before and stopped only for past few days?
my main domain <edited> is pointed to 1and1 name servers and my subdomains clients.<edited> is pointed to ns1 and ns2 of <edited>, why are they working?
As you can see your ticket as VERY confusing and we did the best we possibly could to resolve it. You got angry at us when we were the ones having a hard time understanding your situation.

IDK, this doesn't seem that hard to understand to me...
my.<edited>is not a top level domain and does not have the option to have nameservers configured for it. Only tld domain such as <edited> does.Is this specific to your system? Or a new CPanel restriction? Because it has certainly been possible in the past to create a parked or addon domain using a subdomain name and have it work just like any tld, complete with its own zone file. Of course you also need the NS records for it at the parent domain (wherever that is).
vajjas1 - have you tried just deleting and recreating the (sub)domain yourself? Unless something's changed, with reseller access you probably don't need support to do this for you anyway.

IDK, this doesn't seem that hard to understand to me...
Is this specific to your system? Or a new CPanel restriction? Because it has certainly been possible in the past to create a parked or addon domain using a subdomain name and have it work just like any tld, complete with its own zone file. Of course you also need the NS records for it at the parent domain (wherever that is).
vajjas1 - have you tried just deleting and recreating the (sub)domain yourself? Unless something's changed, with reseller access you probably don't need support to do this for you anyway.
Chris,
The OP stated several times their using our DNS then they would reply saying they weren't so it became confusing to techs.
As you stated yes you are correct but that is not the case. The OP has a domain hosted somewhere else using their DNS and created an account within our reseller control panel as a sub domain which is perfectly fine and doable but I think they are confused on how DNS works as they are claiming they can set different name servers for sub domains which I have never heard of.
I told them in a response to a PM after my reply on here and in the ticket that they need to update the A record on the third party DNS and they did not understand.
As we originally stated the DNS is not pointing to us on the root domain then the OP argued saying it was and it began to go back and fourth due to the confusing replies from the OP in the ticket.
All that needs to be done here is a simple A record update in the third party DNS mangement area.
My exact reply to their PM:
Originally Posted by vajjas1
by the way A record doesn't ahve to be pointed...for example check <edited>.com i host it with 1and and check clients.<edited>.com i host that with hostand.net. All i did was update the name servers in the domain control panel to hostand.net
My Response:
What you're saying is very confusing.
A single domain name can only have one set of name servers. Sure, you could set ns1,ns2,ns3,ns4 if you wanted to but it doesn't make sense.
The most common way this is done is what is called third party DNS. You point your main domain to ns1.blah.com and ns2.blah.com. Then you get a DNS editor and change A records to point where you want.
Then the DNS request goes to ns1/ns2.blah.com which redirects to the proper IP.
Example:
domain.com -> ns1.speedydns.net -> 1.2.3.4
clients.domain.com -> ns1.speedydns.net -> 1.2.3.5
The zone file for domain.com would have:
clients 14400 IN A 1.2.3.5
DNS is reloaded and it's done.

well i didn't delete the subdomain and recreate it. they have their own branding control panel and don't have WHM, or else i could have worked on it myself by editing dns entries for the sub domain. Now they are saying the A record is pointed to wrong ip address so i have to go and update it again later today. Will see if it works. Sounds funky as per them...but will do it so i don't loose billing.

my main domain <edited> is pointed to 1and1 name servers and my subdomains clients.<edited> is pointed to ns1 and ns2 of <edited>, why are they working?
As you can see your ticket as VERY confusing and we did the best we possibly could to resolve it. You got angry at us when we were the ones having a hard time understanding your situation.
I got angry, more like frustrated is the correct word. #1 you guys keep telling me its pointed to wrong servers, to start with my main tld can point anywhere in the world as long as my subdomain is pointed right, you kept telling me to change my main tld to point to your servers, which was rediculous. If you had copied the entire history this ticket has been going on since 2nd with numerous updates. There is nothing to be confused, my subdomain is pointed to n3 and ns4 which are pointed to ur servers, they worked fine...but they stopped working.

I got angry, more like frustrated is the correct word. #1 you guys keep telling me its pointed to wrong servers, to start with my main tld can point anywhere in the world as long as my subdomain is pointed right, you kept telling me to change my main tld to point to your servers, which was rediculous. If you had copied the entire history this ticket has been going on since 2nd with numerous updates. There is nothing to be confused, my subdomain is pointed to n3 and ns4 which are pointed to ur servers, they worked fine...but they stopped working.
This is where you had us confused as that just isn't possible and we told you that several times.
Please see these definitions to get a better understanding as I think this is just one big misunderstanding.
In the Domain Name System (http://en.wikipedia.org/wiki/Domain_Name_System) (DNS) hierarchy, a subdomain is a domain (http://en.wikipedia.org/wiki/Domain_name) that is part of a larger domain.[1] (http://en.wikipedia.org/wiki/Sub_domain#cite_note-0)
For example, "mail.example.com" and "calendar.example.com" are subdomains of the "example.com" domain, which in turn is a subdomain of the "com" top-level domain (http://en.wikipedia.org/wiki/Top-level_domain) (TLD).
You have one set of name servers for the top level domain. A sub domain created off of that can point to any IP in the world through an A record.
An A (address) record is a DNS record that can be used to point your domain name and host names (http://help.yahoo.com/l/us/yahoo/smallbusiness/domains/domainfeatures/advanceddns/advanceddns-08.html) to a static IP address.
The proper IP for your sub domain can be found within the ticket.

Chris,
The OP stated several times their using our DNS then they would reply saying they weren't so it became confusing to techs. Evidently. But it is possible for the main domain to use external DNS while the subdomain uses your DNS.
As you stated yes you are correct but that is not the case. :confused:
The OP has a domain hosted somewhere else using their DNS and created an account within our reseller control panel as a sub domain which is perfectly fine and doable but I think they are confused on how DNS works as they are claiming they can set different name servers for sub domains which I have never heard of.They can. That is exactly how DNS works - there's really no difference between using the .com nameservers to find NS records for example.com vs. using the example.com nameservers to find NS records for sub.example.com. I'm rather surprised you haven't come across this sort of thing before.
Of course the simpler way is to do as you suggest - set up an A record on the main domain, but the disadvantage of this method is that it won't update automatically when you change IP addresses.
Anyway, I don't know the details of what went wrong here - just wanted to express some kind of understanding for the OP's frustration. :) Hope you get it sorted between you.

I can also recommend that you be polite to the support techs. Being rude won't get you anywhere.

Evidently. But it is possible for the main domain to use external DNS while the subdomain uses your DNS.
:confused:
They can. That is exactly how DNS works - there's really no difference between using the .com nameservers to find NS records for example.com vs. using the example.com nameservers to find NS records for sub.example.com. I'm rather surprised you haven't come across this sort of thing before.
Of course the simpler way is to do as you suggest - set up an A record on the main domain, but the disadvantage of this method is that it won't update automatically when you change IP addresses.
Anyway, I don't know the details of what went wrong here - just wanted to express some kind of understanding for the OP's frustration. :) Hope you get it sorted between you.
But here's the thing the way the OP is doing it wouldn't make sense like that. Sure what you're saying would work IF the sub domain was in fact using our name servers (even though they are not the authoritative name servers for the primary domain name but is possible).
In this case the root domain and sub domain are NOT using our name servers. One is using 1and1 and the other is using another set of name servers.
Therefore I do not see the benefit as our DNS cluster cannot update IP's for 1and1 or the other company.
Regardless, if the root domain's name servers fail wouldn't the sub domains fail as well? It still needs to go through the root name servers to get the sub domains name servers either way. Wouldn't a simple A record be more appropriate and much simpler?
Hopefully now you can see why this is confusing :-/

In this case the root domain and sub domain are NOT using our name servers.Looks like you've found the problem then. :agree: