'dig' reports strange results

[Steve Matzura]

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.


On 10/7/2024 11:28 AM, Colin Watson wrote:
> On Mon, Oct 07, 2024 at 11:03:16AM -0400, Steve Matzura wrote:
>> dig -x 92.243.26.209 +short
> [...]
>> What did I break, or what is ghst.net? Why doesn't dig report my FQDN
>> correctly?
> 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
> https://docs.gandi.net/en/cloud/resource_management/network_interface_management.html
> help?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20241007/6d8eaba1/attachment-0001.html>