Hi I am hoping someone can help me with this question, as apparently the chat agent on godaddy couldn't.
I have a DNS for domain A registered with godaddy.
I have a number of sites running from my home pc which unfortunately uses dynamic IP, so I lose these sites everytime my ISP updates the IP address.
I have a no-ip service for Domain B which points directly to my home computer as is always maintained. All of the sites I use with no-ip service are always pointing to the correct place.
Is there a way I can point my godaddy domains (Domain A) to my no-ip domain (Domain B) whilst keeping the original url? I'm thinking its domain forwarding or something to do with NameServers, but this is an area in which I have zero knowledge.
Thanks in advance
Related
I am a bit new to the deployment of a website. I have a server which is written in Node.js. Previously I had been using Heroku for deploying my apps without knowing much about deployment. I would like to know how do I deploy my server to create a website which has .com at the end of it like www.example.com and not www.example.herokuapp.com. I think it has something to do with domains (correct me if I am wrong). I would like to know what exactly is a domain and a DNS provider and how to deploy a website in such a way. Thank you.
You should ask one question to yourself when you hit www.example.com in browser how does it load a page?. When you run a website on your laptop it basically runs locally, if you want to access your website over the internet you would require public IP(host or server) accessible over the internet so you can access a webpage using public IP:port. But this is not the best option because IP may change in the future and also remembering IP for each application will be difficult. Imagine if you access Facebook, Instagram or any other websites by its IP addresses how difficult and inconvenient would it be? There are a couple of things you should know.
DNS-> Domain Name system
Every host is identified by the IP address but remembering numbers is
very difficult for the people and also the IP addresses are not static
therefore, a mapping is required to change the domain name to IP
address. So DNS is used to convert the domain name of the websites to
their numerical IP address.
DNS is a hostname to IP address translation service. DNS is a distributed database implemented in a hierarchy of name servers. It is an application layer protocol for message exchange between clients and servers.
Name servers
Domain Name Servers (DNS) are the Internet's equivalent of a phone book. They maintain a directory of domain names and translate them to Internet Protocol (IP) addresses. This is necessary because, although domain names are easy for people to remember, computers or machines, access websites based on IP addresses.
DNS record
A domain name, IP address what is the validity?? what is the time to live ?? and all the information related to that domain name.
Once you understand the DNS
Host(Deploy) your website to Amazon EC2 or Heroku and obtain Public IP.
Buy a domain from domain provider like Godaddy
Map domain(ie www.example.com to IP)-> DNS record
Mapping domain to IP may vary platform to platform but the Core principle remains the same. I would suggest you these below link. Try to find differences in both, doing so you will learn along the way
http://www.littlebigextra.com/map-domain-name-amazon-aws-ec2-instance/
https://medium.com/progress-on-ios-development/connecting-an-ec2-instance-with-a-godaddy-domain-e74ff190c233
I'm trying to map my ip to the domain name I bought but little did I know, it's more confusing than I thought it would be. Where exactly does the link between the IP and the domain name happens? Does it have something to do with nameservers or domain redirections?
You will need to update your DNS settings and point to the IP you want.
The company / website your domain is registered with will be able to help here / allow you to do this online.
be aware that a lot of residential addresses will have dynamic IP addresses which may change frequently causing you to need to update the DNS a lot.
Id recommend looking at a free web host (freehostia.com for example) if you are able to host your website / server online
I have a VPS server on OVH, it just has its own ip and Reverse DNS.
So i basically always used domain trough cloudflare and pointed a record to my VPS IP.
I don't want to use cloudflare anymore, I've bought the DNS Anycast option for my domain and pointed a record to my VPS IP, but website just stopped working.. What should i do ?
I have 3 more domains, i would want to make some ns1.mydomain.com ns2.mydomain.com zones based on my main domain, so i could use it for all my other domains, How can i do that?
ps. In case if this info is needed, all my domains are in OVH too.
1) You could revert back to previous state. Other than that, it is difficult to troubleshoot DNS issues without real domain name.
2) DNS is crucial part of infrastructure, you don't want to host that by yourself unless you know what you are doing.
Lets say I have ordered domain name abc.com from GoDaddy.
I want to point the domain to my web site that I am hosting locally on my computer via IIS. Lets say that to hit this website currently, you would go to '123.123.123.123/mysite/'.
I am trying to setup the DNS Zone File to do this, but I cannot figure out how to get it to point to the "/mysite/" directory.
How can I properly set my GoDaddy DNS Zone file to point to '123.123.123.123/mysite/'?'
You have got your concepts a little mixed up there. What you are looking for is a HTTP Redirect. DNS is simply a way to map an IP Address to a domain name, it doesn't care what the traffic does once it gets to your site.
Think of DNS as a Postcode (Zipcode). It puts a letter in your letterbox. There is no way for it to know that Betty is on the second floor, because that's not what the Postcode does.
DNS will point a domain name example.com to an IP Address 123.123.123.123. You can have multiple domain names, www.example.com and mysite.example.com all pointing to the same IP Address, and the server can be configured to figure out what to do with each individual domain name.
So what you could potentially do is have the server detect that you are requesting mysite.example.com and have that redirected to www.example.com/mysite. This would be the standard way of achieving this.
The company i work for just begun hosting a new website and had to transfer the domain name from the ISP to a different hosting company.
Now the website is accessible from outside the network but not accessible from inside the network. The ISP is the same and we can't access the website using our ISP. It doesn't resolve the DNS Name at all.
If i try to ping the website, it says "host lookup failed", even nslookup is failing. When trying to access the website via the IPaddress, it refuses.
The problem is in the ISP but I don't know how to solve it and our ISP isn't being very helpful.
This often happens when someone is running authoritative and recursive DNS on the same servers. Which is why you should never do that :)
It also happens when your local domain (Active Directory?) is the same as the domain you use at your hoster. Never do that. For example: if your domain is example.com then don't use example.com as your local domain. If you do then both your hoster and your own servers believe they are authoritative for that domain. Once the zone data starts to diverge you have this kind of weird problems. Instead use a subdomain of your domain name for your office, like office.example.com so that example.com can remain authoritative at the hoster.
If you do have the same domain both locally and at the hoster then you have to manually make sure that the information in your local DNS server stays in sync with the hoster's DNS server. For example: if your hoster has record www.example.com A 192.0.2.1 then you have to have the same record in your local DNS server. When the hoster changes the record to e.g. www.example.com A 192.0.2.222 then you have to make the same change otherwise your local DNS server will keep telling you that www.example.com is at 192.0.2.1. The same happens when you change hoster as they will almost certainly use different IP addresses.
So if you can then don't use the domain name itself in your office but use a subdomain. If that is impossible then you will have to manually keep the hoster's and your own DNS zone data in sync. Because this always goes wrong and breaks in 'interesting' ways really try to use a subdomain though!
PS: and never ever use somebody else's domain name as your local domain. I have seen ICT companies use local domains like <localcityname>.com and then suddenly the whole company can't access the real domain anymore because the local servers think it's theirs.