Fastly DNS

No. Fastly's documentation says Fastly does not provide a managed DNS service, so you still need a separate DNS provider to host the records and delegation. [Fastly routing documentation](https://www.fastly.com/documentation/guides/concepts/routing-traffic-to-fastly/)

For a subdomain such as `www.example.com`, Fastly normally provides a CNAME target from the TLS configuration. An apex such as `example.com` cannot use a normal CNAME, so Fastly provides A and AAAA anycast records for the DNS provider. [Fastly apex-domain guide](https://www.fastly.com/documentation/guides/full-site-delivery/domains-and-origins/using-fastly-with-apex-domains/)

Fastly's edge network can improve delivery after traffic reaches Fastly, while DNS only helps resolve the hostname to the service. Using Fastly anycast or a CNAME can route requests toward the edge, but it does not replace caching, origin tuning, or a separate authoritative DNS service.

You must still publish the CNAME, A, or AAAA records supplied by Fastly at your DNS provider and keep the domain delegation working. Fastly manages the TLS configuration for its edge service, but your DNS provider remains responsible for the domain's records and related DNS settings. [Fastly routing documentation](https://www.fastly.com/documentation/guides/concepts/routing-traffic-to-fastly/)