Using Rackspace.com, which offers DNS service, I am attempting to point one domain EXAMPLE.NET to a dynamic DNS updated domain EXAMPLE.DYNDNS.ORG.
My problem is that when pointing the Fully Qualified Domain Name (example.net without any subdomain in-front) to the dynamic domain that is updated by the dyn service, I am given the response;
CnameRecord: Fqdn has already been taken by another resource record
while, in fact, there are no other records for this domain (other than the NS records that are required). I am not given this error when a subdomain is used, only when the fully qualified domain name is what is being acted on.
I found one article that gives me the insight to believe that one may point to a CNAME record from the FQDN (example.net).
CNAME records should not point to other CNAME records. This is mainly to avoid possible infinite loops.
CNAME records should not contain other resource record types (such as A, NS, MX, etc.). The only exception are DNSSEC related records (that is, RRSIG, NSEC, etc.) when the zone is signed.
Other resource record that point to the fully qualified domain name (FQDN) of a host (that is, NS, MX, PTR) should not point to a CNAME record.
My goal here essentially is to use a dns service to point my .net domain to a domain that is dynamically updated with my router since the server is stuck in a dynamic IP pool. Any advice?
The error message is exactly correct. You cannot create a CNAME RR because the domain already has NS RR (and in fact, also an SOA RR too) and CNAME is not allowed in combination with anything else (except DNSSEC RRs).
Your best bet is to use dynamic DNS to update example.net directly, instead of or in addition to updating example.dyndns.org.
Related
When I deploy my website on Google App Engine and add a custom domain(that I own from GoDaddy.com or name.com or namecheap.com etc.), GAE provides me with A, AAAA, and CNAME records which I need to add in the DNS record configuration in GoDaddy.com/name.com/namecheap.com website.
Similarly, When I deploy my website on Digitalocean and add a custom domain(that I own from GoDaddy.com or name.com or namecheap.com etc.), it provides me with nameservers(ns1.digitalocean.com,ns2.digitalocean.com etc.) which I need to add in the Nameserver configuration in GoDaddy.com/name.com/namecheap.com website.
So is adding nameservers equivalent to setting DNS records?
So is adding nameservers equivalent to setting DNS records?
Well, yes and no.
Yes, the "Nameservers" setting actually creates 'NS' type records in DNS – except they are not in your zone; they are in the parent zone. For example, if your domain is example.com, then its nameserver addresses must be known by the com zone.
(That said, your own zone also has identical 'NS' records, but they're not the ones that really matter.)
But on the other hand, no, setting nameservers (NS records) has a completely different purpose from creating A/AAAA type records. An 'A' record directly points to the server where a website is hosted, while an 'NS' record adds indirection – the 'NS' record points to a server which holds the 'A' records.
Can you tell me the complete flow of what happens including DNS and zone file lookup that take place when I type "www.example.com".
Your OS (which has a 'stub' resolver) sends the query to a 'full' or 'recursive' resolver.
The recursive resolver has a built-in list of nameserver addresses for "" (the DNS root).
The resolver sends the query to the root nameservers, receives a referral to the "com" domain's nameservers ("I don't have that record, but I do have com./NS records").
The resolver sends the same query to the 'com' nameservers, again receives a referral to the "example.com" domain's nameservers.
The resolver sends the same query to the 'example.com' nameservers, and finally receives the actual answer.
The recursive resolver returns the answer to you.
See existing documentation:
https://www.cloudflare.com/learning/dns/dns-server-types/
https://royal.pingdom.com/a-visual-explanation-of-how-dns-lookups-work-2/
It's may be stupid, but I really interested in this question.
I want make mirror www subdomain for main and can't choose which property to use...
CNAME looks more solid and clearer. I can set it like this:
www.exmaple.com -> A someIP.
Just don't quite know how Google Cloud DNS behaves. If use CNAME, will the client get an subdomain IP or will he get the name of the main domain and make a second request to get his IP?
P.S. Yes, I understand that the time difference in the execution of requests is so small that should forget it.
Google Cloud DNS does not support ALIAS resource records.
ALIAS (A) records are usually faster and are typically used for internal services on the same provider. Example would be a load balancer. ALIAS records typically have a short TTL (typically 60 seconds) so that they are constantly being resolved to the service.
When you resolve a CNAME, a subsequent lookup is required for the returned DNS name, which could then be another CNAME, etc.
There are more factors to consider when select an ALIAS versus CNAME. For example:
AWS does not charge for ALIAS record lookups but does for CNAME lookups.
You cannot use a CNAME for the zone apex (example.com). You can for the subdomains (www.example.com).
A CNAME cannot coexist with another resource record of the same name, whereas ALIAS can.
Let's say I have a website example.com which I bought via a common domain registry nomcheap.com.
I want all traffic to a specific subdomain app.example.com to go to name server ns1.appserver.com so I can serve a specific user app.
I also want all other traffic (www.example.com, hello.example.com, *.example.com, etc.) to go to a different name server from a different provider ns1.squaresites.com so I can serve a general website (think something like a commerce Wordpress site).
None of the name servers are provided by the original domain registry nomcheap.com.
Is this possible? If so, any suggestions on how?
To point a subdomain to a name servers you need to create an NS record for the subdomain:
app.example.com NS ns1.appserver.com
This will make all queries go to ns1.appserver.com
*.example.com NS ns1.squaresites.com
The second record should catch all subdomains that don't have their own records (of any kind).
Delegating name server DNS responses can be done was the answer by #Lanexbg describes.
Realize that chaining your DNS lookups this way adds more time to DNS resolution and adds another potential point of failure in the resolution process. If the parent's name servers are down, they won't able to deliver the NS records to tell the client's resolver to continue the lookup process through a delegated name server.
Consider if using DNS "A" or "CNAME" records at the parent's DNS server would be acceptable alternative.
For more detail on how DNS resolution is delegated see this answer on serverfault.com:
How exactly should I set up DNS to delegate authority for subdomains?
Let's say I register the domain name mydomain.com using GoDaddy (or any other registrar). Then I immediately delegate the domain to Azure (i.e change the NS records for the domain to point to Azure's name servers). As far as I understand I would then use Azure's DNS admin tools exclusively to add/change/delete DNS records fot my domain.com.
But do I still need to have any type of relation with GoDaddy (or whichever registrar I used to register mydomain.com)? For example, if I would like to delegate my domain once more from Azure to some other nameserver would I do this through Azure or GoDaddy? Or when I need to renew my domain name, would I have to do this through GoDaddy? Or if my GoDaddy account is hacked, would mydomain.com be at risk somehow? Or would GoDaddy be involved with mydomain.com in some other way I haven't considered?
The registrar is still key in almost every situation.
They are the people you pay your subscription/fee for the domain name (normally every few yrs depending on the domain).
They are the 'tag' holder (in the case of .uk names some info here) which means they are the ones you have to approach if you wanted to move your actual name (and payment) to another registrar (e.g if you decided you didn't like GoDaddy any more you could move to Namesco, or someone else) .com domains have a similar setup
Renewals and any changes to the account or domain name would go via the registrar - this includes any further/new delegation you might do.
If your registrar account gets hacked then anything associated with that account is 'at risk' this includes the hijacking of the domain name to be pointed anywhere.
Your registrar is usually the controlling name server (Check the whois records) so any query would hit them first before any delegations you have in place.
You talked about further delegation of your domain; so presuming one day you decide to move from Azure to AWS (say) then you would go back to your registrar portal and update the NS records to point to your new IP(s) on your new host.
You can either you manage all your DNS via your registrar, or delegate the NS records (as you have already) and run your own DNS Server. In your setup you use the Azure (or whatever) tools to manage your actual records, but you would need to go back to the registrar to manage the NS records that controlled the delegation of the domain. You should note that not all registrar will allow the delegation of NS records and in effect 'force' you to use there own portal/DNS tools so check carefully.
The short of it is - you still have and must maintain any relationship
with the registrar.
I have a domain (for example test.example.com) that I wish to forward to my own network for Active directory purposes. The network already has a static IP address, and a DNS server set up that is successfully handling requests for the Domain controller internally.
What I can't figure out is how to set it up so that I can connect to the Domain Controller from outside my Local network.
We use Names.co.uk for hosting, I've been messing around with the DNS settings for about a week, but the names will not resolve. can anybody explain what I need to dO?
FYI I've tried adding the SRV records to the names.co.uk DNS server, but they do not resolve back to the DC, I've also tried adding a NS record for the names.co.uk DNS server to get my DNS to resolve it, but that doesnt seem to work either!
DNS is resolves names using a hierarchy, with each level requiring NS record listing the low-levels. E.g. test.example.com: the 'com' zone has NS records for the 'example.com' nameservers and the 'example.com' zone has NS records for the 'test.example.com' nameservers.
So, not knowing your domain name, I can't check how it resolves. But I can say that to make it visible to the rest of the world, you need to have NS records created in the parent domain which point to your own nameservers (which should also contain NS records for your domain to pointing to themselves).