Closed Bug 657784 Opened 13 years ago Closed 13 years ago

add *.pub.build.mozilla.org subdomains

Categories

(Infrastructure & Operations :: RelOps: General, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

As part of bug 604688, we'd like to have a number of hostnames with the pub.build.mozilla.org prefix resolve both inside and outside the build domain.  They should all be CNAMEs for dm-wwwbuild01-ext, which should be an A record pointing to dm-wwwbuild01's external IP (63.245.208.186).  So:

$ORIGIN mozilla.org
dm-wwwbuild01-ext IN A 63.245.208.186

$ORIGIN build.mozilla.org
pub IN CNAME dm-wwwbuild01-ext.mozilla.org.

$ORIGIN pub.build.mozilla.org
buildapi IN CNAME dm-wwwbuild01-ext.mozilla.org.
clobberer IN CNAME dm-wwwbuild01-ext.mozilla.org.
clobberer-staging IN CNAME dm-wwwbuild01-ext.mozilla.org.
db IN CNAME dm-wwwbuild01-ext.mozilla.org.
trychooser IN CNAME dm-wwwbuild01-ext.mozilla.org.

As you can see, this doesn't require a new SOA - the dots are just part of the hostname, basically.

We will have a separate bug for adding additional internal-only cnames for things like clobberer and talos bundles.
Will work on these changes after the DNS overhaul on May 26th.
Assignee: server-ops-releng → arich
Ravi, I'd love if you'd double check that I set things up correctly if you have a chance.  What I did:

Added:

external/mozilla.org-mpt:dm-wwwbuild01-ext IN A  63.245.208.186
mpt-dmz/sj.mozilla.org:dm-wwwbuild01-ext IN A  63.245.208.186

(Not sure if those should have been added to a different zone file that exports to both internal and external).

Modified config/zones.public to include:

    zone "build.mozilla.org" IN {
        type master;
        file "zones/mozilla.org/build/public";
    };


Added the following to zones/mozilla.org/build/public:

$ORIGIN build.mozilla.org.

pub                     IN CNAME dm-wwwbuild01-ext.mozilla.org.

$ORIGIN pub.build.mozilla.org.

buildapi                IN CNAME dm-wwwbuild01-ext.mozilla.org.
clobberer               IN CNAME dm-wwwbuild01-ext.mozilla.org.
clobberer-staging       IN CNAME dm-wwwbuild01-ext.mozilla.org.
db                      IN CNAME dm-wwwbuild01-ext.mozilla.org.
trychooser              IN CNAME dm-wwwbuild01-ext.mozilla.org.
From that, my only worry is that build.mozilla.org won't resolve externally anymore (or, to put it another way, it surprises me you had to add the zonefile to the config).
I've reverted that change.
I think it's probably best to hand this over to netops for the time being since I think it's going to be tricky to fix this in the interim before we can get rid of build.mozilla.org as a CNAME.  I'm not sure where the best place for these changes would be at the moment.
Assignee: arich → network-operations
Component: Server Operations: RelEng → Server Operations: Netops
QA Contact: zandr → mrz
Ping?  I think this can be done with some $INCLUDEs, right?  This is blocking a bunch of other work on bug 604688, which is blocking fixing a lot of stuff for devs in MoTo and other remote offices.
Also, since this hasn't happened yet, I want to add one more for bug 657359, bringing the total to:

buildapi                IN CNAME dm-wwwbuild01-ext.mozilla.org.
clobberer               IN CNAME dm-wwwbuild01-ext.mozilla.org.
clobberer-staging       IN CNAME dm-wwwbuild01-ext.mozilla.org.
db                      IN CNAME dm-wwwbuild01-ext.mozilla.org.
trychooser              IN CNAME dm-wwwbuild01-ext.mozilla.org.
reports                 IN CNAME dm-wwwbuild01-ext.mozilla.org.
We haven't forgotten.  There are some outstanding issues (bug 659084) that we want to resolve before we apply these changes.  We were going to apply this after the large update that happened this morning anyhow.
I'm not authorized to see bug 659084 so can we get an update on when these public domain names will be available?  I'm doing a bunch of try work and would like to get trychooser.pub.b.m.o up and running as well as having the option to work on another developer/contributor facing dashboard.
I'll work on getting this finished - it's been a very low priority for me for a while, but I'll bump it up.  I think that the part ravi needed to fix (which had to do with having an SOA for build.mozilla.org) is finished.
dustin@Lorentz ~ $ host -tSOA build.mozilla.org
build.mozilla.org has no SOA record

So I think this is back in the realm of the possible for minions like me :)
Assignee: network-operations → dustin
Component: Server Operations: Netops → Server Operations: RelEng
Priority: -- → P2
QA Contact: mrz → zandr
I think this has been working since the SOA got removed.  I just added reports.
Yep, just verified that this resolves internally and externally:

reports.pub.build.mozilla.org. 300 IN	CNAME	dm-wwwbuild01-ext.mozilla.org.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.