Skip to content →
Log in

Domains and DNS

Verify identity domains and enable private service discovery.

Two Settings pages share the word DNS. Settings → Domains proves you own an email domain so it can be used for SSO routing and as a private DNS suffix. Settings → DNS turns on service discovery so connected devices can reach private services by name.

Before you start#

  • Domains needs sso:manage. DNS needs tenant:update. Under the built-in roles both belong to Owner.
  • Domain verification needs access to the public DNS zone for the domain so you can add a TXT record.
  • Service discovery resolves names for private services. It does not decide who may reach them. Access policy still applies. It is also separate from Secure Web DNS filtering.

Add and verify a domain#

  1. Open Settings → Domains.
  2. Under Add Domain, type the domain (for example example.com) and choose Add. The console lowercases it.
  3. Under Your Domains, the new row shows Unverified. Choose Verify Domain.
  4. The panel shows the record to publish: Name _pulseha-verification.<your domain>, Type TXT, Value the token (it starts with pulseha-verify-). Use Copy to copy the token.
  5. Create that TXT record at your DNS provider.
  6. Back in the console, choose Check DNS.

Domains page with a verified domain and an unverified domain showing its TXT record

Domains with one Verified domain and one Unverified domain after choosing Verify Domain: the TXT record name, type and value to publish.

You should see “<domain> verified successfully!” and the chip change to Verified. The panel notes that DNS changes may take up to 48 hours to propagate. If the check fails, wait and retry.

To remove a domain, use the bin icon and confirm Delete. The dialog warns that verification is revoked and features using the domain need reconfiguring.

Enable service discovery#

  1. Open Settings → DNS.
  2. Under Service Discovery, turn on Enable DNS.
  3. Under Configuration, pick a Domain Suffix. The list contains pulseha.internal plus every verified domain.
  4. Leave Auto-generate DNS Names on if you want names created from service names when no custom name is set.
  5. Review Service Records. Each service shows its DNS Name as <label>.<suffix> and its Address.
  6. Choose Save Changes.

DNS settings page with service discovery enabled and the service records table

DNS with service discovery enabled: the domain suffix, auto-generated names, and the Service Records table listing each service by DNS name and address.

You should see “DNS settings saved”. With DNS enabled, services become resolvable by those names on connected devices. A service with no custom name and auto-generation off shows No DNS name.

Generated labels are derived from the service name: lowercased, runs of non-alphanumeric characters replaced with a single hyphen, leading and trailing hyphens trimmed, and cut to 63 characters.

Reference#

Domain fields and states:

ItemValue
TXT record name_pulseha-verification.<domain>
TXT record typeTXT
TXT record valueToken from Verify Domain, prefix pulseha-verify-
ChipVerified or Unverified
Accepted domain formatLowercase letters, digits, dots and hyphens, starting and ending with a letter or digit

DNS settings:

SettingDefaultMeaning
Enable DNSOffPublishes service names to connected devices.
Domain Suffixpulseha.internalSuffix appended to every label. Must be pulseha.internal or a verified domain.
Auto-generate DNS NamesOnDerive a label from the service name when none is set.

Service Records columns: Service, DNS Name, Address.

Troubleshooting#

  • “invalid domain format”. The control plane only accepts lowercase letters, digits, dots and hyphens. Remove https://, paths and trailing dots.
  • “domain already exists”. The domain is already in Your Domains on this tenant. Verify the existing row instead of adding it again.
  • “DNS TXT record not found for <domain>.” The lookup of _pulseha-verification.<domain> returned nothing. Confirm the record name has the underscore prefix and that it has propagated.
  • “TXT record found but does not match the verification token.” The published value differs from the current token. Copy it again from Verify Domain. Starting verification again issues a new token and the old one stops matching.
  • “no verification token set; initiate verification first”. Choose Verify Domain before Check DNS.
  • “domain suffix must be a verified domain or pulseha.internal”. The chosen suffix lost verification or was deleted. Verify it under Domains or fall back to pulseha.internal.
  • A custom suffix is missing from the list. Only Verified domains appear. The hint links to Settings → Domains.
  • A service shows No DNS name. Set a name on the service, or turn on Auto-generate DNS Names, then Save Changes.
  • Names resolve in the table but not on a device. Confirm Enable DNS is on and saved, then check the device is connected under Network → Devices.