Back to bug 1294506
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Lukáš Nykrýn | 2016-01-05 11:32:55 UTC | CC | lnykryn | |
| Onmeac | 2016-01-05 12:04:57 UTC | CC | sebastiaan | |
| Carl Henrik Lunde | 2016-02-23 09:47:42 UTC | CC | chlunde | |
| Nilesh Parmar | 2016-04-20 07:33:28 UTC | Priority | unspecified | medium |
| CC | nparmar | |||
| Tomáš Hozza | 2016-05-10 08:16:15 UTC | CC | john | |
| Tomáš Hozza | 2016-05-10 08:16:43 UTC | CC | rgermann | |
| Tomáš Hozza | 2016-05-10 08:20:21 UTC | Status | NEW | ASSIGNED |
| Tomáš Hozza | 2016-05-11 17:58:40 UTC | Keywords | Patch | |
| Tomáš Hozza | 2016-05-11 17:59:08 UTC | Severity | high | medium |
| Jan Ščotka | 2016-05-12 07:53:53 UTC | CC | jscotka | |
| Tomáš Hozza | 2016-05-12 08:28:12 UTC | Doc Text | Previously BIND was not able to react to network configuration changes by itself and shipped NetworkManager dispatcher script for this purpose. The solution didn't work on systems, where NetworkManager was not installed, because the dispatcher script was never run. From latest upstream version we backported the support for getting information about network configuration using standard system API. As a result BIND is now able to react to situations when new IP address is added to an interface or is removed. If the new address is allowed by BIND's configuration, it will automatically start to listen on it. The NetworkManager dispatcher script has been also removed, as it is not needed any more. Not using NetworkManager dispatcher script, which caused full server reload, can result in better performance in case your configuration contains large zone files. | |
| Doc Type | Bug Fix | Release Note | ||
| Tomáš Hozza | 2016-05-12 12:42:51 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | bind-9.9.4-36.el7 | |||
| errata-xmlrpc | 2016-05-12 12:44:45 UTC | Status | MODIFIED | ON_QA |
| Lenka Špačková | 2016-07-14 12:54:30 UTC | Docs Contact | mjahoda | |
| Mirek Jahoda | 2016-07-15 12:33:06 UTC | Doc Text | Previously BIND was not able to react to network configuration changes by itself and shipped NetworkManager dispatcher script for this purpose. The solution didn't work on systems, where NetworkManager was not installed, because the dispatcher script was never run. From latest upstream version we backported the support for getting information about network configuration using standard system API. As a result BIND is now able to react to situations when new IP address is added to an interface or is removed. If the new address is allowed by BIND's configuration, it will automatically start to listen on it. The NetworkManager dispatcher script has been also removed, as it is not needed any more. Not using NetworkManager dispatcher script, which caused full server reload, can result in better performance in case your configuration contains large zone files. | The *named* service now bounds to all interfaces With this update, *BIND* is able to react to situations when a new IP address is added to an interface. If the new address is allowed by the configuration, *BIND* will automatically start to listen on its interface. |
| Mirek Jahoda | 2016-07-15 12:44:03 UTC | Doc Text | The *named* service now bounds to all interfaces With this update, *BIND* is able to react to situations when a new IP address is added to an interface. If the new address is allowed by the configuration, *BIND* will automatically start to listen on its interface. | The *named* service now binds to all interfaces With this update, *BIND* is able to react to situations when a new IP address is added to an interface. If the new address is allowed by the configuration, *BIND* will automatically start to listen on that interface. |
| Petr Sklenar | 2016-08-29 13:49:59 UTC | QA Contact | qe-baseos-daemons | psklenar |
| Blaz Podrzaj | 2016-09-02 10:34:50 UTC | CC | blayo | |
| Petr Sklenar | 2016-09-14 10:38:13 UTC | Status | ON_QA | VERIFIED |
| John Skeoch | 2016-11-01 01:42:14 UTC | CC | rgermann | bkruell |
| errata-xmlrpc | 2016-11-02 15:41:51 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-11-04 01:26:00 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-03 21:26:00 UTC |
Back to bug 1294506