<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Perhaps this message when using /usr/bin/dig without +short might be the answer…?<br class=""><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 13px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">;; Got answer:</span></div><div style="margin: 0px; font-stretch: normal; font-size: 13px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">;; WARNING: .local is reserved for Multicast DNS</span></div><div style="margin: 0px; font-stretch: normal; font-size: 13px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">;; You are currently testing what happens when an mDNS query is leaked to DNS</span></div><div style="margin: 0px; font-stretch: normal; font-size: 13px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div style="margin: 0px; font-stretch: normal; font-size: 13px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">I guess the MacPorts version considers this a security issue?</span></div><div style="margin: 0px; font-stretch: normal; font-size: 13px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><blockquote type="cite" class=""><div class="">On 26 Jun 2022, at 04:56, Larry Stone <<a href="mailto:lstone19@stonejongleux.com" class="">lstone19@stonejongleux.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I’m fairly new to MacPorts and just installed it on a Macintosh I use for, among other thing, network monitoring. One of things it does is check that other computers on our network are up by getting the current IP address for the computer by using dig to make a mDNS query (dig +short @224.0.0.251 -p 5353 hostname.local). <br class=""><br class="">With the MacPorts version of dig provided in the Bind9 port, it fails:<br class="">/opt/local/bin/dig +short @224.0.0.251 -p 5353 hostname.local<br class="">;; connection timed out; no servers could be reached<br class=""><br class="">Using the Apple provided version in /usr/bin, it works:<br class="">/usr/bin/dig +short @224.0.0.251 -p 5353 hostname.local<br class="">192.168.0.82<br class=""><br class="">And on an older system where I had built Bind from source, it works:<br class="">/usr/local/bin/dig +short @224.0.0.251 -p 5353 hostname.local<br class="">192.168.0.82<br class=""><br class="">The MacPorts version of dig works fine for regular DNS queries. It’s only when adding "@224.0.0.251 -p 5353” for the mDNS query that it fails. Any ideas as to why this fails with the MacPorts version?<br class=""><br class="">-- <br class="">Larry Stone<br class=""><a href="mailto:lstone19@stonejongleux.com" class="">lstone19@stonejongleux.com</a><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>