Commit c59d18f7 authored Jul 09, 2026 by Erik Lentz

Move Domain Registration to InfraSec

parent 811e6f76

content/handbook/company/infrastructure-standards/realms/sandbox/_index.md

+1 −1

Original line number	Diff line number	Diff line
		@@ -130,7 +130,7 @@ Self-hosted application infrastructure is determined on a case-by-case basis and

		## Domain Names

		See the [Domain Names and DNS Records](https://internal.gitlab.com/handbook/it/it-self-service/it-guides/domains-dns/) IT guide internal handbook page for more details.
		See the [Domain Names and DNS Records](https://internal.gitlab.com/handbook/security/product_security/infrastructure_security/guides/domains-dns/) InfraSec guide internal handbook page for more details.

		## Terraform Environments

content/handbook/marketing/developer-relations/workflows-tools/cloud-resources.md

+1 −1

Original line number	Diff line number	Diff line
		@@ -30,7 +30,7 @@ Technical owners: @johncoghlan @dnsmichi

		1. All Developer Relations team members can manage resources in Google Cloud in the [community-group project](https://console.cloud.google.com/kubernetes/list/overview?hl=en&project=group-community-a29572) using the `Editor` role.
		- This access is not provisioned by default. Create an [access request](/handbook/security/corporate/end-user-services/access-requests/access-requests/) to add/remove team members (example: [group update AR](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/13320)).
		1. Google Cloud/AWS also allows to [register domains that are not trademarked](https://internal.gitlab.com/handbook/it/it-self-service/it-guides/domains-dns/#non-trademark-domain-names) (internal) and use the domains for demo setups.
		1. Google Cloud/AWS also allows to [register domains that are not trademarked](https://internal.gitlab.com/handbook/security/product_security/infrastructure_security/guides/domains-dns/#non-trademark-domain-names) (internal) and use the domains for demo setups.

		### Demo environments

content/handbook/support/workflows/test_env.md

+2 −2

Original line number	Diff line number	Diff line
		@@ -351,9 +351,9 @@ Setting up a test Keycloak instance might be useful when learning & troubleshoot

		### DNS for test instances

		See the handbook for IT policies about [Domain Names and DNS Records](https://internal.gitlab.com/handbook/it/it-self-service/it-guides/domains-dns/).
		See the handbook for InfraSec policies about [Domain Names and DNS Records](https://internal.gitlab.com/handbook/security/product_security/infrastructure_security/guides/domains-dns/).

		If you wish to test resources using a real domain name (instead of an IP address, e.g. for testing TLS certificates), you can purchase a domain name of your choice (without GitLab trademarks) that is paid for by GitLab through your Sandbox Cloud AWS account or GCP project. Instructions and guidelines can be found [here](https://internal.gitlab.com/handbook/it/it-self-service/it-guides/domains-dns#non-trademark-domain-names).
		Instructions and guidelines can be found in the [non-trademark domain name instructions](https://internal.gitlab.com/handbook/security/product_security/infrastructure_security/guides/domains-dns/#non-trademark-domain-names).

		## Securing Cloud Testing Environments