537 DNS Resolution Error
The HTTP 537 DNS Resolution Error status code is an unofficial server error specific to Edgio (formerly Layer0), returned when the proxy is unable to resolve the origin hostname through DNS.
Usage
Edgio operates as a content delivery network with serverless compute at the edge. When a request arrives at an Edgio POP (point of presence), the platform resolves the origin hostname to route the request upstream. A 537 response means DNS resolution for the hostname failed.
Common causes include:
- The origin hostname contains a typo or does not exist in DNS.
- DNS records for the origin expired or were deleted.
- The DNS provider is experiencing an outage.
- A recently changed DNS record has not propagated to the resolvers used by Edgio's infrastructure.
The error originates within Edgio's proxy layer before the request reaches the origin server. The origin never receives the request.
SEO impact
Search engines treat 537 responses as server errors. Persistent errors cause crawlers to reduce crawl frequency and eventually drop affected URLs from the index.
Example
A client requests a page through Edgio, but the origin hostname configured in the project does not resolve.
Request
GET /products HTTP/1.1
Host: www.example.re
Accept: text/html
Response
HTTP/1.1 537 DNS Resolution Error
Content-Type: text/html
x-0-status: eh=537
<html>
<head>
<title>537 DNS Resolution Error</title>
</head>
<body>
<h1>537 DNS Resolution Error</h1>
<p>The proxy was unable to resolve the origin
hostname through DNS.</p>
</body>
</html>
How to fix
Verify the origin hostname in the Edgio project
configuration matches an existing DNS record. Run
dig or nslookup against the configured hostname
to confirm resolution:
dig origin.example.re
If the hostname resolves locally but Edgio still returns 537, the DNS change has not propagated to Edgio's resolvers. Lower the TTL on the DNS record and wait for propagation. Typical propagation completes within minutes for low-TTL records.
Check the DNS provider's status page for outages. A provider-side failure prevents all resolvers, including Edgio's, from obtaining a valid response.
Review the x-0-status response header for
additional context. This header shows the status
code at each POP component involved in processing
request, helping pinpoint where resolution failed.
If the origin uses a private or internal DNS zone not reachable from public resolvers, ensure the Edgio project is configured with a publicly resolvable hostname or uses an IP address directly.
Takeaway
The 537 DNS Resolution Error status code is an unofficial server error specific to Edgio, returned when the platform's proxy fails to resolve the origin hostname through DNS. The fix is typically correcting the hostname or waiting for DNS propagation.