Requests not routed through CloudFlare - dns

I have my domain example.com on CloudFlare and a subdomain, fo.example.com, delegated to another name server.
This is the setting on CloudFlare
A www.example.com 1.2.3.4
CNAME test www.example.com
CNAME test2 www.google.com
CNAME test3 fo.example.com
plus the NS for fo. All the above have the orange icon, i.e. requests should go through CloudFlare.
and this is the setting on the other nameserver
A fo.example.com 5.6.7.8
Now, when I traceroute www.example.com, test.example.com and test2.example.com I can see that it goes through CloudFlare but when I traceroute test3.example.com it goes direct exactly as I traceroute fo.example.com. This looks incorrect to me, why requests to a CNAME pointing to an extrenal domain (google.com) goes through cloudflare and the one pointing to a delegated subdomain does not?

Very difficult to look at without knowing the actual subdomain in question. There are some records that can't be proxied (pointing to other CDNs, for example, does create DNS lookup issues in some cases).

CloudFlare supports answer:
That's not possible, no way around it either. I've tried.
Unfortunately our current system doesn't allow this. This has been a
feature request for awhile, it will get added eventually, but no ETA
as of right now, sorry.

Related

hostless DNS CNAME record

We are running BIND 9.9.7 on Centos 6.5 and for a long time I have been creating "hostless" DNS entries so that sites work with or without the www.
Eg:
www IN A 192.168.1.1
domain.com. IN A 192.168.1.1
However, our client wants to use a CNAME record to a cloudfront host and the "hostless" entry doesn't work as a CNAME record.
In fact, it more than doesn't work, BIND won't even load the zone file. The error is
"failed: CNAME and other data"
domain.com. IN CNAME host.cloudfront.net.
www IN CNAME host.cloudfront.net.
It will load and resolve fine without the domain.com entry. I have tried a few variations, but nothing seems to work. including "", "."
Can anyone tell me the correct syntax for this entry?
There is no correct syntax for this (and it is not BIND specific, it is a side effect of RFC1912 which states that A CNAME record is not allowed to coexist with any other data.
Detailed explanation: Why can't a CNAME record be used at the apex (aka root) of a domain?
Some DNS providers might offer workaround hacks.

dns propogation issue with cloudflare subdomain

Want to configure sub-domain - www.portfolios.shuttrbox.com
when I check DNS propagation for portfolios.shuttrbox.com, it works fine
whereas when I check for www.portfolios.shuttrbox.com it shows all crosses on https://www.whatsmydns.net
Traffic routes through cloudflare
I have my .htaccess configured to add "www" to my domain shuttrbox.com
Not able to figure why www.portfolios.shuttrbox.com is not being propagated.
It was probably a propagation time issue. It appears to now be working correctly.
actually I added 2 CNAME entries in cloudflare:
1/ portfolios.shuttrbox.com
2/ www.portfolios.shuttrbox.com
That seems to have worked somehow.

Domain DNS settings redirection (www to https)

I have a SSL certificate for domain example.com. I want to redirect www.domain.com (and also the 2nd domain, e.g domain.com.au) request to the domain.com. In the example.com domain DNS setting I see
CNAME www.example.com is an alias of example.com
do I have to play with that entry or maybe set up that redirection on my server (Windows Server 2008 R2) ?
The CNAME only tells the browser (or more accurately, the resolver) how to find the IP address of the domain name. In this case, when the browser tries to resolve "www.example.com", it finds a CNAME record, so it needs to follow that alias and resolve "example.com". Eventually, it should arrive at an IP address to which it can make a HTTP(S) connection.
In short, yes, you need to setup the redirection on your web server as well.
Use URL Rewrite for redirections. It's a bit cryptic at first but it's a powerfull tool in IIS for this purpose. http://www.iis.net/learn/extensions/url-rewrite-module

Linking multiple domains to a server

I have a server that already has a domain, lets say mysite.com but i want to put another site on it with the domain mysite2.com.
So my questions are, how do i set up the nameserver settings.... My first domain i have listed
ns1.mysite.com
ns2.mysite.com
So would it work if i used:
ns1.mysite2.com
ns2.mysite2.com
for my new site?
Also, i have to set up "glue records". These are the ns1 and ns2 from the nameserver and provide the ip of my server. So for the mysite2.com would i use ns1.mysite2.com and then the ip would be for example 111.111.111.111/MYSITE2 ? Because the glue record for the first site is just 111.111.111.111.....?
Hope this isn't to confusing, i'm just new to this stuff and want to understand it a bit better and i don't want to mess my original site up in anyway.
thanks for the help.
Your DNS records don't have to be within the same domain as the one they host. If you are running your own DNS servers, they can live inside your primary domain. But if you're using another DNS provider like zoneedit.com or easydns.com, just use the hostnames they provide.
"Glue records" are the NS pointers that let the root servers find the DNS servers for a particular domain. For example, there might be:
mysite.com NS dns1.example.com
mysite.com NS dns2.example.com
mysite2.com NS dns1.example.com
mysite2.com NS dns2.example.com
Note that this is entirely different from where your domain's web site is served. For that, you just configure the DNS for each of these domains so that the IP address for the "www" host (and probably the domain itself) points to the same IP ... then you read your web server software's documentation on how to set up "named virtualhosts".
Are you clear on the distinction between DNS hosting and web hosting? If not, I can go into more detail.

Custom domain in Tumblr

I setup this domain's A-record to point to this tumblr:
emmaraviv.com :: timeoftstretched.tumblr.com
Which works fine, but www.emmaraviv.com does not.
In tumblr, I have the "custom domain" set to "emmaraviv.com". I don't see a way to specify multiples. i.e. "emmaraviv.com", "www.emmaraviv.com".
I added another A-record for www., point to the same IP (the one Tumblr tells you to use). But when you try to go to this records address specifically (www.emmaraviv.com.ryan-orourke.com -- it's under my primary domain on my host) it resolves to Tumblr, but not her site. Which makes me think the issue is with Tumblr not recognizeing this domain as one that should be pointing at timeoftstretched.tumblr.com.
Would love some ideas?
Thanks!!
On mine I did the following and it worked, on the DNS just setup:
# A 66.6.44.4
www A 66.6.44.4
Then both domain.com and www.domain.com both go to tumblr, in your Customize area just put www.domain.com as your domain, hopefully this should work.

Resources