Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: Port 53 udp & tcp are opened in firewalld, able to connect to master through port 53. But getting following failure message when firewalld is turned on info: zone xxxxxxx/xxxx: refresh: failure trying master x.x.x.x#53 (source 0.0.0.0#0): operation cancelled Version-Release number of selected component (if applicable): bind-chroot-9.9.4-38.el7_3.x86_64 How reproducible: Always when firewalld is turned on Steps to Reproduce: 1: Setup Master Slave DNS (Chroot) 2: Configure logging on Slave logging { channel chrooted_logfile { file "/var/log/named"; severity info; print-time yes; print-category yes; print-severity yes; }; channel debug_chrooted_logfile { file "/var/log/debug_named"; severity debug; print-time yes; print-category yes; print-severity yes; }; category default { chrooted_logfile; }; category notify { chrooted_logfile; }; category config { chrooted_logfile; }; category update { chrooted_logfile; }; category lame-servers { null; }; category resolver { null; }; category database { null; }; category security { chrooted_logfile; }; category xfer-in { chrooted_logfile; }; category xfer-out { chrooted_logfile; }; }; 3: Turn on firewalld on Slave 4: Check debug log Actual results: failure trying master operation cancelled Expected results: The error should not appear.