logoAbout Me: I'm a freelance web developer that specializes in WordPress Themes and plugin development. I've written about some of my projects here.
Hire me e-mail

Home / tweets / Found my first GoDaddy DNS lim…

Found my first GoDaddy DNS limitation: multiple nameservers for a subdomain. Which Rackspace won’t do and I’ve never even heard of doing tha

  • Good thing I'm not one to say I told you so.

    But, out of curiosity, why would you want to have nameservers for your subdomains that are different from your primary ones? Maybe I'm not getting what you're saying.
  • Dan
    No you're getting what I'm saying it's just that it's so obscure that I've found noone does it.

    The reason is some marketing analytics requires it for gl.com.
  • I think you may have never heard of it because it may not be possible. I've never heard of having different nameservers for subdomains; different addresses, sure, but all on one nameserver.
  • Dan
    No not one name server.

    QUESTION SECTION:
    ;www3.domain.com. A

    ;; ANSWER SECTION:
    www3.domain.com. A 69.48.237.11



    ;; AUTHORITY SECTION:

    www3.domain.com. NS ns1.coremetrics.com.

    www3.domain.com. NS ns2.coremetrics.com.

    www3.domain.com. NS ns3.coremetrics.com.



    ;; ADDITIONAL SECTION:

    ns1.coremetrics.com. A 66.179.5.6

    ns2.coremetrics.com. A 64.238.216.230

    Ns3.coremetrics.com. A 209.235.30.142
  • But I don't see this as subdomains being on different nameservers; all three of those nameservers are providing records for the domain.com domain, and therefore the www3 subdomain. This is normal; is this what you're saying GoDaddy doesn't allow?
  • Dan
    Your missing it. These are records they want you to add to an already setup domain that is pointing to other nameservers.

    So
    www.domain.com NS ns1.dns1..
    www.domain.com NS ns2.dns1..

    www3.domain.com NS ns1.dns2..
    www3.domain.com NS ns2.dns2..
    www3.domain.com NS ns3.dns2..
  • I get it now (although that's different than what you listed above).

    It is actually possible to do this (using a DNS server you actually have control of, like BIND), but I'm still curious as to why anyone would want to do this. Could you elaborate any more on that? What are they trying to achieve?

    The only logical thing I could think of would be in a very large organization that uses multiple levels of subdomains and wants to delegate the management duties of each to different servers/teams, or if there is one group that you want to grant control of the DNS for only a specific subdomain (www for example) to, without them being able to affect the primary DNS for the domain.

    In any event, it seems like this would be such a rare situation that I wouldn't even fault GoDaddy for not providing for it; anyone who wants to do that kind of complex setup needs to be running their own DNS server anyway.
  • Dan
    [quote comment="243043"]
    The only logical thing I could think of would be in a very large organization that uses multiple levels of subdomains and wants to delegate the management duties of each to different servers/teams[/quote]
    That's exactly it. We would need to give subdomain control over to coremetrics in order for them to use it for analytics. That way they can control first party cookies and such from another colo.
  • Did you finally fix this issue? I have similar problem now...
blog comments powered by Disqus