One of my client has two domains names linking to a website :
Domain A
used for emails
used to access the website
Domain B
used to access the website
The problem is that the client doesn't want to let us manage the DNS of the domain A and they don't want to link it to Cloudflare (we don't really know what they want to do with the DNS of this domain). They only allow us to manage the Domain B.
Is there a way, somehow, to have the Domain B linked to Cloudflare and their Domain A linked to the Domain B which is linked to Cloudflare ? Like this, if they try to access the website from Domain A or Domain B, they both benefit of Cloudflare.
(I hope I didn't say something really stupid, DNS management and CDN are still a new concept to me - if I did, please excuse me)
"Is there a way, somehow, to have the Domain B linked to Cloudflare and their Domain A linked to the Domain B which is linked to Cloudflare ? Like this, if they try to access the website from Domain A or Domain B, they both benefit of Cloudflare."
Probably would need more details in a support ticket. Based on what I'm reading, however, you can't point a domain not on CloudFlare to one on CloudFlare (can cause DNS resolution errors).
If the client doesn't want to switch the domain to us entirely, then they could look at doing a CNAME setup.
Is there a way, somehow, to have the Domain B linked to Cloudflare
Yes, you could have Domain B on Cloudflare if you control that domain.
and their Domain A linked to the Domain B which is linked to Cloudflare ?
Technically yes, you could CNAME Domain A to Domain B, which is on Cloudflare.
However, this would likely fall afoul of:
they don't want to link it to Cloudflare
They would have to modify the DNS for Domain A to do this, and if they don't want to link that domain to Cloudflare, I don't see why they would want to CNAME it to a domain that's on Cloudflare, which will effectively have the same outcome, if a little less efficient.
I see this problem as less of a technical problem and more of a client relations problem. It sounds like you're trying to find sneaky ways of doing something the client expressly doesn't want. It sounds like the proper solution would be to have an honest talk with the client about why you believe they should use Cloudflare (sell them on its benefits) and if they are still not interested, find a solution that doesn't involve Cloudflare.
Really if both domain are in the seam server the solution is easy no cnames no complications
In config.php
'trusted_domains' =>
array (
0 => 'DomainA.com', 'DomainB.com',
In the folder of DomainB
ln -s ../path/to/owncloud mycloud
Cloudflare is a Nameserver, You can create a account and add desired Records like A, CNAME, TXT, MX.
Related
Is it possible to move my domain from one.com to cloudflare?
If so, can I then buy an ssl from them?
Also, any resources on how to do this would be great.
My biggest concern is the downtime when switching over.
Cloudflare is not a webhost and domain registrar services are only available to Enterprise customers. It provides DNS, proxy, CDN and various other tools.
SSL is provided free to all customers on all plans, but your certificate will be shared. If you need/desire a dedicated certificate that can be purchased as an add-on to any account for $5 a month.
If you are worried about downtime when you begin routing your traffic through Cloudflare (assuming that's what you mean by "move" to) just make sure you follow steps 1 and 2 of the Cloudflare 101 tutorials in the Knowledge Base before changing your nameservers in Step 3. It should be seamless.
A little more detail to answer the follow-up:
After adding your domain to Cloudflare, and setting up your DNS records, you will be provided with details for two Cloudflare nameservers. Take them to your registrar (in this case one.com) and update your nameserver information. As soon as the changes take effect with your registrar your traffic will begin routing through Cloudflare which is waiting and ready to go.
One.com is shared hosting and you can not change DNS settings on it aside from creating new subdomains. Also, your shared host will change its IP pretty frequently, so pointing a non-one.com managed domain to your one webspace's IP will break faster than you can update it. There is a reason that you can't even see your IP in your account settings.
If you really want to use cloudflare for DDoS protection and its other benefits, one.com and most other shared hosting is not a good choice.
When you search for a new web&domain host, confirm that they allow you to move your DNS to cloudflare before you sign up.
This question is sort of dev ops or networking related. When I point a domain at a hosting provider, I use a fairly generic Nameserver, i.e. ns1.digitalocean.com.
I understand when I add a domain to my hosting service to manage, that the hosting service recognises I am the registrant and serves up the site to the domain - so my question is, if another customer of the same hosting service adds my exact domain to manage on his account (there are now two) how does the correct registrant of the domain get selected? I.e. if there are two accounts on Digitalocean and they both put in example.com to manage and the registrar of example.com is pointing to the generic ns1.digitalocean.com how does Digitalocean select the correct accounut and code base to serve up? Apologies if any confusion or lack terminology - I am a bit fuzzy on this whole process. Thanks, Nick
They wouldn't allow another user to add the same domain, otherwise it's a bug.
I am trying to find hosting provider for a website that is connected to cloudflare. On Whois Lookup, I get Name Server(s) NOAH.NS.CLOUDFLARE.COM
UMA.NS.CLOUDFLARE.COM
When I use this website http://network-tools.com
I get Attempt to get a DNS server for 104.XX.1xx.3x failed:
I know that cloudflare is not a hosting provider. How can I dig deep and find the actual hosting provider?
If you have some type of abuse related issue with the website in question you'll need to file a complete abuse report at cloudflare.com/abuse
In most cases there isn't an obvious way to identify the underlying hosting provider for a website behind CloudFlare. With a valid and complete abuse report they can put you in touch with the hosting provider's abuse team though.
There is a service called CrimeFlare that helps to resolve the actual IP address behind CloudFlare.
If the website owner has properly set up their website's configuration with CloudFlare. There is no way to acquire the IP through any external means (Whois, DNS, etc)
If you must send an abuse report or DMCA complaint, you can contact CloudFlare through their website and they will be able to forward it on for you.
1. Check hosting history
Services like https://toolbar.netcraft.com/site_report can help you discover the history of hostings for the website.
2. Try Cloudflare IP resolver
https://iphostinfo.com/cloudflare/ (Works as of 2019.12.10, not sure if you can trust this source in a long-term).
Enter your domain name. Click "Search DNS" and you will be
brought to a page that checks for common DNS entries. This tool was
created to help webmasters configure their domains DNS with CloudFlare
properly and is not meant to be used for abuse purposes. If you see
your servers real ip in any DNS entry, anyone can easily find your
real servers ip then.
3. Look for subdomains manualy
You can check and WHOIS the IPs for subdomains. E.g. if www.XYZ.com and XYZ.com are both behind CloudFlare, check for popular subdomains, like:
status.XYZ.com
ns.XYZ.com
beta.XYZ.com
test.XYZ.com
forum.XYZ.com
blog.XYZ.com
admin.XYZ.com
etc..
There is some chance that they will be available directly without CloudFlare.
4. Ask
You can find a way to ask them directly. Or get such information via CloudFlare if you have a legit need to know it. (E.g. by contacting cloudflare.com/abuse as suggested by #xxdesmus).
Law enforcement officials can contact us directly at abuse+law#cloudflare.com. You must include your badge & case number when contacting us to receive a response.
Is there a way to hide the nameservers of my hosting provider in the public whois?
Regards
No, you can't hide such information. A few registries don't disclose them, but it's very limited number.
Some DNS providers offer a feature called "vanity name servers" that allow you to use custom name servers, if your purpose is to hide the name of the hosting provider to curious eyes.
Your question makes no sense over at least 2 points, and you should accept not to try pursuing something as pure vanity.
Here is why:
first whois is not the authoritative source on which nameservers are used for a given domain name, the DNS is;
and the DNS is public because otherwise if your nameservers are "hidden" then your domain name (like your website, emails, etc.) would not work at all.
And even if all the above would not be the case, your website ultimately resolve to an IP address and with just that information people could find out who is the hosting company. Which is why "vanity nameservers" do not help at all.
So there is no shame in having anyone know who hosts your website.
Or, if you are so ashamed of your hosting provider for whatever personal reasons, then it is time to switch, there are a lot of them.
You can reach out to your web host and request a private registration.
here is a link from godaddy.
https://support.godaddy.com/help/article/420/adding-private-registration-to-your-domain-names
The best way to mask your nameserver is using services like cloudflare. However, if you purchased your domain from Namecheap it will surely appear as the domain registrant. but cloudflare will change your nameservers to something link alexia.cloudflare.com
Cloudflare nameserver change will only work if you change your default nameservers to point to cloudflare, some hosting companies have partnership agreements with cloudflare which makes it possible to use the cloudflare services without changing your nameserver.
From the looks of it the new Azure Websites Feature still does not support hosting them under a naked domain such as example.com instead of www.example.com. Am I missing something?
Azure Websites have now released support for naked domains. Websites that are run on Shared or Reserved instances does support naked domains through an A record. Domain management is available through the Azure management portal.
Update 2012-10-21:
I previously stated that free instances could rely on CNAME to redirect a subdomain to their free Azure-website, but this appear to be incorrect, at least at the moment. Doing a CNAME to your Azure-website will result in an HTTP 404, as reported by MemeDeveloper in his comment.
However, if you run your website on a Free instance, you are still limited to CNAME, so for those websites naked domains are not possible.
Update:
As MemeDeveloper suggest in his comment, there are web services you can use that will take your naked-domain example.com and redirect it to www.example.com for you. For your www subdomain you could then have a CNAME to your Azure-URL.
Not as clean as a simple A record that is available for your paid websites, but a workaround for your free sites.
The conversations above are a bit dated. This entry however, comes up at the top of the list when folks are hunting/searching for Azure Naked Domain support.I'd update the answer.
Azure now supplies an IP in shared and > plans, and you can configure a naked domain.
Check out the following articles for more info:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/
http://blogs.msdn.com/b/waws/archive/2014/10/01/mapping-a-naked-url-to-your-azure-web-site-url-with-no-www.aspx
Azure does not support naked domain, because this requires to map definitively an IP address to the domain name. To map a naked domain name, you need a 1 record in the DNS. So, in this case, services like load balancing are more difficult to put in place.
Most registrars provide a way to redirect a naked domain request to another name, through HTTP redirect mechanism. For instance, you could redirect example.com to www.example.com.
There seems to be some confusion about this. I don't know what the deal with Websites is, but normal Azure Web Roles provide a virtual IP address that is guaranteed not to change unless you delete a webrole deployment.
You can bind a domain name A-record to that VIP, as described here.
In practice, that means that when I want to update my website, I have to do a staging deployment first; and then switch it with the production deployment, and finally delete the staging deployment. The only caveat that I've been aware of, is that you can't do this if you switch your endpoint configuration (not even names).
I'm currently looking if there are same kinds of guarantees for websites, but haven't found appropriate documentation yet.