4 ms·
> if you signed up via a hosting partner then you may have gotten a > CNAME that...SNIP...will now resolve directly from your domain to an > IP address. Thi
by dfc 13y ago
> if you signed up via a hosting partner then you may have gotten a
> CNAME that...SNIP...will now resolve directly from your domain to an
> IP address. This makes DNS resolution a bit faster and also better
> obscures the fact that you're using CloudFlare.
To what end are we obscuring the use of cloudflare? And how useful is the "cloudflara obscura" if the responses are being served by the cloudflare machines listed in the NS records?
dfc@fob-xray:~$ dig +short ns nasdaqprivatemarket.com
jill.ns.cloudflare.com.
igor.ns.cloudflare.com.
dfc@fob-xray:~$ dig +short ns skyprep.com
mark.ns.cloudflare.com.
vera.ns.cloudflare.com.
dfc@fob-xray:~$ dig +short ns econsultancy.com
cody.ns.cloudflare.com.
kay.ns.cloudflare.com.
dfc@fob-xray:~$ dig +short ns jct.com
ben.ns.cloudflare.com.
iris.ns.cloudflare.com.
I am not trying to be nit picky. I am genuinely curious, DNS is one of those things I find very interesting.
- jlgaddis 13y ago> "... better obscures ..." In their defense, they didn't say it completely* obscures the use of CloudFlare.
- dfc 13y agoThe real question is the first question: What is the point of obscuring? I probably should have skipped the bit about the effectiveness.
- evilDagmar 13y agoAs best I can tell it seems to be a very heavily veiled excuse to get their web service customers to sign up for Cloudflare hosting their DNS zones as well. Traffic balancing and redirection via DNS responses isn't new ground--other people just don't conflate it with CNAME kludgery.