I just happened to notice that I could reach ship-it-dev while not on the VPN. Looks like its DNS never got switched over: ➜ release-kickoff git:(master) host ship-it.mozilla.org ship-it.mozilla.org has address 10.8.81.228 ➜ release-kickoff git:(master) host ship-it.allizom.org ship-it.allizom.org has address 10.8.81.227 ➜ release-kickoff git:(master) host ship-it-dev.allizom.org ship-it-dev.allizom.org has address 220.127.116.11
i believe this is the expected result since it lives on our generic web cluster. access to the contents are behind LDAP authentication, which meet our security requirements for access management. is there a specific reason why you believe the site should not be accessible outside of the vpn?
Not really. I just figured it was the most correct thing to do in terms of keeping dev as close to production as possible. I've got no issue with it being public if that's preferred, though.
i just had a look through dns and see exactly that you're saying. there was an internal vip on the load balancer setup for dev, but it wasn't being used. i have adjusted that now. $ host ship-it-dev.allizom.org ship-it-dev.allizom.org has address 10.8.81.226 do you want give it a quick test for me to confirm everything is still functioning as expected.
Assignee: server-ops-webops → cturra
Whiteboard: [triaged 20130401]
Everything looks fine to me.
thnx for the confirmation and your clarification on this bug :) marking as r/fixed.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.