amazon-route53amazon-web-servicescname-recorddomain-name-systemsoa-record
Does setting the refresh time in an SOA record make newly created DNS records "propagate" faster? (I understand the term propagate is technically inaccurate)
I'm making many new DNS records (A records to assign subdomains to each new user on the site), and I'd like for that subdomain to be available ASAP after a user signs up. So I'm looking for ways to speed up the rate at which DNS servers check for new DNS records.
Is this possible with the refresh time in the SOA? Or somewhere else?
In order to do this, you will need an NS record on the zone hosted at DnsMadeEasy for each subdomain. This action is called "delegating a subdomain" to an external DNS server. Here's the DNS Made Easy guide for that.
For instance, you would need an NS record in the parent zone for: tenant1.example.com, which points to the four namserver addresses assigned to you when you create a tenant1.example.com hosted zone in Amazon Route 53.
Create your hosted subdomains in Amazon Route 53:
Then make sure DNS Made Easy has an entry like this for each subdomain:
CNAMES are not redirections, they are aliases. CNAME also includes all other resource records such as A,MX,TXT.
so if you query for an A record, the cname will send you to the A record of it's alias.
Many registrars include additional options such as redirect services, godaddy and Google for example.
also, be careful entering values for CNAMES, some systems assume terminating periods, others do not.
assuming domain example.com
test IN CNAME example.org
results in test resolves to the IP of host example.org.example.com which does not exist.
test IN CNAME example.org.
results in test resolves to the IP of host example.org which does exist.
CNAME values can only be HOSTS, not a URL.
dig A keep.richardyang.ca @8.8.8.8
keep.richardyang.ca. 299 IN CNAME https://keep.google.com/.
Change it to
keep.richardyang.ca. 299 IN CNAME keep.google.com.
Maybe check out https://stackoverflow.com/questions/10115799/set-up-dns-based-url-forwarding-in-amazon-route53
Example on how to use Synthetic records with Google.com Domains.
;; ANSWER SECTION:
keep.jacobdevans.com. 3600 IN CNAME ghs.googlehosted.com.
ghs.googlehosted.com. 163 IN A 173.194.207.121
This sends my request to google's servers, google then sends a 302 code to the new url, I've chosen 302, you would want 301 if you want SEO to know this is a permanent change, I may want to switch my destinations at a later time as I use this for my signature links to ensure my contact info stays current.
OR, since you already have a website, point the domain there and redirect the site.
Script:
<script type="text/javascript">
if (window.location.href== "http://keep.richardyang.ca") {
window.location.href = 'http://keep.google.com';
}
</script>
DNS:
keep.richardyang.ca. 299 IN CNAME richardyang.ca.
Best Answer
New A records shouldn't have any propagation delay at all, since they aren't cached anywhere. Any DNS client that can't find your new record in a cache should be going direct to your authoritative servers. It's only changes to existing records that can suffer from a delay.