<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dns on Simon Shine</title><link>https://simonshine.dk/tags/dns/</link><description>Recent content in Dns on Simon Shine</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 29 Jan 2022 16:21:50 +0100</lastBuildDate><atom:link href="https://simonshine.dk/tags/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>A Terraform DNS moment</title><link>https://simonshine.dk/articles/a-terraform-dns-moment/</link><pubDate>Sat, 29 Jan 2022 16:21:50 +0100</pubDate><guid>https://simonshine.dk/articles/a-terraform-dns-moment/</guid><description>&lt;p&gt;&lt;strong&gt;tl;dr:&lt;/strong&gt; I stuck the IPv4 and IPv6 address of my VPS into an SPF record field text.&lt;/p&gt;
&lt;p&gt;I manage my DNS with Terraform. This means that past domain registration and changing nameservers, I manage DNS with the Terraform command-line interface and git. Today I experienced a moment of happiness when two pieces of personal infrastructure fitted.&lt;/p&gt;
&lt;p&gt;The scenario: I&amp;rsquo;m setting up a send-only email server on a VPS for Gitea notifications. If this works out well, I will consider using it for a newsletter. Doing this on a commercial cloud VPS means that my server&amp;rsquo;s IPv4 address gets a bad score. One way to improve on that score is to add an &lt;a href="http://www.open-spf.org/SPF_Record_Syntax/"&gt;SPF record&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>