How do all DNS providers like Google, Cloudflare and etc. agree on where an address should point to?
Why won't one company try to sell a domain, already sold to a customer by another company?
Related
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
In light of the seizure of Backpage.com.
How does the process of DNS seizure process technically work? Is there a change in the A Record of the DNS to redirect to the seizure IP notification site?
According to this (non-authoritative) webpage: https://comptutor.me/2015/05/25/prevent-domain-seizures/
The government agency finds the registrar responsible for the domain (GoDaddy, NameCheap, etc). The registrar must be under the jurisdiction of the agency and the court that determined the name must be seized.
Agency gets a court-order that shows they have the right to control the domain-name.
Agency contacts the registrar, referencing the court-order.
The registrar authenticates the court-order (hopefully!) and then moves their internal registration to a different customer account representing the agency.
If the registrar was also hosting the DNS zone, then the zone may or may not be copied over - but more than likely they won't, so they'll just change the domain's SOA (Start of Authority) record to point to DNS zone servers that are under the control of the agency (or self-hosted by the registrar themselves).
So no A records are updated directly - though that is an option if the registrar is hosting the zone, it's far more straightforward just to treat it like any other (voluntary) domain-transfer between two customers of the same registrar.
The court-order may also order the domain name be transferred to another registrar, though as that takes more time it may make sense to do an internal transfer.
I bought my domain with a hosting company but I no longer need the hosting space. I am just redirecting my domain to my github pages. I did that with the admin panel my host provided.
I would like to quit paying the hosting company but continue having the domain point to github. How is this done?
You need to transfer your domain to a domain host like Namecheap or Godaddy. They will charge you just about $11 (based on the domain extension) to keep just your domain per year.
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.
I'm new at DNS world, did some readings in the Internet and wanted to know if I came to the right conclusions. I want to build a system where users are able to create new sub-domains of existing registered domains automatically:
My system provides services to different companies, these services are hosted in my system or some cloud provider. Lets call my system "services" and some company "company1". I want to offer "company1" my services and have its users access these services through "company1" new sub-domain, when "company1" has an already registered domain company1.com. I want "company1" admin user be able to control and choose the sub-domain via my system when he registers his company in my system, and have the whole thing automatic. If i understand correctly:
if the admin would want to use a sub-domain like services.company1.com this will be a problem since I would need to update the authoritative name-servers of company1.com which I don't know who they are, and even if I have a way to know them (and from reading a bit I see that I do have a way), I don't know if every such name server will allow such updates from some external source, connectivity issues etc
if the admin would like to use a sub-domain like company1.services.com then I can achieve this by having my own dns server which I will register the services.com domain for and actually manage all these company sub-domains in my own dns server. This means though that all companies will have to have a sub-domain under my domain services.com
Please correct me if I have a wrong view on how DNS works.
thanks!
services.company1.com
To provide this kind of domain name to your customer, you will need their collaboration. A lot of companies provides this kind of feature by asking you to point an alias (CNAME Record) to a specific server.
Examples of concrete usage
blog.company1.com. 3600 IN CNAME domains.tumblr.com.
shop.company1.com. 3600 IN CNAME myapp.herokuapp.com.
git.company1.com. 3600 IN CNAME bitbucket.org.
Here's some links to the documentation of companies offering this feature:
BitBucket
Heroku
Tumblr
Sample client zone file
So in your case your customer DNS zone will contain something like that:
services.company1.com. 3600 IN CNAME domains.services.com.
where domains.services.com. will be the server that handles the subdomain authentication
company1.services.com
To provide to your customers company1.services.com, you don't have to manage your own DNS server, you just have to be able to add a wildcard record to point all the subdomains to your application. It will be the role of your application to filter your service per subdomains.
Sample service zone file
For example (where 0.0.0.0 is your service IP address):
*.services.com. 3600 IN A 0.0.0.0