'dig' reports strange results

Steve Matzura sm at noisynotes.com
Mon Oct 7 15:03:16 UTC 2024


Yestrday I used 'dig' to help figure out that I was missing a 
reverse-DNS record in my domain's zone file. I typed:


dig -x 92.243.26.209 +short


and I got: a correct response. Today when I do that, I get:


xvm-26-209.sd6.ghst.net


Thinking something went wrong somewhere, I looked into this a little 
further:


$ resolvectl status

Global
          Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
   resolv.conf mode: stub

Link 2 (enX0)
     Current Scopes: DNS
          Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS 
DNSSEC=no/unsupported
Current DNS Server: 155.133.140.130
        DNS Servers: 155.133.140.129 155.133.140.130 155.133.140.131
         DNS Domain: openstacklocal


What did I break, or what is ghst.net? Why doesn't dig report my FQDN 
correctly?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20241007/4a557250/attachment.html>


More information about the ubuntu-users mailing list