Re: What to report for "refresh: failure trying master ... operation canceled" bug?

2016-11-23 Thread Bob Harold
On Mon, Nov 21, 2016 at 7:02 PM, schilling wrote: > added both tcp and udp port 53, still seeing the log messages. > > Best, > > Shiling > > On Mon, Nov 21, 2016 at 5:45 PM, Anand Buddhdev wrote: > >> On 22/11/2016 00:27, schilling wrote: >> >> > Thanks

Re: What to report for "refresh: failure trying master ... operation canceled" bug?

2016-11-21 Thread schilling
added both tcp and udp port 53, still seeing the log messages. Best, Shiling On Mon, Nov 21, 2016 at 5:45 PM, Anand Buddhdev wrote: > On 22/11/2016 00:27, schilling wrote: > > > Thanks for the insight. > > I added the following rule > > sudo firewall-cmd --permanent --direct

Re: What to report for "refresh: failure trying master ... operation canceled" bug?

2016-11-21 Thread Anand Buddhdev
On 22/11/2016 00:27, schilling wrote: > Thanks for the insight. > I added the following rule > sudo firewall-cmd --permanent --direct --get-all-rules > [sudo] password for admin: > ipv4 filter OUTPUT 0 -d 10.10.10.100 -p tcp -m tcp --dport=53 -j ACCEPT > where 10.10.10.100 is our DNS master,

Re: What to report for "refresh: failure trying master ... operation canceled" bug?

2016-11-21 Thread schilling
Thanks for the insight. I added the following rule sudo firewall-cmd --permanent --direct --get-all-rules [sudo] password for admin: ipv4 filter OUTPUT 0 -d 10.10.10.100 -p tcp -m tcp --dport=53 -j ACCEPT where 10.10.10.100 is our DNS master, still receiving the error. I found a solution for

Re: What to report for "refresh: failure trying master ... operation canceled" bug?

2016-11-21 Thread Mark Andrews
In message , schilling writes: > > We are experiencing this bug with BIND 9.9.4-RedHat-9.9.4-29.el7_2.4 > (Extended Support Version) running as slave on Red Hat Enterprise Linux > Server release 7.2 (Maipo). > disable firewalld

Re: What to report for "refresh: failure trying master ... operation canceled" bug?

2016-11-21 Thread schilling
We are experiencing this bug with BIND 9.9.4-RedHat-9.9.4-29.el7_2.4 (Extended Support Version) running as slave on Red Hat Enterprise Linux Server release 7.2 (Maipo). disable firewalld seems to stopped the error logging. But as soon as re-enable firewalld, the messages came back. Do we have any