You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/manual/transition-a-site.html.md
+5-45Lines changed: 5 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,47 +35,7 @@ The organisation that owns the site determines several things:
35
35
36
36
Extra organisations can be added later.
37
37
38
-
### 1) Verify the domain (for *.gov.uk domains only)
39
-
40
-
For security reasons, Fastly require that *.gov.uk domains are verified before they can be added to our Fastly account.
41
-
42
-
> When the steps below are not completed, there will be a `Domain 'gov.uk' is owned by another customer` error when the terraform apply command runs.
43
-
>
44
-
> This error results in any further transitioned sites being blocked until the verification is completed. Therefore this step must be completed before moving onto the next step.
45
-
46
-
We need to:
47
-
48
-
1. Obtain the TXT record by submitting a Fastly support request. You will need to provide the 'Production bouncer' service ID and the subdomain you want to add.
49
-
50
-
Support requests are created on the [Fastly Support Case Management](https://support.fastly.com/s/case-management) website. You must login before creating the request, to verify you can perform actions on GOV.UK's account.
51
-
52
-
You will need the 'Service ID', which is obtained by logging into [Fastly](https://manage.fastly.com/home) and navigating to the 'Production Bouncer' service, then locating the value labelled 'ID' on the service page.
53
-
54
-
For the request type, select 'Other' and the subject can be 'Verify a subdomain'.
55
-
56
-
An example request may be as follows:
57
-
58
-
> Hi,
59
-
>
60
-
> Similar to our previous requests, we would like to add a new *.gov.uk domain to our service and understand that you now require explicit verification.
61
-
>
62
-
> Can you please provide me with the details of a TXT record we need to add to manually verify the addition?
63
-
>
64
-
> Details below:
65
-
>
66
-
> Service ID: [add the service ID here]
67
-
>
68
-
> Subdomain: [add the domain here]
69
-
>
70
-
> Kind regards,
71
-
>
72
-
> [your name]
73
-
74
-
1. If the domain's DNS is managed by GOV.UK: add the DNS record to [govuk-dns-tf](https://github.com/alphagov/govuk-dns-tf) and apply terraform configuration. If the domain's DNS is managed by the department: send the TXT record to the department and ask them to add this record to the DNS.
75
-
76
-
> It's not possible to add additional records on a subdomain if a CNAME already exists. In such case Fastly accepts setting the record on a subdomain prefixed with `_fastly` as a proof of ownership. See an [example code change][code change].
77
-
78
-
### 2) Add a site to the Transition app
38
+
### 1) Add a site to the Transition app
79
39
80
40
If you have the Site Manager permission for Transition, you will see an "Add a transition site" button on each organisation page. Follow the instructions on that form to add a site, using the following as guidance for common cases.
81
41
@@ -111,25 +71,25 @@ Use the following settings for the site. All other form fields can be ignored.
111
71
112
72
See the ['Configure transition mappings for a site' guidance](/manual/configure-transition-mappings.html).
113
73
114
-
### 3) Get the domain owner to lower the TTL on the DNS records a day ahead
74
+
### 2) Get the domain owner to lower the TTL on the DNS records a day ahead
115
75
116
76
> This step is only required if the domain currently has DNS records.
117
77
118
78
In order to cleanly switch the domain from the old site, the TTL needs to be low enough that there isn't a significant period where some users will get the old site and some get the new one. This is important for several reasons, including user experience and giving a professional impression to stakeholders. We normally ask for this to be done a day in advance, and to be lowered to 300 seconds (5 minutes). It can be raised again once everyone is happy there is no need to switch back - normally the day after.
119
79
120
-
### 4) Add the domain to Fastly
80
+
### 3) Add the domain to Fastly
121
81
122
82
Manually trigger `govuk-fastly-bouncer-production` 'Plan and apply' run in [Terraform Cloud UI](https://app.terraform.io/app/govuk/workspaces/govuk-fastly-bouncer-production/runs). Review the plan with changes to `module.bouncer-production.fastly_service_vcl.service` and apply the configuration.
123
83
124
84
> A periodic cron job runs to populate the DNS records cached in the Transition app. For newly added domains, the DNS will be empty until the cron job next runs. Due to [this line of code](https://github.com/alphagov/transition/blob/8a532735ce8e61731986fd580a5d6ca1552e095f/app/controllers/hosts_controller.rb#L3C14-L3C49), the domain will not be added to Fastly if there are no cached DNS records. The `transition-import-dns` cron job can be run manually in [the Argo user interface](https://argo.eks.production.govuk.digital/applications/cluster-services/transition).
125
85
>
126
86
> If the domain currently has no DNS records (e.g. it is brand new), you should request the domain's owner point the DNS to us (see next step) before running this Terraform project, else the domain will not be added.
127
87
128
-
### 5) Obtain a TLS certificate
88
+
### 4) Obtain a TLS certificate
129
89
130
90
You'll need to create a TLS certificate in Fastly, otherwise users will see a certificate error when being redirected from an external HTTPS URL to GOV.UK via Bouncer. Read how to [request a Fastly TLS certificate][].
131
91
132
-
### 6) Change the domain's DNS to point at Bouncer
92
+
### 5) Change the domain's DNS to point at Bouncer
133
93
134
94
Once the transition is ready to be deployed, the domain must be pointed at Bouncer.
0 commit comments