Re: 9.18 behavior change for mDNS queries with dig

2022-07-01 Thread Larry Stone
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

Re: 9.18 behavior change for mDNS queries with dig

2022-07-01 Thread Greg Choules via bind-users
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 wro

Re: 9.18 behavior change for mDNS queries with dig

2022-07-01 Thread Petr Menšík
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

Re: Unable to start Bind on a fresh RHEL 8.6 system with enforcing SELinux

2022-07-01 Thread Petr Menšík
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=/