# A test address without your organisation in it

Brewless names every environment after your organisation, application and environment. test_address: short or random leaves the organisation out.

## In short

- Every Brewless environment gets a test address and a pull zone named after the organisation, the application and the environment, such as acme-shop-production.
- That name ends up in places your customer sees, like the CNAME or ALIAS record you send them for their own domain.
- test_address short leaves the organisation out of the test address and the pull zone, and test_address random puts a fixed random value in its place.
- A pull zone at bunny.net cannot be renamed, so Brewless replaces it, but only while none of your domains leads to the old one yet.
- Each name under the test domain belongs to one environment, so a short name someone else has already gets a short code at the end.

Deploy an application with [Brewless](/) and it gets a test address straight away, before you have a domain of your own: `acme-shop-production.brewless.dev`. Put bunny.net in front and the pull zone is called the same: `acme-shop-production.b-cdn.net`. That is clear for you. It is less pleasant when you build sites for customers and the first thing you send them is a DNS record with your own company's name in it.

Since today, `test_address` in `brewless.yml` decides what goes in front of the application and the environment.

## Can I leave my organisation out of the test address?

Yes. Set `test_address: short` on the environment and the next deploy gives it `shop-production.brewless.dev` and a pull zone called `shop-production`. Set `test_address: random` and both start with a random value instead, such as `k3x9q2ab-shop-production`. Without the setting nothing changes.

```yaml brewless.yml
environments:
  production:
    test_address: short
```

## Where the name shows up

An environment has three names that are made of the same parts:

| Name | Default | `short` |
| --- | --- | --- |
| Test address | `acme-shop-production.brewless.dev` | `shop-production.brewless.dev` |
| Files address under the test domain | `cdn-acme-shop-production.brewless.dev` | `cdn-shop-production.brewless.dev` |
| Pull zone at bunny.net | `acme-shop-production.b-cdn.net` | `shop-production.b-cdn.net` |

The pull zone is the one that travels. When you add a domain of your own, `brewless domain:add` tells you which record to make, and for the domain itself that is an `ALIAS` to the pull zone:

```text
ALIAS  shop.example.eu  ->  shop-production.b-cdn.net
```

Whoever keeps the DNS for that domain sees that value. With `short` or `random` it no longer says who built the site.

## Why short and random both exist

Every name under the test domain belongs to exactly one environment. Brewless keeps a central list of them, so a name never leads to two environments, and a report of abuse on brewless.dev can still be traced back to an organisation when its name is not in the address.

That list is first come, first served. Your `shop-production` is free until someone else asks for it; then your environment gets the name with a short code at the end, the same way two environments with the same name always did. A common name like `website-production` may be gone already. `random` does not have that problem: the eight letters and digits are your environment's own, given once, and the name stays the same with every deploy.

## Why the pull zone is replaced, not renamed

A pull zone at bunny.net keeps the name it was made with. So when `test_address` asks for another name, the deploy makes a new pull zone, moves the hostnames of the old one over, and deletes the old pull zone and the one for files. The pull zone for files is made again under the new name in the same deploy, and the edge settings are applied to the new pull zone as they are on every deploy.

That is only safe while nobody reaches the site through the old pull zone. As soon as one of your domains is active, its DNS leads to the old name, and a new pull zone would take the site offline until the DNS follows. So Brewless only replaces the pull zones while none of your domains is **Active** and no files address of your own has its certificate. Otherwise the pull zones keep their names and the deploy tells you; the test address changes all the same.

> [!TIP]
> Decide on `test_address` before you send anyone a DNS record. A domain that is still **Waiting for DNS** follows the new name straight away, in the console and in `brewless domain:list`, so the record you send is the new one.

The details are in the documentation on [domains and the test address](https://docs.brewless.eu/running/domains#without-the-organisation-in-the-name).

## Frequently asked questions

### Where does my organisation's name show up in an environment?

In the test address under brewless.dev, in the files address under the test domain, and in the name of the pull zone at bunny.net. The last one is the value of the CNAME or ALIAS record a domain of your own needs, so it is the one your customer sees.

### What is the difference between short and random?

short gives shop-production, random gives something like k3x9q2ab-shop-production. A short name goes to whoever asks for it first, so a common one may be taken; the random value is the environment's own and stays the same with every deploy.

### Can I switch an environment that already has a domain?

The test address switches on the next deploy either way. The pull zone only gets a new name while none of your domains is active on the old one, because a new pull zone would take the site offline until the DNS follows. Otherwise the deploy keeps it and says so.

### Do I have to change anything in my Laravel application?

No. brewless/laravel answers on any name under the test domain, so the new test address works as soon as the deploy is done.

Source: https://brewless.eu/blog/test-address-without-organisation-name
