Smash Notes
How Did Dnsimple's Domain Control Plane Let Zones at Azure and at Dnsimple Sit Side by Side and Move Back and Forth?
On Hanselminutes, a dashboard can show 41 registered domains beside 47 DNS zones. DNSimple says the extra zones might be a domain registered somewhere else and pointing at DNSimple, or a name that was never registered.
The domain control plane came from a limit DNSimple states outright: everybody using DNSimple all the time is not a reality. Some people mix DNSimple with Route 53, Azure DNS, other providers, or on-premise DNS like Core DNS. DNSimple built a way to connect into the other systems. From within DNSimple, zones at Azure and at DNSimple can be managed side by side in a bi-directional fashion and moved back and forth.
Hanselminutes with Scott Hanselman
·
Is it always DNS? with DNSimple's Anthony Eden
·
at 19:11
·
·Transcript
People
On this episode
- Why Does Microsoft Say Controlling the Dot Microsoft Registry Makes Cloud Names More Secure Than Dot Com by Leaving One Less Point Somebody Can Attack? Transcript
- How Did Dnsimple's Domain Control Plane Let Zones at Azure and at Dnsimple Sit Side by Side and Move Back and Forth? Transcript
- Why Does Dnsimple Push Record Changes to Eight Points of Presence, as Far as Australia, With Its Own Transfer System and a Low Time to Live Instead of a One-day Default? Transcript
You might also like
- How Did Anthony Eden Turn a Perl Alias Script Into an Erlang Name Server So a Naked Domain Could Point at Heroku?
- How Did the Last Couple of Years of Registrar Investment Make Dnsimple Split Almost Evenly Between Domain Registration and Operational Domain Name System Work?
- How Did a Few Months Building a Knowledge Base Pull Dnsimple Back to Staying Focused?
- How Did Dnsimple Replace a User-equals-account Login With a Many-to-many Relationship So One User Can Reach Many Accounts?