RFC8482 and engine-setup
Hello All, recently I have changed my firewall and DNS server and I have noticed that engine-setup warns with: Failed to resolve engine.localdomain using DNS, it can be resolved only locally. The command used was: 'dig +noall +answer FQDN ANY' It seems that according to RFC8482, ANY is deprecated and DNS can return anything.Once such example is the output of 'dig wikipedia.org ANY' . What are our options now ? I guess we can query for A and AAAA records ? Extra info: https://blog.cloudflare.com/rfc8482-saying-goodbye-to-any/ Best Regards,Strahil Nikolov
Hi All, Short update: I've opened a bug for this -> https://bugzilla.redhat.com/show_bug.cgi?id=1971863 Best Regards, Strahil Nikolov В понеделник, 14 юни 2021 г., 09:20:13 ч. Гринуич+3, Strahil Nikolov <hunter86_bg@yahoo.com> написа: Hello All, recently I have changed my firewall and DNS server and I have noticed that engine-setup warns with: Failed to resolve engine.localdomain using DNS, it can be resolved only locally. The command used was: 'dig +noall +answer FQDN ANY' It seems that according to RFC8482, ANY is deprecated and DNS can return anything. Once such example is the output of 'dig wikipedia.org ANY' . What are our options now ? I guess we can query for A and AAAA records ? Extra info: https://blog.cloudflare.com/rfc8482-saying-goodbye-to-any/ Best Regards, Strahil Nikolov
participants (1)
-
Strahil Nikolov