Custom Domains Test

cp.broofa.com = "DNS Verified, but needs update"

Custom domain with legacy (AWS) A records. Clients will get to their website, but won't have valid SSL certs. User needs to update their DNS records as described in blog post

isVerified = true
aRecordStatus = Legacy
cnameRecordStatus = None

cp.broofa.com.		60	IN	A	52.40.196.217
cp.broofa.com.		60	IN	A	52.10.184.195

cpnew.broofa.com = "DNS Verified"

Domain has valid `CNAME` record, DNS nameserver replies with that, plus valid A records. I suspect this will be the most common case for custom subdomain setups.

isVerified = true
aRecordStatus = Valid
cnameRecordStatus = Valid

cpnew.broofa.com.	60	IN	CNAME	fair-sun-bedbug.codepen.app.
fair-sun-bedbug.codepen.app. 300 IN	A	172.66.42.242
fair-sun-bedbug.codepen.app. 300 IN	A	172.66.41.14

cp-a.broofa.com = "DNS Verified"

Domain has A records for cloudflare IPs, but no CNAME record. This is what we expect to see with apex domain setups that use DNS proxying, ALIAS or ANAME records

isVerified = true
aRecordStatus = Valid
cnameRecordStatus = None

cp-a.broofa.com.		60	IN	A	172.66.42.242
cp-a.broofa.com.		60	IN	A	172.66.41.14

cp-a-maybe.broofa.com = "Pending DNS setup"

Domain has a mixed "A" records (some valid, some invalid). The user would have to remove the invalid A records to resolve this.

isVerified = false
aRecordStatus = Invalid
cnameRecordStatus = None

cp-a-maybe.broofa.com.		60	IN	A	172.66.41.14
cp-a-maybe.broofa.com.		60	IN	A	1.1.1.1

cp-a-broken.broofa.com = "Pending DNS setup"

Domain has one or more A records for invalid IPs. Basically the DNS setup is borked.

isVerified = false
aRecordStatus = Invalid
cnameRecordStatus = None

cp-a-broken.broofa.com.		60	IN	A	1.1.1.1

drroberthorowitz.com = "DNS Verified"

Apex domain (setup with ALIAS record).

isVerified = true
aRecordStatus = Valid
cnameRecordStatus = None

[`dig` output pending]