DomainMapper complains path on Adressable Knative Broker

Following this guide:
https://knative.dev/docs/serving/services/custom-domains/

 
I set these values in the "network" ConfigMap:
```yaml
...
autocreateClusterDomainClaims: "true"
defaultExternalScheme: https
domainTemplate: '{{.Name}}-{{.Namespace}}.{{.Domain}}'
ingress.class: kourier.ingress.networking.knative.dev {code}
...
```

So I created a `DomainMapping` for a Knative Broker:

```yaml
apiVersion: serving.knative.dev/v1alpha1
kind: DomainMapping
metadata:
name: default-borker.apps.my-server.somewhere.com
namespace: default
spec:
ref:
name: default
kind: Broker
apiVersion: eventing.knative.dev/v1
```

But I am getting this:

```
...
Status:
Address:
URL: default-borker.apps.my-server.somewhere.com
Conditions:
Last Transition Time: 2022-03-01T11:36:01Z
Message: autoTLS is not enabled
Reason: TLSNotEnabled
Status: True
Type: CertificateProvisioned
Last Transition Time: 2022-03-01T11:36:01Z
Status: True
Type: DomainClaimed
Last Transition Time: 2022-03-01T11:36:01Z
Message: Ingress has not yet been reconciled.
Reason: IngressNotConfigured
Status: Unknown
Type: IngressReady
Last Transition Time: 2022-03-01T11:36:01Z
Message: resolved URI "http://broker-ingress.knative-eventing.svc.cluster.local/default/default" contains a path
Reason: ResolveFailed
Status: False
Type: Ready
Last Transition Time: 2022-03-01T11:36:01Z
Message: resolved URI "http://broker-ingress.knative-eventing.svc.cluster.local/default/default" contains a path
Reason: ResolveFailed
Status: False
Type: ReferenceResolved
Observed Generation: 1
URL: default-borker.apps.my-server.somewhere.com
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal FinalizerUpdate 40m domainmapping-controller Updated "default-borker.apps.my-server.somewhere.com" finalizers
Warning InternalError 2m14s (x20 over 40m) domainmapping-controller resolved URI "http://broker-ingress.knative-eventing.svc.cluster.local/default/default" contains a path
```
 
The guide does mention:
> ...as long as they conform to the Addressable contract...

IMO this error "contains a path" does break that

No source file or test is named. Start with the domainmapping-controller event and the Addressable reference resolution for the Broker URI, then reproduce the manifest and network ConfigMap values from the report. Done means the path error has a confirmed resolution and the DomainMapping reaches the expected ready state.

Written by the indexing model from the issue text.