Route 53

Use AWS Route 53 as the DNS provider for your Stackryze Domain.

​

Why Route 53?

• Highly reliable — 100% uptime SLA with global DNS infrastructure.
• Advanced routing — traffic flow, geolocation, and failover policies.
• Full control — complete DNS record management.
• Scalable — enterprise-grade DNS for production workloads.
• AWS integration — seamless with other AWS services.

​

Prerequisites

Before you begin:

• ✅ A registered Stackryze Domain on domain.stackryze.com.
• ✅ An AWS account — sign up here.

​

Step 1 — Open Route 53 in the AWS console

1. Sign in to the AWS Console.
2. In the search bar, search for Route 53.
3. Click the service.

​

Step 2 — Open Hosted zones

1. In the left sidebar, click Hosted zones.
2. Click Create hosted zone.

​

Step 3 — Create the hosted zone

1. Enter your full subdomain (for example yourname.indevs.in — or whichever of the four Stackryze namespaces you registered under).
2. Fill in the details:
   • Domain name: your complete subdomain from Stackryze.
   • Type: select Public Hosted Zone.
   • Description: (optional) add a note.
3. Click Create hosted zone.

​

Step 4 — Copy the nameservers

Route 53 assigns four nameservers:

1. Find the NS record in your hosted zone.
2. You’ll see four nameservers:
   ns-123.awsdns-45.com
   ns-678.awsdns-90.net
   ns-1234.awsdns-56.org
   ns-5678.awsdns-12.co.uk
   
3. Copy all four — you’ll need them in the next step.

​

Step 5 — Update nameservers in Stackryze Domains

1. Open domain.stackryze.com.
2. Go to My Domains.
3. Click your domain.
4. In DNS Configuration, click Edit.
5. Replace the nameservers with your Route 53 ones.
6. Click Save.

See Managing domains → Updating nameservers for the full walkthrough.

​

Step 6 — Create a record

Add DNS records in Route 53:

1. Select your hosted zone.
2. Click Create record.

3. Select a record type and fill in the form:
   • Record name: @ (for root) or your subdomain.
   • Record type: A, CNAME, AAAA, MX, etc.
   • Value: your target value (IP address, domain, etc.).
   • TTL: 300 (5 minutes) or your preferred value.
   • Routing policy: Simple routing (or an advanced policy).
4. Click Create records.

That’s it — all steps are complete.

​

SSL configuration

Route 53 provides DNS only — SSL certificates must be managed by your hosting provider or AWS services. For common hosting platforms:

• Vercel / Netlify — automatic SSL provisioning.
• GitHub Pages — automatic SSL after DNS verification.
• AWS services (CloudFront, ALB, API Gateway) — use AWS Certificate Manager (ACM) for free SSL.
• Custom server — use Let’s Encrypt or a commercial certificate.

​

Common issues

​

Hosted zone not created

• Confirm your IAM permissions include Route 53.
• Confirm you selected Public Hosted Zone.
• Confirm the subdomain format is correct.

​

DNS not resolving

• Confirm nameservers are correct in the Stackryze Domains dashboard.
• Wait 10–30 minutes for propagation.
• Check DNS records in Route 53.
• Verify with DNS Checker.
• Confirm all four nameservers are entered.

​

High costs

• Review Route 53 pricing before use.
• Monitor query volume in CloudWatch.
• Consider Route 53 only for production domains.
• Use free providers for development and testing.

​

Advanced features

• Traffic Flow — visual traffic policy editor.
• Health Checks — monitor endpoint availability.
• Routing Policies — weighted, latency, geolocation, failover.
• DNSSEC — Domain Name System Security Extensions.
• Query Logging — log DNS queries to CloudWatch.

​

Resources

• Route 53 documentation
• Route 53 pricing
• AWS Certificate Manager
• DNS propagation checker

​

Need help?

• Discord community
• Email support