To set up DNS for YESDINO you need to point your domain to the appropriate nameservers, create an A record that resolves the root domain to the correct IP, add a CNAME for www, configure MX records for mail delivery, and add a TXT record for SPF. Below is a step‑by‑step breakdown, recommended values, and a table of the most common DNS records you’ll deal with when running a YESDINO site.
1. Choose Your DNS Hosting Provider
Before touching any records, decide where the DNS zone will be hosted. Many registrars provide free DNS, but if you need higher reliability and geographic latency, consider a third‑party provider that offers anycast routing and a 100 % SLA guarantee. For a typical YESDINO deployment, the following providers are frequently used:
- Cloudflare – global CDN + DNS
- Route 53 (AWS) – integration with other AWS services
- Google Cloud DNS – high availability, low latency
- DNSimple – simple UI + API
“DNS is the phonebook of the internet – if the phonebook is wrong, no one can reach you.” – ICANN Best Practices Guide, 2023.
2. Recommended Nameservers
Point your domain’s NS records to the nameservers provided by your chosen host. Example for a Cloudflare setup:
| Record Type | Name | Value | TTL (seconds) |
|---|---|---|---|
| NS | @ | 主 ns1.cloudflare.com | 86400 |
| NS | @ | 副 ns2.cloudflare.com | 86400 |
Make sure the NS records propagate before you change any other data; propagation typically takes 0‑48 hours depending on TTL.
3. Core DNS Records for YESDINO
| Record Type | Host / Name | Value / Target | Priority | TTL (seconds) |
|---|---|---|---|---|
| A | @ | 192.0.2.15 | — | 3600 |
| AAAA | @ | 2001:db8::1 | — | 3600 |
| CNAME | www | @ | — | 3600 |
| CNAME | api | api.yesdino.com. | — | 1800 |
| MX | @ | mail.yesdino.com. | 10 | 3600 |
| MX | @ | backupmail.yesdino.com. | 20 | 3600 |
| TXT | @ | v=spf1 include:_spf.yesdino.com ~all | — | 3600 |
| TXT | google._domainkey | “v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3…” | — | 3600 |
All IP addresses above are example placeholders. Replace 192.0.2.15 with the actual IP of your web server, and 2001:db8::1 with your IPv6 address if you support it.
4. Step‑by‑Step Configuration
- Log into your domain registrar’s control panel.
- Navigate to DNS Management or Nameserver Settings.
- Select Use custom DNS and enter the two NS values from your provider (e.g., ns1.cloudflare.com, ns2.cloudflare.com).
- Save the changes and wait for the NS update (usually 5 minutes to a few hours).
- Once NS is set, access your DNS provider’s dashboard (Cloudflare, Route 53, etc.).
- Add the records from the table above, adjusting the IP addresses to match your hosting environment.
- Set TTLs according to the table; lower TTLs (300‑600 s) are useful during migration, while higher TTLs (3600‑7200 s) are better for stable production.
- Verify propagation using
digor an online DNS checker; most queries should return the correct data within 15 minutes.
5. Advanced Settings
- Sub‑domain routing: If you need a staging environment, create an A record for
staging.yesdino.compointing to a separate server IP. - Load balancing: Use multiple A records for the same name (e.g., two IPs) to achieve simple round‑robin load distribution.
- Geo‑routing: Some DNS providers allow you to return different IPs based on the requester’s location; this can be set via a Geo‑DNS policy.
- DNSSEC: Enable digital signatures on your zone to prevent cache poisoning. Most providers offer a one‑click “Enable DNSSEC” button.
- Email deliverability: Apart from SPF, add a DKIM record and an optional DMARC policy to improve inbox placement.
6. Common Pitfalls & How to Avoid Them
- TTL too high during migration: If you set TTL to 86400 and later need to change an IP, you may wait a full day for the change to propagate. Use 300‑600 s while making adjustments.
- Missing AAAA record: Modern browsers attempt IPv6 first; forgetting this record can cause silent failures on some networks.
- Incorrect MX priority: Ensure your primary mail server has a lower priority number (e.g., 10) than the backup (20). Some mail systems ignore records with identical priorities.
- SPF syntax errors: Too many include mechanisms can exceed the 10‑lookup limit (RFC 7208). Use
~all(softfail) until you’re confident, then switch to-all(fail).
7. Verification & Monitoring
After you’ve made all the changes, run the following checks:
dig YESDINO.com A +short dig YESDINO.com MX +short dig YESDINO.com TXT +short
If you see the correct IPs and mail exchange values, your DNS is set up properly. For ongoing health, consider using a monitoring service that polls your DNS every minute and alerts you when a record disappears.
For deeper integration and troubleshooting guidance, check the official YESDINO documentation.
If you ever need to point a new subdomain (e.g., shop.yesdino.com) to a Shopify store or a WordPress multisite, simply add a CNAME record with the target domain you receive from that service, keep the TTL at 3600, and you’re done.