How to setup domain to use own dns server exclusively - dns

For example, when I buy a domain from GoDaddy and I setup up my own DNS server, the first thing is to change the NS record on GoDaddy panel. But the NS record can only be in domain format.
How can I set my domain to use my own DNS server without any others?

For example:
You create an A record for your server ns.mydomain.com -> xx.xx.xx.xx
then you point the NS record to ns.mydomain.com

Related

Can you override a DNS entry that you've delegated to another name server?

Let's say I have two DNS servers
DNS Server 1 (dnsserver1.com)
test.mydomain.com NS dnsserver2.com
hello.test.mydomain.com CNAME www.apple.com
DNS Server 2 (dnsserver2.com)
hello.test.mydomain.com CNAME www.google.com
According to my tests, if you visit hello.test.mydomain.com it'll display google.com, but I'm wondering if there's a way to override the delegation. Reason for this being that I'm switching my second DNS server (dnsserver2.com -> dnsserver3.com) and I would like to test this new delegation by individually overriding entries before I swap over the entire delegation.
I think I found my answer here, specifically:
Also note that any local zones you create would step on and override any outside DNS server's zones: It's not possible to have the A record for pc.home.mydomain.tld come from one NS and the AAAA record for it come from another: DNS delegates and declares authority by zone name, and that authority is for all record types within that zone.
If a nameserver is told it is authoritative for something and can't find the record it will not forward the query up the DNS tree, it will simply return NXDOMAIN.
As a result, my plan is to delegate individual records a second time like so:
DNS Server 1 (dnsserver1.com)
test.mydomain.com NS dnsserver2.com
DNS Server 2 (dnsserver2.com)
hello.test.mydomain.com NS dnsserver3.com
DNS Server 3 (dnsserver3.com)
hello.test.mydomain.com CNAME www.apple.com

How to setup a subdomain DNS proxy?

Hello I will get a access to a subdomain division.company.com and I will have to name where to point it in contract. I don't want request for contract update because where subdomain has point to every time I need to switch a server.
I am looking to have a top level DNS like control for a subdomain.
a) Do I use some kind of routing/proxy server?
b) Is there a way to have a dynamic DNS assignation (single time minimal configuration on the top level domain side)?
c) Is what I am looking for possible with DDNS providers like https://www.dynu.com/ ?
I tried using dynamic with a test domain but it did not seam to function properly.
On test domain I added CNAME DNS record b.a.com pointing to b.dynamicdns.com and then on dynamic DNS'es DNS records I pointed a CNAME record of www.b.dynamicdns.com to a website's server then on website server side I tried www.b.a.com but it did not seam to work.
Top level domains has to add NS (name server) records for the subdomain pointing to a DNS management provider
https://www.dynu.com/ has and add own domain where subdomain can be entered and configured but other providers should work too.
NS b.a.com NS1.provider.com
NS b.a.com NS2.provider.com
That will delegate subdomains DNS record management to it and will allow for full control of it. Including adding CNAME records pointing to any server.

Subdomain and # record

I'm facing an interrogation on how to set up an # record for a sub DNS zone.
Imagine I have a domain example.com on my primary DNS servers.
I want to delegate the sub-zone france.example.com to a secondary external DNS server, so I create an NS record for this zone pointing to the correct server. This works.
I then want to declare the A record france.example.com on this secondary server.
It seems to me that this is not possible.
Can you confirm the correct workflow while trying to resolve this record?
The client asks its recursive DNS server for resolution.
The recursive DNS server determines who is the NS for example.com from the internet root servers.
The recursive DNS server asks the example.com name servers for the "france" record.
No issues for records xxx.france.example.com, they can be defined on the secondary server as the workflow changes this way :
The client asks its recursive DNS server for resolution.
The recursive DNS server determines who is the NS for example.com from the internet root servers.
The recursive DNS server determines who is the NS for france.example.com from the example.com servers.
The recursive DNS server asks the france.example.com name servers for the "xxx" record.
Any help would be greatly appreciated.

Making nameserver for put domain on server ip

I have a domain and i want to set it to my server(centos 7).
I made a dns server by bind on my server and made 2 nameserver (ns1.myDomain.ir and ns1.myDomain.ir) and set it in my domain configuration, But i cant ping to my domain.
What is the problem?
At the domain registrar, you need to specify the authorised DNS server for your domain. My suggestion is to use the domain registrar's DNS server for resolution and create a zone file there for your domain and enter the A records and other records for your use case.
To have a domain working you don't need to setup your on DNS (bind) server.

Setting up a custom nameserver with BIND9

Lets say that I purchased a new domain (somedomain.com) from a domain registar and I wanted to setup my own nameserver on a server that has two IP addresses.
First I buy the domain.
I get the server.
install BIND9.
I login to the server and prepare the DNS records for NS1.SOMEDOMAIN.COM and NS2.SOMEDOMAIN.COM.
Where do I set these up in BIND and how should I do it?
Next Step:
Go back to the domain registar and set the DNS to point to NS1.SOMEDOMAIN.COM and NS2.SOMEDOMAIN.COM.
Is it a bad thing if the domain that I am forwarding is pointed to its OWN nameserver domain? Should I change this? How does it know where NS1 and NS2 go when both subdomains are apart of the domain that is being forwarded to them?
Should I just use the DNS provided by my registar and make two CNAME record entries for NS1 and NS2 to point to the server ips of the newly created DNS server? Would this work?
Can anyone explain this process to me? Thanks.
Do add the following step which is crucial to using your name servers in the WHOIS record:
Step 5: Go back to your registrar (wherever you bought the domain in step 1) and create the special NameServer records in their administrative control panel; for example, on godaddy.com, you need to go to advanced > hosts and there you can set up ns1 to point to the IP address of your server (step 2).
You will need to do the same for ns2.
This will vary from registrar to registrar, consult their documentation or contact customer support.
Step 6: Update the WHOIS record to reflect your new nameservers.
Where do I set these up in BIND and how should I do it?
You would set these up in the domain's zone record, not unlike this:
yourdomain.com. IN SOA ns1.yourdomain.com. you.yourdomain.com. (
1032789388
10800
3600
604800
300 )
yourdomain.com. IN NS ns1.yourdomain.com.
yourdomain.com. IN NS ns2.yourdomain.com.
ns1.yourdomain.com. IN A xxx.xxx.xxx.xxx
ns2.yourdomain.com. IN A yyy.yyy.yyy.yyy
Is it a bad thing if the domain that I am forwarding is pointed to its OWN nameserver domain? Should I change this?
Running DNS from the same domain is fine.
How does it know where NS1 and NS2 go when both sub-domains are apart of the domain that is being forwarded to them?
See Step 5 above - your registrar handles this bit, registering your name servers and allowing them to participate in the 'net.
Should I just use the DNS provided by my registar and make two CNAME record entries for NS1 and NS2 to point to the server ips of the newly created DNS server? Would this work?
This would not work as you would still need to do Step 5; to be honest, I'm not sure what would happen if you did not serve the DNS for ns1 off of the same host.
Additional note:
While you CAN run one DNS server for both ns1 and ns2, it is not recommended.
Usually you want your secondary (slave) DNS server to be as far away as possible from your primary (master) DNS server... located in a different country is usually the best.
But, there is nothing technically preventing you from using two different IPs on the same physical hardware.

Resources