Good observation. Still, what the MacPorts version of dig is doing is not the 
default (or at least hasn’t been (see next paragraph) as I mentioned in my 
first post, I used to build BIND from source).

But one other thought I just had is it’s a change with the latest version of 
BIND. The Apple provided dig is old enough that it must be BIND 9.16 and the 
source-built version I tested with is also from the 9.16 tree. But the MacPorts 
version is from the new 9.18 tree. Unfortunately, I no longer have a 
source-built 9.18 copy of dig to test with.

-- 
Larry Stone
[email protected]





> On Jun 26, 2022, at 1:54 AM, Mark Lucas <[email protected]> wrote:
> 
> Perhaps this message when using  /usr/bin/dig  without +short might be the 
> answer…?
> 
> ;; Got answer:
> ;; WARNING: .local is reserved for Multicast DNS
> ;; You are currently testing what happens when an mDNS query is leaked to DNS
> 
> I guess the MacPorts version considers this a security issue?
> 
>> On 26 Jun 2022, at 04:56, Larry Stone <[email protected]> wrote:
>> 
>> 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). 
>> 
>> With the MacPorts version of dig provided in the Bind9 port, it fails:
>> /opt/local/bin/dig +short @224.0.0.251 -p 5353 hostname.local
>> ;; connection timed out; no servers could be reached
>> 
>> Using the Apple provided version in /usr/bin, it works:
>> /usr/bin/dig +short @224.0.0.251 -p 5353 hostname.local
>> 192.168.0.82
>> 
>> And on an older system where I had built Bind from source, it works:
>> /usr/local/bin/dig +short @224.0.0.251 -p 5353 hostname.local
>> 192.168.0.82
>> 
>> 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?
>> 
>> -- 
>> Larry Stone
>> [email protected]
>> 
>> 
>> 
>> 
>> 
> 

Reply via email to