I have 100 sites down due to 1016 Error?

They all have CName pointing to the Cloudways server and i am suddenly getting a 1016 error on all sites???

Hey,

Sound like Cloudways server is down :slight_smile:

1 Like

I’m also getting the 1016 error on several dozen sites

Server is fine and up - if i change cname to an arecord and point it comes back up

Can anybody post here a domain which is affected? :slight_smile:

https://wcportland.com/

https://localfresh.com/

http://www.algomamotel.com/

Not mine, but just say another one:

Anyone know how to get Cloudflare’s attention on this?

I have over 300 sites affected all in all now and though changing the CName records to an A record and pointing directly to the IP address seems to fix it, that’ a lot of manual work

I have already escalated it to CSUP.

2 Likes

I am only seeing A record setups around for Cloudways, which might make it a change on their end. Can anyone post the CNAME target? Or a tutorial showing CNAME setup instructions?

Here’s out business site localfresh.com cname points to: wordpress-156085-1601897.cloudwaysapps.com

Yeah, it doesn’t resolve at all. It’s a change on their end…

% dig wordpress-156085-1601897.cloudwaysapps.com @8.8.8.8

; <<>> DiG 9.10.6 <<>> wordpress-156085-1601897.cloudwaysapps.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14887
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;wordpress-156085-1601897.cloudwaysapps.com. IN A

;; AUTHORITY SECTION:
com.			889	IN	SOA	a.gtld-servers.net. nstld.verisign-grs.com. 1651622868 1800 900 604800 86400

;; Query time: 93 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed May 04 02:08:14 CEST 2022
;; MSG SIZE  rcvd: 144
2 Likes

Whose end? CF or CW?

Cloudways, of course. Their domain doesn’t resolve… :man_shrugging:

Cloudfalre won’t be able to invent a record for a non-resolving domain.

It does from 1.1.1.1 and from the authoritative nameservers:

% dig  wordpress-156085-1601897.cloudwaysapps.com @ns-854.awsdns-42.net

; <<>> DiG 9.18.2 <<>> wordpress-156085-1601897.cloudwaysapps.com @ns-854.awsdns-42.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64500
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;wordpress-156085-1601897.cloudwaysapps.com. IN A

;; ANSWER SECTION:
wordpress-156085-1601897.cloudwaysapps.com. 900	IN A 104.196.230.84
1 Like

It does now. It didn’t before…

It is very intermittent. I guess they had an issue, which is now resolving.

I seem to be getting 1 out of 3 requests come back as failed from 8.8.8.8. Way worse on 1.1.1.1.

I’m not even getting NS records for the cloudwaysapp.com zone on 1.1.1.1.

1 Like

thanks for the help Matteo - went back to Cloudways support and they finally fessed up to it:

“Some of our customers faced same issue as because of the DNS is not working currently on different location and our team is already working on it to fix it”
So basically our team is continuously in communication with the Cloudflare support team for the permanent fix for all the domains."

This is what I’m getting from my chat over at Cloudways:

Y> es I understand.

But we use Cloudflare for the cloudwaysapps.com domains.
So, technically its their issue.

We are following up with them in the background. Since its a DNS issue, It could take some time to be resovled.