New answers tagged

2

A CNAME resource record cannot point at a zone, RFC1034: "If a CNAME RR is present at a node, no other data should be present; this ensures that the data for a canonical name and its aliases cannot be different." Therefore you can't have a CNAME and an SOA called mydomain.org, so they are partly correct. However, www is not special, it's just a string and ...


1

A CNAME (Alias) record points to an A (Host) record. You can create multiple CNAME records and point them to an A record. The most common CNAME record used is the subdomains www, which is supported by every provider. You can also use Route53 to create A or CNAME. it supports 'www'. Cheers!! Tested Solution : Update - To solve your problem you can use ...


3

This is utter nonsense. A CNAME record can be as arbitrary as an A record. This crap together with the fact they need emails to change records is a clear hint to run! Edit: To avoid confusion: Having a CNAME point to the zone itself (like example.com instead of www.example.com, this is called the Apex) is not possible, but I thought you wanted to have ...


4

Is it fine that dns.aisp.net is not the authoritative domain server for bbbbbbbb.com pointed to by the CNAME record, and contains no information about bbbbbbbb.com or www.bbbbbbbb.com? Yes. This is fine. Will it prevent any modern software/browser/OS from accessing www.aaaaaaaa.com? No. As HBruijn mentions in his comment, the CNAME can point ...


1

The AWVerify record is only used at the time you add the the hostname to your resource in Azure, after that it is no longer required and can be removed.


0

The point is: CNAME is an alias to example.mydomainname.com, which resolves into ip address. So when you type in your browser acustomdomain.com DNS gives you ip of example.mydomainname.com . That's the only thing CNAME does. So in your request to server you will have http-header "Host: acustomdomain.com". Apache knows nothing about it, but there is Default ...



Top 50 recent answers are included