Zero DNS setup with Copilot: what it means for SL devs

The zero DNS configuration demo GitHub just published is being read as "AI does your DNS for you." I read it differently. What GitHub actually showed is that fiddly, half-remembered ops steps — A records, CNAME entries, TTLs — can now be described in plain English and executed by a tool. That's a bigger shift than one custom domain going live.

The source is GitHub's own post, breaks down registration and renewal so the gap between "$2 gTLD" and "annual .lk" is clear before you decide.

Bottom line: The Copilot flow is fantastic for a $2 gTLD demo. For a real .lk presence, you're still doing it the manual way — so learn the DNS basics anyway.

🛠️ How I'd adapt this workflow on a learning budget

The pattern generalises well beyond this one demo. You don't need Namecheap or even a paid domain to get most of the benefit. Here's how I'd sequence it for a student or solo builder here:

1. 
   Ship on the free subdomain first. A public repo with Pages enabled gives you username.github.io with HTTPS, zero cost, zero DNS. Prove the site works before spending anything.


2. 
   Buy the cheapest gTLD you'll actually keep. Skip the $2 impulse buy you'll forget to renew. Renewal price matters more than first-year price.


3. 
   Let the tooling do the wiring — but read the diff. Copilot asks before it writes records. Actually look at what it's changing so you learn the shape of a correct Pages config.


4. 
   Verify like the demo did. Confirm DNS resolves and the site returns HTTP 200 before you tell anyone the link.

The deeper reason to pay attention: a registrar skill today means a cloud provider, CI runner, or DNS host skill tomorrow. The interface to your infrastructure is quietly becoming a chat prompt with a confirmation step, and the people who understand what's underneath will get more out of it than the people who don't.

💡 What this means for you

If you're learning to ship, this lowers one real barrier: you can have a public site on your own domain in an afternoon, with HTTPS handled for you. That's worth doing for the confidence alone.

But don't outsource the understanding. The Copilot skill is a fast path over DNS, not a replacement for knowing what an A record is — and the moment you want a .lk domain, the automation stops and the manual knowledge starts. Use the tooling to move quickly, read every change it proposes, and price your options before you buy. Start on the free github.io subdomain today, and only reach for a custom domain when you have something worth putting a name on.