1

We updated CNAME on a production website, after updating it website showed "server's DNS address could not be found" message for about 8 mins. Could this be because of the change in CNAME?

Dhawal
  • 13

3 Answers3

1

Did you change it as a delete/create or as a update? Delete/create could cause an outage. A straight update is safe and does not result in a not-found message.

Jason Martin
  • 5,193
1

From our discussion in the comments, it looks like you attempted to set an IP address target using a CNAME record. This record type is only intended to alias the host resources of one name to another, and the value will be interpreted as a name even if you input an IP address.

Input:

 $ORIGIN example.com.
 www     IN CNAME 203.0.113.0

Effective output with FQDNs:

 $ORIGIN example.com.
 www.example.com.     IN CNAME 203.0.113.0.example.com.

This mistake almost always results in NXDOMAIN (barring wildcard matching), as the target is very unlikely to exist.

Andrew B
  • 33,868
0

If you have added the CNAME records for your domain with the record name www or with a blank record name, your website may not be accessible until the DNS records are propagated.