<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Digital.gov</title>
    <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/nathan-smith/</link>
    <description>Recent content on Digital.gov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/nathan-smith/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Let’s Encrypt Those CNAMES, Shall We?</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/09/07/lets-encrypt-those-cnames-shall-we/</link>
      <pubDate>Wed, 07 Sep 2016 11:00:56 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/09/07/lets-encrypt-those-cnames-shall-we/</guid>
      <description>This is post 4 in the 5-part series, The Right Tools for the Job: Re-Hosting DigitalGov Search to a Dynamic Infrastructure Environment. This post references the previous posts frequently, so please read those before reading this one if you haven’t done so already. In addition to the DNS challenges created by offering “masked” domains such</description>
    </item>
  </channel>
</rss>
