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.
Bug 1301912 - Bind starts before all network interfaces are up during boot
Summary: Bind starts before all network interfaces are up during boot
Keywords:
Status: CLOSED DUPLICATE of bug 1294506
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bind
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Tomáš Hozza
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-26 11:16 UTC by John Cameron
Modified: 2016-05-10 08:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 08:16:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description John Cameron 2016-01-26 11:16:26 UTC 
Description of problem:
  Bind starts before all network interfaces are up during boot,
  Therefore only binds to the interfaces that are already up at the time.
  Particularly when using multiple VLAN interfaces which are
  Brought up one after the other.
Version-Release number of selected component (if applicable):
  bind-chroot-9.9.4-29.el7_2.1.x86_64
How reproducible:
  Always, depending on the amount of interfaces.
Steps to Reproduce:
 Install and configure bind-chroot
 Configure multiple VLAN interfaces with subnets from 10.1.1.1/24 to 10.1.1.10/24
 Reboot
Actual results:
  ss -tnl | grep -w 53
  LISTEN     0      10     127.0.0.1:53                       *:*
Expected results:
  ss -tnl | grep -w 53
  LISTEN     0      10     127.0.0.1:53                       *:*
  LISTEN     0      10     10.1.1.1:53                         *:*
  LISTEN     0      10     10.1.1.2:53                         *:*
  LISTEN     0      10     10.1.1.3:53                         *:*
  LISTEN     0      10     10.1.1.4:53                         *:*
  LISTEN     0      10     10.1.1.5:53                         *:*
  LISTEN     0      10     10.1.1.6:53                         *:*
  LISTEN     0      10     10.1.1.7:53                         *:*
  LISTEN     0      10     10.1.1.8:53                         *:*
  LISTEN     0      10     10.1.1.9:53                         *:*
  LISTEN     0      10     10.1.1.10:53                       *:*
Additional info:
  Fix with :
  
  sed -i "/^Requires=/ aRequires=network.target" /usr/lib/systemd/system/named-chroot.service
Comment 2 Tomáš Hozza 2016-05-10 08:16:15 UTC 

*** This bug has been marked as a duplicate of bug 1294506 ***
Note You need to log in before you can comment on or make changes to this bug.