Closed Bug 853612 Opened 11 years ago Closed 11 years ago

Update whois for webmaker.org

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: johns, Assigned: cliang)

Details

(Whiteboard: [triaged 20130322])

Hi,

Would you please point nameservers for webmaker.org to:
ns-1504.awsdns-60.org.
ns-1635.awsdns-12.co.uk.
ns-659.awsdns-18.net.
ns-292.awsdns-36.com.

Afterward, please assign this ticket to cyliang for removal of the zone file on Moz kit.
Thanks!
name servers updated for webmaker.org

 $ whois webmaker.org | grep -i "name server:n"
 Name Server:NS-1504.AWSDNS-60.ORG
 Name Server:NS-1635.AWSDNS-12.CO.UK
 Name Server:NS-659.AWSDNS-18.NET
 Name Server:NS-292.AWSDNS-36.COM


assigning ticket to cyliang to complete the DNS zone removal on ns{1-3}.mozilla.org 
as requested.
Assignee: server-ops-webops → cliang
Status: NEW → ASSIGNED
Whiteboard: [triaged 20130322]
cliang-07757:dnsconfig cliang$ svn commit -m "Deleting webmaker.org zone file (BZ 853612)"
[...]
Transmitting file data .
Committed revision 61908.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Had to revert this (mmm ... DNS recursion issues).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
:cyliang - anything i can assist you with?
:cturra - Thanks for the offer, but I think I only had to revert my change (deletion of the zone file).  I've got a "placeholder" zone file with NS records that point to the Route53 servers.  That should take care of issues with ns<x>.mozilla.com lookups for now and the zone file can be deleted after all records causing recursive lookups have been moved.
Looks like this got done (cf. Bug 884086)
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.