I want type domain.com at browser, then connect www.domain.com likes type google.com to connect www.google.com.
The information below is currently set.
domain.com. NS ns-1623.awsdns-10.co.uk.
ns-1461.awsdns-54.org.
ns-180.awsdns-22.com.
ns-880.awsdns-46.net.
domain.com. SOA ns-1461.awsdns-54.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
*.domain.com. A XXX.XXX.XXX.XXX
What should I do if you would like to do this?
You want to use DNS redirection with a CNAME entry/record. Check out this link.
Basically, you create a record that refers to some other A record (or, perhaps, another CNAME in some circumstances). You can set this up for any number of subdomains (www, www2, mail, home, etc.).
Related
We are running BIND 9.9.7 on Centos 6.5 and for a long time I have been creating "hostless" DNS entries so that sites work with or without the www.
Eg:
www IN A 192.168.1.1
domain.com. IN A 192.168.1.1
However, our client wants to use a CNAME record to a cloudfront host and the "hostless" entry doesn't work as a CNAME record.
In fact, it more than doesn't work, BIND won't even load the zone file. The error is
"failed: CNAME and other data"
domain.com. IN CNAME host.cloudfront.net.
www IN CNAME host.cloudfront.net.
It will load and resolve fine without the domain.com entry. I have tried a few variations, but nothing seems to work. including "", "."
Can anyone tell me the correct syntax for this entry?
There is no correct syntax for this (and it is not BIND specific, it is a side effect of RFC1912 which states that A CNAME record is not allowed to coexist with any other data.
Detailed explanation: Why can't a CNAME record be used at the apex (aka root) of a domain?
Some DNS providers might offer workaround hacks.
This question must be so basic that I am bewildered why I cannot find a clear answer.
I want to configure my DNS for a new domain name. I configure the A record with the IP address of my host server. domain.com works fine. But how do I configure the CNAME to create the www. alias? It won't accept an IP address, and aliasing it to domain.com does not seem to work.
The following record should work:
www IN CNAME domain.com.
Make sure you have the . at the end of domain.com.. Names that don't end with . automatically get the origin appended, so it would be treated as domain.com.domain.com..
I have my domain example.com on CloudFlare and a subdomain, fo.example.com, delegated to another name server.
This is the setting on CloudFlare
A www.example.com 1.2.3.4
CNAME test www.example.com
CNAME test2 www.google.com
CNAME test3 fo.example.com
plus the NS for fo. All the above have the orange icon, i.e. requests should go through CloudFlare.
and this is the setting on the other nameserver
A fo.example.com 5.6.7.8
Now, when I traceroute www.example.com, test.example.com and test2.example.com I can see that it goes through CloudFlare but when I traceroute test3.example.com it goes direct exactly as I traceroute fo.example.com. This looks incorrect to me, why requests to a CNAME pointing to an extrenal domain (google.com) goes through cloudflare and the one pointing to a delegated subdomain does not?
Very difficult to look at without knowing the actual subdomain in question. There are some records that can't be proxied (pointing to other CDNs, for example, does create DNS lookup issues in some cases).
CloudFlare supports answer:
That's not possible, no way around it either. I've tried.
Unfortunately our current system doesn't allow this. This has been a
feature request for awhile, it will get added eventually, but no ETA
as of right now, sorry.
Ok so I did everything tumblr asks to use a custom domain
A record pointing mydomain.com to 66 6 44 4
A record pointing www mydomain com to 66 6 44 4
Cname - pointing to domains tumblr com
And Tumblr says we don't have to change/erase our nameservers
BUT turns out that mydomain keeps opening the website from my server, instead of tumblr. Which sounds natural to me, so I can't understand how can the A record own my domain instead of the nameserver?
1-) I can't leave the nameserver empty, my domain hoster doesn't allow
2-) tumblr doesn't allow their IP to be pointed as nameservers.
help :(
What you did is right, all you need are A records for domain.com and for www.domain.com. Nameservers are not relevant here.
The fact that your setup does not work originates from some other reason, maybe old records cached somewhere etc...
My DNS has a set up for the domain base.com that consists of A and MX records. There are several other domains that are set up with CNAME records, pointing to base.com.
Do I need to set up anything special (like extra MX records) for the CNAME domains, or will the CNAME records also forward any MX requests.
Example:
Will an email sent to info#otherdomain.com be delivered correctly to the MX of base.com if these (and only these) DNS records are in place:
; A and MX set up for base.com
base.com. 3600 IN A 123.45.67.89
mail.base.com. 3600 A 123.45.67.89
base.com. 3600 IN MX 10 mail.base.com.
; CNAME set up for otherdomain.com
otherdomain.com. CNAME IN A base.com.
CNAME causes queries for all RR types (excluding CNAME itself) to be directed to the target name. That includes MX. So yes, the above zone data will cause queries for otherdomain.com.'s MX to resolve to mail.base.com..
Experiment with dig or your favorite DNS client. Not only will you confirm the result for sure, but you won't have to wait 4 hours for someone to answer your SO question before you get your answer!
Unfortunately, in this particular case, if your domain is really of the form otherdomain.com., you would not be able to configure a CNAME resource records for it. This is because domains that have CNAME records cannot have any other type of resource record at the same time. Yet if otherdomain.com. is directly below com. (or another gTLD), it is necessarily at the top of a zone and so it needs at least SOA and NS records.