<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks for this. Although I understand perfectly what that
article says to do, I find it interesting that I added a
reverse-DNS record yesterday for the IPv6 address and that's when
things went wrong. Will have to study this a bit more before
diving in and fixing it.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 10/7/2024 11:28 AM, Colin Watson
wrote:<br>
</div>
<blockquote type="cite" cite="mid:ZwP-KGbPZB9yBTVC@riva.ucam.org">
<pre wrap="" class="moz-quote-pre">On Mon, Oct 07, 2024 at 11:03:16AM -0400, Steve Matzura wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">dig -x 92.243.26.209 +short
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">[...]
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">What did I break, or what is ghst.net? Why doesn't dig report my FQDN
correctly?
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
ghst.net belongs to Gandi, who also own the IP range containing
92.243.26.209. The reverse DNS would need to be in their zone file,
since it's their IP range.
Does
<a class="moz-txt-link-freetext" href="https://docs.gandi.net/en/cloud/resource_management/network_interface_management.html">https://docs.gandi.net/en/cloud/resource_management/network_interface_management.html</a>
help?
</pre>
</blockquote>
</body>
</html>