What's an ALIAS record? - DNSimple Help

ALIAS Records

Table of Contents

What’s an ALIAS record?

An ALIAS record is a virtual record type DNSimple created to provide CNAME-like behavior on apex domains .

For example, if your domain is example.com, and you want it to point to a host name like myapp.herokuapp.com, you can’t use a CNAME record, but you can use an ALIAS record. The ALIAS record will automatically resolve your domain to one or more A records at resolution time, and resolvers see your domain as if it had A records.

How ALIAS records work

The DNSimple name servers are based on an open source Erlang DNS server we developed with the help of others in the DNS community. The erl-dns server provides a mechanism for plugging in custom handlers. We use that extension mechanism for providing an ALIAS handler. Each time a request hits the DNSimple name servers for either an A or AAAA record type, the custom handler is invoked and attempts to resolve the ALIAS into its appropriate IPv4 or IPv6 address. It does this by asking a resolver to resolve the domain. We’re running PowerDNS’s resolver locally on each system for this purpose.

If the resolution succeeds, the handler extracts the A and AAAA records and returns them to the erl-dns server process, which then goes on its way. It also stores the result in an in-memory cache.

If the resolution fails, for example due to a timeout, then the cached response is returned, if one exists. We have the request timeout set to 500 milliseconds, which is considered low. In the future, we may lower it further. If there’s no response in the cache, the request is retried again, up to the maximum number of retries. If the request ultimately fails, we return an empty result set.

Resolving ALIAS records with secondary DNS

To support secondary DNS servers, especially ones that connect to us and pull zones using AXFR, we must resolve the ALIAS differently. We resolve it as part of the secondary DNS setup process, then run a scheduled job to update the ALIAS record at secondary name servers by resolving them again, removing the old records, and writing the new records to our zone transfer database. We then send a NOTIFY message to the appropriate secondary name servers, letting it know a change has been made.