Resolves for me. Can you go to terminal/CMD and run the dig/nslookup command and screenshot the output here?
what are the parameters for nslookup ?
Your screenshot looks like you’re using a local resolver. Try:
nslookup woolyss.com 1.1.1.1
I’m using DNSCrypt-proxy 2 with Cloudflare + Google for DNS
Here you go - https://i.gyazo.com/113584cd9b08bb555cb69cc3b9d8e66f.png
Does anything resolve for you through 1.1.1.1? And…try this:
dig +short CHAOS TXT id.server @1.1.1.1
Yes all other domains resolve through 1.1.1.1, how do you think I browse internet or reply here ? 
Does dig work on Windows 10 ?
You must be Linux, as dig is not a known command on Windows.
With a Mac? 
Try this then:
nslookup -class=chaos -type=txt id.server 1.1.1.1
With a Mac?
Good one man
Try this then:
nslookup -class=chaos -type=txt id.server 1.1.1.1
It says BOM- https://i.gyazo.com/05f317a10217371c70652e7121066b00.png
Open up a Support Ticket and let them know you can’t resolve that domain through BOM and that LAX works.
Login to Cloudflare and then contact Cloudflare Support
Can I just link this thread so they can see the whole story here ?
Sorry, can’t find any option to file a support ticket, please expand on how to do that ?
Let’s see…at that Support page, there’s a Get More Help link.
Oh, and I think that’s about all. The next screen should start asking you questions. (Usually there are more steps to getting to the Ticket process).
Or you can just email support AT Cloudflare DOT com if you have an account. Send from the email address associated with your account.
Thanks, just got done. ticket number is 1614011.
Also this is my debug information from https://1.1.1.1/help –
So what next ?