Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding the www.digitalgov.gov record to AWS/Route53 #145

Merged
merged 1 commit into from
Oct 26, 2017
Merged

Adding the www.digitalgov.gov record to AWS/Route53 #145

merged 1 commit into from
Oct 26, 2017

Conversation

jeremyzilar
Copy link
Contributor

We are going to ask GSA IT to point the www sub-domain of digitalgov.gov at CloudFront for now — thus, not having to move all the sub-domains that are currently associated with digitalgov.gov at this time.

This also means that we’ll be relying on the apache config that SITES program currently has in place to redirect the root digitalgov.gov to www.digitalgov.gov. If/when that goes away after Jan 31, we’ll need to figure out another solution.

For the product, this is an acceptable solution since we’ll be moving DigitalGov.gov over to the digital.gov domain in the next 3-5 months.

@wslack
Copy link
Member

wslack commented Oct 26, 2017

@erik-burgess is this formatted correctly? Also, should this be an ALIAS record?

@wslack
Copy link
Member

wslack commented Oct 26, 2017

@jeremyzilar I approved but just make sure it aligns to other formatting plz.

@jeremyzilar
Copy link
Contributor Author

@wslack I believe the formatting is the same as the others on the page.
The only thing I added in was a comment # www.digitalgov.gov to indicate which record is for our site.

I am not touching any of the existing records for openopps.

@wslack wslack merged commit e3fe2fb into 18F:deploy Oct 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants