I have my domains and DNS in Cloudflare but have multiple website in local & other hosting providers.
Currently i am using port forwarding in the hosting side and DNS in routed to public at Cloudflare.
My problem is some security settings i have defined in Cloudflare but the host is accessible with ip address, which by passes the Cloudflare settings.
How can i prevent this, how can i open the ports only to be accessible though Cloudflare DNS.
Regards
Ibbe
Website should be accessible only from dns. I want to accept only HTTPs
You should configure your DNS records in Cloudflare as a "Proxied", and in the "local & other hosting providers" you should allow access only from Cloudflare ip addresses. You can found the IP ranges here: https://www.cloudflare.com/ips/
Related
I have a domain and the host (Education Host) require to change the nameserver of that domain to its nameservers but the host doesn't have a DNS zone so I want to manage DNS with CloudFlare but its require to change nameservers too. So I want to use both of them but I don't know what happens?
Nothing happens, enter to your Cloudflare panel, change your domains DNS to Cloudflare DNS and in the IP section; Insert IP of your hosts (Education Host).
This will connect your domain to the host, and you can also manage domain records in Cloudfler.
reading this article will help you.
I purchased domain on dreamhost. and I deploy my application on other server. How to connect the dreamhost domain to other server ip address?
In goddady, there is an option to specify ip address on other server.
but I can't find a those settings on dreamhost DNS.
Anybody has a similar experience?
I found an answer. we need to set DNS only at the Hosting tab on
Dreamhost/websites/your_websites.
and Go to the DNS tab
First, click the Refresh DNS, it may take a few minutes
and then click the Add Record Button, and set your IP address on hosting.
I am hosting my own website on a Proliant Rack server using Internet Information Services. I have configured everything; port forwards, IIS, and also my Content Management System, Joomla. I have also registered a domain, www.example.com (not the real domain obviously) with godaddy. I have also gone into proliant iLO and I have set the server FQDN to www.example.com. Finally, I forwarded the domain in godaddy to my public ip. However, when I enter in the URL (www.example.com) into a browser (outside of my network), it simply shows my IP address. My host file is as follows:
127.0.0.1 localhost
127.0.0.1 example.com
127.0.0.1 www.example.com
Any help is appreciated. Thanks!
You need to add a site and bind its host name to your domain. Otherwise, IIS doesn't know what the domain point to.
This is a definitely a high level question so please take that with a grain of salt. I'm using GoDaddy as my registrar to point to my github pages website. I've uploaded the CNAME file and the URL resolves correctly. I've then set up CloudFlare on my site and am confused as to why I need to switch DNS servers to resolve to an IP address. So now, when the root finds the Top Level Domain for .com, will it now point to the CloudFlare DNS vs the GoDaddy one? In effect am I now just paying GoDaddy for the address and allowing CloudFlare to resolve the IP from the Top Level Domain Servers? Just trying to get an idea of what the CloudFlare DNS server is actually doing and why I had to switch out the GoDaddy one.
CloudFlare is taking over managing the DNS for the domain when you switch to our nameservers (GoDaddy is still your registrar/host). CloudFlare works via authoritative DNS.
I am unsure Whether both DNS server and Host file are the same or different.
I Hosted an application in IIS and created A host name as website1.domain.com and tried to browse it and it didn't work.
When searching on net i found that we need to make entry in DNS server or Host file.
As in most of the sites that I saw mentioned DNS server or host file. I am unsure Whether the both are same or they both are different.
A hosts file is used by Operating Systems to manually specify the IP addresses for specific domains/subdomains - think of it as an override.
DNS however is a server - think of it as a registry - that keeps track of records pertaining to domains, such as A records, MX records etc.
For the purposes of a local test site, an entry in your hosts file would be sufficient, however for a live site, a DNS entry relating to the domain you wish to have your site hosted on would be required.
Choosing which to use comes down to a few things. Does the server upon which your hosting the site use its own DNS server, i.e. a DNS server on the same network, which the connections to the server will be using as well? Does the domain name the site uses have its nameserver set to one that is externally available (i.e. 123-reg.co.uk). If either of these cases are true, you could probably use a DNS server.
If not, is the server hosting the site running on the same machine as the client that will be viewing the site? If so, you can probably use a hosts file, pointing your domains to the localhost IP of 127.0.0.1, ensuring the domains match the bindings in IIS.
Dns server is a server that will help to resolve dns names. ie when you type google.com in your browser , the name will be passed to the dns server provided by your isp. then it will be resolved to ip address by the dns server and your request will be routed to the google ip address by isp network. host file is different one. if you add www.mydomian.com entry in your host file and map it to an ip address 192.168.0.1 then your computer will check ion your host file when you type www.mydomain.com, whether there is any entry for mydomain.com in your host file, and if exists it will be routed to that ip address. in case if there is dns server and you set that server ip in your hnetwork configuration in your pc, then all the domain name request will be sent to that dns server(if there is no host entry exists)