New answers tagged cname-record
Your registrar and your DNS provider can be different companies. If you can change just the NS records to point to another provider (such as Route53 or DynDNS for example) then your registrar will not be hosting your DNS any more. Your registrar should take care of the glue records for you but may not. It will still work if they don't but may be less ...
The problem is fixed. It works. It seems that my browser cache displayed the website from the old server. Now it displays the website from the new server. Like Kamil Šrot mentioned, we need to wait a few hours for the domain to propagate the dns records change.
You can do both. If you use A records for all your ip addresses you must change each and every record affected every time you need to change the ip address, e.g., when you change the ip address of a server. Using CNAME records enable you to group the ip addresses in a logical way so you often only need to change a few entries, e.g., an A record to change ...
What DNS server are both machines running? Microsoft? BIND? There should be a way for you to automate migration, which would do the 100 domains for you. Heck, you could even ask for access to do a domain transfer (AXFR) and get the domains that way.
Using Google's public DNS servers, the expiration of the A record causes a query of the CNAME record as well, even if the CNAME has a longer TTL. We painfully experienced that because the DNS provider charged us for DNS queries. The CNAME hosted by the DNS provider had a TTL of several days. The TTL of the A record was hosted on Windows Azure with a TTL of ...
example.com: "example" = domain name ".com" = generic domain extension When you say "example.com is a subdomain of com, and com is a subdomain of " this statement is incorrect. Sub-domains also called DNS records are what goes before any domain name. www.example.com mail.example.com webmail.example.com "www" is a subdomain, so is "mail" so is ...
Top 50 recent answers are included