* SAQUIB AKHTAR <saquib.offi...@gmail.com> [230927 02:23]: > Hi - It's a great news to see the www.vim.org hosted very quickly to new > provider. Everything now works fine. But vim.org --->does not resolves or > redirects to www.vim.org , can someone fix this by adding 1 CNAME in DNS ?
First, there have been several attempts in the past by others to convince Bram to do this. Bram was adamant that he would not. vim.org is a domain, not a host, and the host serving the Vim website is www.vim.org. (In DNS RFC parlance, a host name is also a domain name, but not necessarily the other way around.) This is an organizational decision of those running the domain; there is nothing, such as an HTTP standard, that requires or even encourages what you are asking. If the current Vim website managers want to make vim.org redirect to www.vim.org, there is nothing wrong with that, but it is entirely their decision. I have no opinion one way or the other on this. I supported Bram in the past, and will support the new maintainers whichever way they go. If they do want to make vim.org redirect, the rest of this message is important. According to the relevant RFCs (1034 and 1035), a CNAME must not be used at the apex of a zone (e.g. vim.org), so your proposed implementation is wrong (i.e. non-compliant). The alias (left side of the CNAME in a zone file) cannot have any other records associated with it (e.g. it must not be the name of an SOA, MX, SRV, or other record). If the current maintainers decide to do this, there are a few ways, but there is really only one viable way if they wish to keep the canonical name of the web server as www.vim.org: Add an A (and possibly AAAA) record for vim.org, and run a small HTTP/HTTPS server that redirects to www.vim.org. The IP address(es) for vim.org can be the same as www.vim.org if the web server handles virtual domains correctly. It should respond with a redirect (preferably 301 rather than 302) to handle browser history and caching correctly. If the website maintainers would like to change the canonical URI to vim.org, with www.vim.org redirecting to that, use the above method, just changing which host is redirected to the other. Another way (of changing the canonical to vim.org) would be to give vim.org the IP address(es) and have www.vim.org be the CNAME alias. This is standards-compliant, whereas having vim.org be the CNAME alias is not. One problem with using a CNAME is that the web browser is unaware of it; the DNS resolver simply returns the IP address for the canonical name of the alias that it was told to look up. This effectively results in two different web sites with identical content. Think about how your browser handles this. If you go to www.vim.org/about.php, and also to vim.org/about.php, the browser considers these to be two different pages. History and cache treat these as different pages. Using CNAME should be avoided when possible. It generally has non-obvious side effects, like the browser history and cache above. If you really want to have two names where one is an alias for the other, and both hames are in the same zone, simply use duplicate A and AAAA records with different names and the same IP addresses. This can have some of the same problems as CNAMEs (e.g. if the web server serves the same site from both names without redirection), but avoids extra DNS traffic to resolve the CNAME and then resolve the A record for the response. If an alias and a canonical name are in the same zone, use multiple address records rather than a CNAME record. If you still think you want a CNAME record, read the above two paragraphs again, and then reread this paragraph and follow its directions. ...Marvin -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/ZRRBis9h6jt2%2B86z%40basil.wdw.