Smash Notes

Back to Is it always DNS? with DNSimple's Anthony Eden, with Anthony Eden.

How Did DNSimple Move Names Back and Forth With Azure?

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.

Transcript

Is it always DNS? with DNSimple's Anthony Eden ·

Hanselminutes with Scott Hanselman

More from this episode

  1. Why Does Microsoft Call Cloud Names on Dot Microsoft Safer?On Hanselminutes, Microsoft is starting to move cloud services to the dot Microsoft top-level domain, and Microsoft says the change is more secure.
  2. How Did No Outside Money Keep DNSimple on Domains?On Hanselminutes, DNSimple has always been funded by bootstrapping and has never taken outside funds.
  3. Why Does DNSimple Push Domain Changes as Far as Australia?DNSimple gets record changes out through its own internal transfer system, and the bar for that system is Australia.

People

More answers like this

The other side

More with Anthony Eden

Related episodes

Plays from this note through the rest of the episode.

Weekly highlights

One letter a week.

The notes worth hearing, with the minute they were said.