<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/16dff02ee5604b7daf3ebc7c9c93d8a4&quot; frameborder=&quot;0&quot; width=&quot;2574&quot; height=&quot;1930&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1930</height><width>2574</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1930</thumbnail_height><thumbnail_width>2574</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/16dff02ee5604b7daf3ebc7c9c93d8a4-dc6c02aa6a85c87b.gif</thumbnail_url><duration>173.241</duration><title>Streamlining DNS Changes with Dual Control</title><description>This Loom discusses building a workflow to make DNS record update proposals and approvals easier and more secure. The author explains that someone can share DNS update instructions from a website or copy and paste via email or Slack, which the system turns into a proposal for approval. For sensitive DNS changes, they want a dual-control or multi-person approval flow with full audit history of who proposed and approved changes and when. They also ask for feedback on UI design observations of how AI-generated interface output can be overly verbose and poorly structured, and whether others have experienced similar issues.</description></oembed>