<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>What are your corporate policies on subzone creation and the maintenance of them?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We have created numerous subzones and delegated them to AWS private hosted zones for our ‘move to the cloud’ efforts. This has resulted in a sprawl of subzones. Does anyone else have thoughts on how to manage the number of zones? How do you maintain currency on them – like identifying ones that are abandoned and should be removed?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sue Steffen<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>