Closed
Bug 950446
Opened 11 years ago
Closed 10 years ago
DNS Changes for mozilla.lt
Categories
(Infrastructure & Operations :: SSL Certificates, task)
Infrastructure & Operations
SSL Certificates
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: tom, Assigned: cturra)
References
Details
Hi, Please can you create/modify the following DNS records on mozilla.lt: Add TXT Record google-site-verification=qw3imldyHFbdbiF7NJY14uSaL_-9timQlUCNISBL9o8 Set NS to ns368374.ovh.net As per usual, not worth setting secondary dns here. You could use sdns1.ovh.net but the records aren't there
Assignee | ||
Comment 1•11 years ago
|
||
these two action items are mutually exclusive. would you like the TXT entry added to the current DNS now so you can complete Google Apps domain verification then move the Name Server record to OVH? or would you like the name server record moved to OVH so you can manage the Google Apps domain verification yourself?
Flags: needinfo?(tom)
OS: Mac OS X → All
Hardware: x86 → All
Right, I see what you mean. Was half asleep when I filed this (when aren't I?). Set the NS please, also, because of that regulation I found, set ns2 to sdns2.ovh.net Thanks Chris!
Flags: needinfo?(tom)
Assignee | ||
Comment 3•11 years ago
|
||
i have submitted the name server change through our registrar. .lt domains can take a little bit to update, but i will report back when that's complete.
Assignee: server-ops-webops → cturra
Assignee | ||
Comment 4•11 years ago
|
||
:tad - i just wanted to follow up to confirm you know that the name servers over at OVH.net are not configured to receive this domain. if the name server change happens as requested, you will take down mozilla.lt $ dig +short @ns368374.ovh.net mozilla.lt | wc -l 0 currently, through our name servers, the base domain and www resolve to: 193.219.42.40. can you please ensure this is configured correctly over at OVH.net? $ dig +short mozilla.lt 193.219.42.40 $ dig +short www.mozilla.lt 193.219.42.40
Flags: needinfo?(tom)
Assignee | ||
Comment 5•11 years ago
|
||
:tad - just pinging for feedback here.
Assignee | ||
Comment 6•10 years ago
|
||
any update on this :tad?
Okay, lets go ahead and just add google-site-verification=qw3imldyHFbdbiF7NJY14uSaL_-9timQlUCNISBL9o8 as a txt record for now. NS can come once the community have got their stuff onto the shared server. (Creating their accounts now)
Flags: needinfo?(tom)
Assignee | ||
Comment 8•10 years ago
|
||
txt entry added as requested. $ dig +short txt mozilla.lt "google-site-verification=qw3imldyHFbdbiF7NJY14uSaL_-9timQlUCNISBL9o8"
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Can we go ahead with the following instructions please? Set NS1 to ns368374.ovh.net Set NS2 to sdns2.ovh.net (pointlessly, but better to avoid regulation issues) Really appreciated :) Site is uploaded to ovh plesk now, and should be active in the DNS server
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 10•10 years ago
|
||
(In reply to Tom Farrow [:Tad] from comment #9) > Can we go ahead with the following instructions please? > > Set NS1 to ns368374.ovh.net > Set NS2 to sdns2.ovh.net (pointlessly, but better to avoid regulation issues) dns propagation might take a couple hours, but the name server record changes have been made. $ whois mozilla.lt | grep -i nameserver Nameserver: sdns2.ovh.net Nameserver: ns368374.ovh.net
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•