Pointing domain to FTP Hosting without changing nameservers - dns

I have a domain registered at godaddy [www.example.com]. And i have a free hosting at Binhoster.
I want to point my domain to Binhoster's FTP server where my pages are hosted.
I googled this and I was instructed to change my nameservers of godaddy to Binhoster's nameserver, then add the FTP IP in the A-Record.
But I, without changing the nameservers, Added the A-Record to point to Binhoster's and added a custom domain at Binhoster's [www.example.com to point to public_html] and its working. I'm currently using my original nameserver. Then why is it instructed to change nameservers everywhere. Is it mandatory ??

You may want to reach out directly to Binhoster to see why they suggest to change your NS. This may be because the IP address could change. If an IP address changes and you control the DNS, you will need to be notified and subsequently update the A record IP, whereas if you pointed your NS the IP may be updated automatically at the host.
Ultimately, as long as you point your A record to the host, you should be fine.

Related

Add CNAME entry in which zone?

There is an article on Run Multiple Websites on the Same Port and IP Address on IIS. So in my Windows Server 2012 R2, I installed DNS Server. However there is no zone by default.
But according to the link, I want to run multiple websites on the same port and IP address on IIS. After I edited site bindings on IIS. All I have to do is to add an alias for the server (A or CNAME) to DNS that specifies the IP address or the name of the web server.
Now I want to follow the example to add an entry to the zone. The below image is from the link. It has two zones. One is _msdcs and the other one is something I don't know.
However my DNS server doesn't have zone yet. I guess that I must create zones.then add the CNAME entry.
My question is which zone can I add the CNAME entry?
Or it doesn't matter in any primary zone?
It should definitely be your company IT DNS server. The CNAMEs can go in an existing zone on that server; they don't have to go into a new one. However, there needs to be at least one host a.k.a. A record that points to the webserver. The CNAMEs should all point to that as the target host.
For example, if you need to access a website from www.test.com.
Then you can create a forward lookup zone.
Then you need to create a A record to map your IP address to your server
Now you can right click blank place->create Alias(CNAME) to map your A record to CNAME
Finally, you only have to set IIS binding and access the website

Why using A record for OpenShift is bad idea?

If I ping my OpenShift application I see some IP like this
ec2-11-22-33-44.compute-1.amazonaws.com [11.22.33.44]
Can I be sure that my IP is 11.22.33.44 and I can use it for A record in DNS settings?
In which cases this IP is changed ?
Never seen this inforamtion. All articles claim that only CNAME may work.
You should never use an A record to point to your OpenShift application with an external domain. That IP address can change at any time for outage or maintenance reasons. You should always use a CNAME to point your domain name to your application url of the format app-domain.rhcloud.com
Just found an answer.
This was not just my own IP.
Several sites have this IP too.
http://www.bing.com/search?q=IP:11.22.33.44

How to map domain to hosting server

My client have a dedicated server on liquedweb cloud service and we my web app is hosted on that server. We want our users to map their domain to our server. So they can enjoy our web app by using their domain name. What information I need to provide to my user so he can map domain and what information I need from them?
I don't know much(in fact anything) about domain mapping
thanks
It depends if the server has a dedicated IP address or is natted.
If the server has a dedicated IP address you can ask your clients to point their entire domain to you server by adding the following A records:
Host TTL Protocol Type IP Address
# 300 IN A 1.1.1.1
www 300 IN A 1.1.1.1
Not all domain hosts ask for TTL,if not dont worry about it.
If you want just their subdomain to point to your server (subdomain.website.com)
subdomain IN A 0.0.0.1
TTL is optional in some systems, in this case the default will be used.
Generally it is recommended that you use an IP for the Apex record and not a domain name. EG: example.com is the apex, www.example.com is the www subdomain.
A typical configuration would be below:
Host TTL Protocol Type Result
# 300 IN A 1.1.1.1
www 300 IN CNAME example.com
This is the same config as the top example but using CNAME example.com. It is the same as using A 1.1.1.1, it just means you only need to change one record.
If your server details are a hostname and not an IP address, most systems will not let you use the hostname for the apex so you will need to find out the IP address. (A simple method is to use the nslookup command or dig command).
TTL is how long in seconds a record last before it expires. If you are unsure what you are doing I recommend lowering this so you can correct mistakes more quickly.
Different methods for the different servers. For most of the servers, you have to change the nameservers of your domain.
This mostly needs when your domain registrar and hosting provider both are different.
First Login into your hosting account, navigate to the account details,
then copy the nameservers from there...which would be like :- dns1.hostingprovider.com
dns2.hostingprovider.com
After that, Go to control panel of your domain. Navigate to the nameservers
You will see the link:- dns1.domainregistrar.com
dns2.domainregistrar.com
Paste the above links at the place of below links.
They need the IP address (and possibly instructions on how to configure their DNS servers (which means a variety of different sets of instructions for different servers and control panels)).
You need the domain name.

DNS setting to access website using IP address and domain name

I have Static IP, i would like to access website using static IP as well using domain name.
I have below DNS entries to for my domain, i am not sure what setup i need to do to make it works.
when user access my site using domain name they should be able to access. Also when someone want to access using IP address they should be able to do that.
www 14400 IN CNAME example.com
example.com 14400 IN A 50.63.147.111
If anybody have idea please let me know.
Thank you
Regards,
Mona
If you can't access your IP address, then it isn't because of your DNS. DNS stands for domain name system and translates domain names TO IP addresses. Thus, you must already have a reachable IP address for your A record to be meaningful. Make sure that you've configured your server correctly (Apache?) and that the necessary ports are open in your firewall (iptables).
Check that your domain registrar is pointing its name servers to the authoritative name server (the server with your zone file) for your domain.

Pointing DNS name to IP address on local machine

This might be a stupid question but i would really appreciate any compact answer.
I have uploaded a Joomla site on my local machine using a static IP address (213.221.211.111 for example). I have registered a domain (like www.example.com) on Godaddy.com. Within their dashboard, I set the primary and secondary name servers (I looked it from my router setup page).
Is there any else I need to do so that entering e.g. www.example.com would take the user to 213.221.211.111.
Inside of godaddy, you need to map "www" to your static IP address. It would be a good idea to also map the default entry for your domain, sometimes called "#".
Edit: Upon further reading of your original question, you don't set the primary and secondary DNS servers for your domain to your ISP's servers. Your domain's primary and secondary servers are for the addresses of the servers that are responsible for serving your domain. Unless you have your domain hosted with your ISP and not with godaddy, then this is not the right thing to do at all. If you have your domain hosted with godaddy, follow their instructions for setting up a domain and pointing "www" at an IP address.
In addition to what jricher said, you will also probably need to port forward.

Resources