Merge pull request #4484 from alphagov/dns-docs

Update references to DNS delegation / domain verification documentation

source/manual/common-aws-tasks-for-2nd-line-support.html.md

@@ -84,13 +84,4 @@ View the documentation on [how to backup and restore in AWS RDS].
 
 [how to backup and restore in AWS RDS]: /manual/howto-backup-and-restore-in-aws-rds.html
 
-## Learn
-
-### How do we do DNS?
-
-GOV.UK is effectively a DNS registrar for some third-level domain names, for
-example service.gov.uk.
-
-See [how GOV.UK does DNS](/manual/dns.html).
-
 [govuk-aws]: https://github.com/alphagov/govuk-aws

source/manual/dns.html.md

@@ -7,18 +7,14 @@ layout: manual_layout
 parent: "/manual.html"
 ---
 
-GOV.UK is responsible for managing several DNS zones. For documentation on updating DNS, see the [DNS change request and hostmaster](https://drive.google.com/drive/search?q=-%20type:document%20title:%22Tech%202nd%20Line%20-%20Handle%20Tickets%20on%20DNS%20Change%20request%20hostmaster%40%22) doc for Technical 2nd Line.
+> For **Technical 2nd Line documentation** on when and how to respond to DNS delegation and domain verification requests, read the [DNS change request and hostmaster Google doc](https://drive.google.com/drive/search?q=-%20type:document%20title:%22Tech%202nd%20Line%20-%20Handle%20Tickets%20on%20DNS%20Change%20request%20hostmaster%40%22).
 
-In most cases, zones are hosted by AWS (Route 53) and Google Cloud Platform (Cloud DNS). See [Amazon Route53 vs Google Cloud in the govuk-dns-tf README](https://github.com/alphagov/govuk-dns-tf#amazon-route53-vs-google-cloud)
+GOV.UK is responsible for managing several DNS zones, spanning a number of `*.gov.uk` domains. As of February 2024, there are 45 hosted zones, configuring many hundreds of domains. A list of hosted zones is retrievable from a terminal using:
 
-As of December 2022, there are 61 hosted zones. A list is retrievable from a terminal using:
-
-```
+```sh
 gds aws govuk-production-poweruser -- aws route53 list-hosted-zones | grep Name
 ```
 
-Some individual records within these zones are managed by other teams.
-
 ## Records for GOV.UK systems
 
 We use a few domains:

source/manual/zendesk.html.md

@@ -109,19 +109,7 @@ review and assign to the `3rd Line--GOV.UK Product Requests` Zendesk group.
 
 ## DNS delegation tickets
 
-As of October 2022, Technical 2nd line may be asked to process DNS delegation requests. This used to be handled by a dedicated `3rd Line--GDS Reliability Engineering` Zendesk queue, which has now been merged into `2nd Line--GOV.UK Alerts and Issues`.
-
-The requests will look something like the following:
-
-> Please delegate the following to `something.service.gov.uk`
-> `nameserver1.example.com`
-> `nameserver2.example.com`
-
-The workflow for these requests is that a requester emails a particular email address, which creates a Zendesk ticket for the GOV.UK Policy and Strategy team. The request is then signed off and routed to us. We then double-check with someone from GOV.UK Policy and Strategy that the change has been agreed, then add/change the necessary DNS records (see [example](https://github.com/alphagov/govuk-dns-config/pull/854/files)) and respond to the requestor via the ticket.
-
-Note that some requests come directly via the [hostmaster Google group](https://groups.google.com/a/digital.cabinet-office.gov.uk/g/hostmaster). If you are in any doubt about the legitimacy of a request, reassign the ticket to `3rd Line--Policy and Strategy` and add an internal note asking them.
-
-For actioning these requests, [read our DNS documentation](/manual/dns.html).
+[Read our DNS documentation](/manual/dns.html) to find out more about these requests and how to action them.
 
 ## Automated requests from Amazon ACM or AWS Certificate Manager