Re: 9.18 behavior change for mDNS queries with dig
Neither wireshark or nor tcpdump (AFAIK) can return the data in a form suitable for use in a shell script (my need was (emphasis on “was”, I’ve already re-worked my configuration to no longer need the lookup) get the current address of example.local and then use it in the shell script). In any event, the bug report was submitted and the response was that dig was never intended to be used for mDNS queries and that it did until 9.18 was just luck. Changes made in 9.18 make it no longer work but since that was never a documented use of dig, there are no plans to make it work again. I am satisfied with that response and since my use of dig for mDNS lookups was legacy code in my script that was no longer needed (there was another way to accomplish the end goal of the script), it was a good excuse to clean up the script. -- Larry Stone lston...@stonejongleux.com > On Jul 1, 2022, at 6:12 AM, Greg Choules via bind-users > wrote: > > Wireshark works just fine on a Mac (I am using it right now) and yes, it is a > great tool. You also have the choice of using tcpdump in a terminal window, > if that's your preference. Personally I usually capture using tcpdump and > view later in Wireshark. > > On Fri, 1 Jul 2022 at 12:01, Petr Menšík wrote: > Wireshark is a great tool with a nice GUI, which can record you traffic > on selected ports. Just use capture filter port 5353. But I am not > certain it works on Mac just as it does not Linux. > > On 6/27/22 15:10, Larry Stone wrote: > > Petr, you are going to have to tell me how to create an appropriate PCAP > > file. As most of this stuff works so well these days, it’s been years since > > I had to do any sort of packet level analysis (moved on to other things > > professionally) and what I knew of how to do that has long since been lost. > > My issue is on a small home network so very little goes wrong. The > > appropriate tcpdump command to get what is needed should be all I need. > > > > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from > this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from > this list > > ISC funds the development of this software with paid support subscriptions. > Contact us at https://www.isc.org/contact/ for more information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: 9.18 behavior change for mDNS queries with dig
Wireshark works just fine on a Mac (I am using it right now) and yes, it is a great tool. You also have the choice of using tcpdump in a terminal window, if that's your preference. Personally I usually capture using tcpdump and view later in Wireshark. On Fri, 1 Jul 2022 at 12:01, Petr Menšík wrote: > Wireshark is a great tool with a nice GUI, which can record you traffic > on selected ports. Just use capture filter port 5353. But I am not > certain it works on Mac just as it does not Linux. > > On 6/27/22 15:10, Larry Stone wrote: > > Petr, you are going to have to tell me how to create an appropriate PCAP > file. As most of this stuff works so well these days, it’s been years since > I had to do any sort of packet level analysis (moved on to other things > professionally) and what I knew of how to do that has long since been lost. > My issue is on a small home network so very little goes wrong. The > appropriate tcpdump command to get what is needed should be all I need. > > > > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users > -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: 9.18 behavior change for mDNS queries with dig
Wireshark is a great tool with a nice GUI, which can record you traffic on selected ports. Just use capture filter port 5353. But I am not certain it works on Mac just as it does not Linux. On 6/27/22 15:10, Larry Stone wrote: Petr, you are going to have to tell me how to create an appropriate PCAP file. As most of this stuff works so well these days, it’s been years since I had to do any sort of packet level analysis (moved on to other things professionally) and what I knew of how to do that has long since been lost. My issue is on a small home network so very little goes wrong. The appropriate tcpdump command to get what is needed should be all I need. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux
On 6/10/22 12:53, Reindl Harald wrote: PIDFile shouldn't be needed at all - esepcially for threaded services it's useless, systemd knows the PID anyways if that option is used in the provided systemd-unit one should ask the guy who have written it: why? if it would be useful my "ExecReload=/usr/bin/kill -HUP $MAINPID" won't work for nearly 10 years without "PIDFile" (no i won't use and configure rndc - keep it simple) PIDFile is required on type=forking services. And type=forking services is required to report success or failure during systemctl start named. Your custom workflow may not need it, but it is still useful and there is a reason why it is still used. rndc is quite a cool thing. running your named without it prevents several great debugging checks. YMMV. Petr -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
