An alias zone is a zone type that does not have its own zone file. Instead, it bases itself on another Edge DNS (base) zone’s (either primary or secondary) resource records. In other words, the zone data is a copy of another Edge DNS zone. You can modify data in alias zones by changing the "parent" or "alias-of" zone.
An organization may have several hundred vanity or brand domains that need to be registered and for which DNS services are required, but for which DNS is configured identically to a base zone. In these cases you can configure one base zone, point many aliases to the base zone, and easily manage any DNS changes by updating only the base zone file.
Alias zones generate their own log lines independent of their base zone. To receive logs with alias zone traffic, you need to configure log delivery for each alias zone individually.
Alias zones are compatible with:
- Zone apex mapping
- Top level CNAME (This can only be configured by technical support.)
- Vanity name servers (These name server records should not be from a base zone with aliases.)
When using these features, pay attention before adding alias zones. Check the property receiving the traffic in Property Manager: make sure the appropriate hostnames are configured and that the correct redirects are set up. If HTTPS support is required, make sure the certificates are correctly configured. With a certificate that supports subject alternative names (SAN) this typically means adding the domain apex to the certificate.
Alias zones are not compatible with DNSSEC. Each DNSSEC zone requires its own resource record signatures. Base zones with DNSSEC enabled can’t have any aliases.