Last Comment Bug 718784 - MCS needs access to the DNS editing of the child-domains
: MCS needs access to the DNS editing of the child-domains
Status: RESOLVED FIXED
:
Product: mozilla.org Graveyard
Classification: Graveyard
Component: Server Operations (show other bugs)
: other
: All All
-- normal (vote)
: ---
Assigned To: Arzhel Younsi [:XioNoX]
: Corey Shields [:cshields]
:
Mentors:
Depends on: 712908
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-17 12:22 PST by Soumya Deb [:Debloper]
Modified: 2015-03-12 08:17 PDT (History)
10 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description User image Soumya Deb [:Debloper] 2012-01-17 12:22:33 PST
We (MCS) got the mozilla-antarctica.org (710487), yay!

Now, to use this domain (and future community-domains) on the provided hosting, we need to edit/update it's DNS resource-records as required.

Presently MCS has no control over those domains, and can not forward them to desired hosting. Please resolve.
Comment 1 User image Shyam Mani [:fox2mike] 2012-01-17 16:37:23 PST
Do you have nameservers for this? Or do you want us to manage DNS?
Comment 2 User image Soumya Deb [:Debloper] 2012-01-18 11:07:54 PST
(In reply to Shyam Mani [:fox2mike] from comment #1)
> Do you have nameservers for this? Or do you want us to manage DNS?

For now, vps13934.ovh.net & sdns2.ovh.net are the NS we have - from the VPS that we're using temporarily to try-things-out. But, I'd actually look forward to a (more permanent) management policy, so that either:
1. IT is able to configure the settings as required, on demand by MCS.
2. Or, MCS manages the settings as required (if that's OK by IT).
3. Or, MCS and IT both are able to configure the settings as required.

Going by :XioNoX's timeline, this week we're going to have the dedicated server for MCS sites. It'll be best just to migrate the DNS also, along with it.
Comment 3 User image Shyam Mani [:fox2mike] 2012-01-20 05:27:07 PST
Let's go with 1. XioNoX and a bunch of others can do this pretty easily.

What's the IP you want the domain to point to?
Comment 4 User image Arzhel Younsi [:XioNoX] 2012-01-20 06:14:33 PST
this is in standby as long as we don't have the server.

Then we will need Shyam to change the root servers info of this domain to point to the Plesk server so both community and mozilla sysadmins will be able to manage it.
Comment 5 User image Arzhel Younsi [:XioNoX] 2012-01-26 12:31:11 PST
Okay, could you switch mozilla-antarctica.org to use:
    ns1.mediatemple.net
    ns2.mediatemple.net
as nameservers.

Thanks!
Comment 6 User image Dave Miller [:justdave] (justdave@bugzilla.org) 2012-01-30 07:29:35 PST
(In reply to Arzhel Younsi [:XioNoX] from comment #5)
> Okay, could you switch mozilla-antarctica.org to use:
>     ns1.mediatemple.net
>     ns2.mediatemple.net
> as nameservers.

Done.  This will take effect on the root nameservers within 15 minutes, however there is a 12 hour TTL on root nameserver records, so it could be up to 24 hours for anyone who already has it cached to pick up the new servers.
Comment 7 User image Corey Shields [:cshields] 2012-01-31 10:52:46 PST
Done??  reopen if not.

Note You need to log in before you can comment on or make changes to this bug.