Back to bug 1388534
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Christian Heimes | 2016-10-25 15:06:40 UTC | CC | cheimes | |
| Tomáš Hozza | 2016-10-25 16:46:00 UTC | Blocks | 1380362 | |
| Tomáš Hozza | 2016-10-25 16:46:35 UTC | Priority | unspecified | medium |
| Severity | unspecified | medium | ||
| Filip Krska | 2016-11-28 12:31:54 UTC | Blocks | 1298243 | |
| Tomáš Hozza | 2016-11-28 17:21:41 UTC | Blocks | 1393869 | |
| Petr Sklenar | 2016-12-01 08:34:48 UTC | CC | psklenar | |
| autobot-bugzilla | 2016-12-01 14:36:34 UTC | Assignee | thozza | pemensik |
| Tomáš Hozza | 2017-01-04 18:37:15 UTC | Priority | medium | high |
| CC | thozza | |||
| Petr Menšík | 2017-01-19 16:57:08 UTC | Status | NEW | ASSIGNED |
| CC | pemensik | |||
| Doc Text | This change will make URI records incompatible with previous version! It will no longer understand URI records provided by previous versions and will not be able to serve URI records to older clients. But it will be able to cache and receive records from later versions and provide records to them. In other words communicate only in the later format described in rfc7553. | |||
| Doc Type | If docs needed, set a value | Release Note | ||
| Tomáš Hozza | 2017-01-20 11:27:01 UTC | CC | fkrska | |
| Flags | needinfo?(fkrska) | |||
| Filip Krska | 2017-01-20 13:00:16 UTC | CC | jreznik, snagar | |
| Flags | needinfo?(fkrska) | needinfo?(snagar) | ||
| Filip Krska | 2017-01-20 13:14:31 UTC | Flags | needinfo?(jreznik) | |
| Tomáš Hozza | 2017-02-17 14:25:06 UTC | CC | salmy | |
| Flags | needinfo?(snagar) | needinfo?(salmy) | ||
| Petr Menšík | 2017-03-03 13:01:27 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | bind-9.9.4-34.el7 | |||
| Tomáš Hozza | 2017-03-03 13:24:14 UTC | Flags | needinfo?(salmy) needinfo?(jreznik) | |
| errata-xmlrpc | 2017-03-15 20:45:55 UTC | Status | MODIFIED | ON_QA |
| Petr Sklenar | 2017-04-03 10:58:26 UTC | QA Contact | qe-baseos-daemons | psklenar |
| Lenka Špačková | 2017-04-27 18:55:02 UTC | Docs Contact | apetrova | |
| Aneta Šteflová Petrová | 2017-05-15 09:42:58 UTC | Doc Text | This change will make URI records incompatible with previous version! It will no longer understand URI records provided by previous versions and will not be able to serve URI records to older clients. But it will be able to cache and receive records from later versions and provide records to them. In other words communicate only in the later format described in rfc7553. | BIND changes the way it handles URI resource records, impacting also URI backward compatibility Previously, the BIND suite unexpectedly added an additional length byte to a value field when using a URI resource record. With this update, BIND no longer adds the length byte. Note that this update makes new URI records incompatible with records created using BIND in previous versions of Red Hat Enterprise Linux (RHEL). Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL * Serve URI records to clients using previous versions of BIND in RHEL However, BIND in RHEL 7.4 still can: * Cache and receive records from future versions of BIND in RHEL * Provide records to future versions of BIND in RHEL Thanks to this update, BIND in RHEL 7.4 now communicates only in the later format described in RFC 7553. See https://tools.ietf.org/html/rfc7553 for details. |
| Flags | needinfo?(pemensik) | |||
| Aneta Šteflová Petrová | 2017-05-15 09:44:26 UTC | Doc Text | BIND changes the way it handles URI resource records, impacting also URI backward compatibility Previously, the BIND suite unexpectedly added an additional length byte to a value field when using a URI resource record. With this update, BIND no longer adds the length byte. Note that this update makes new URI records incompatible with records created using BIND in previous versions of Red Hat Enterprise Linux (RHEL). Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL * Serve URI records to clients using previous versions of BIND in RHEL However, BIND in RHEL 7.4 still can: * Cache and receive records from future versions of BIND in RHEL * Provide records to future versions of BIND in RHEL Thanks to this update, BIND in RHEL 7.4 now communicates only in the later format described in RFC 7553. See https://tools.ietf.org/html/rfc7553 for details. | BIND changes the way it handles URI resource records, impacting also URI backward compatibility Previously, the BIND suite unexpectedly added an additional length byte to a value field when using a URI resource record. With this update, BIND no longer adds the length byte. This also means that BIND in Red Hat Enterprise Linux (RHEL) 7.4 communicates only in the later format described in RFC 7553. See https://tools.ietf.org/html/rfc7553 for details. Note that this update makes new URI records incompatible with records created using BIND in previous versions of RHEL. Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL * Serve URI records to clients using previous versions of BIND in RHEL However, BIND in RHEL 7.4 still can: * Cache and receive records from future versions of BIND in RHEL * Provide records to future versions of BIND in RHEL |
| Petr Menšík | 2017-05-15 18:45:41 UTC | Flags | needinfo?(pemensik) | |
| Aneta Šteflová Petrová | 2017-05-16 08:44:36 UTC | Doc Text | BIND changes the way it handles URI resource records, impacting also URI backward compatibility Previously, the BIND suite unexpectedly added an additional length byte to a value field when using a URI resource record. With this update, BIND no longer adds the length byte. This also means that BIND in Red Hat Enterprise Linux (RHEL) 7.4 communicates only in the later format described in RFC 7553. See https://tools.ietf.org/html/rfc7553 for details. Note that this update makes new URI records incompatible with records created using BIND in previous versions of RHEL. Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL * Serve URI records to clients using previous versions of BIND in RHEL However, BIND in RHEL 7.4 still can: * Cache and receive records from future versions of BIND in RHEL * Provide records to future versions of BIND in RHEL | BIND changes the way it handles URI resource records, impacting also URI backward compatibility Previously, the BIND suite unexpectedly added an additional length byte to a value field when using a URI resource record. With this update, BIND no longer adds the length byte. This also means that BIND in Red Hat Enterprise Linux (RHEL) 7.4 communicates only in the later format described in RFC 7553. See https://tools.ietf.org/html/rfc7553 for details. Note that this update makes new URI records incompatible with records created using BIND in previous versions of RHEL. Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL * Serve URI records to clients using previous versions of BIND in RHEL However, BIND in RHEL 7.4 still can: * Cache and receive records from both earlier and future versions of BIND in RHEL * Serve records in the old URI format encoded as Unknown DNS Resource Record (see RFC 3597 for details) After this update, you do not need to make any change to the DNS zone files. |
| Flags | needinfo?(pemensik) | |||
| Aneta Šteflová Petrová | 2017-05-16 08:45:45 UTC | Doc Type | Release Note | Enhancement |
| Petr Menšík | 2017-05-16 10:06:33 UTC | Flags | needinfo?(pemensik) | |
| Aneta Šteflová Petrová | 2017-05-16 10:17:03 UTC | Doc Text | BIND changes the way it handles URI resource records, impacting also URI backward compatibility Previously, the BIND suite unexpectedly added an additional length byte to a value field when using a URI resource record. With this update, BIND no longer adds the length byte. This also means that BIND in Red Hat Enterprise Linux (RHEL) 7.4 communicates only in the later format described in RFC 7553. See https://tools.ietf.org/html/rfc7553 for details. Note that this update makes new URI records incompatible with records created using BIND in previous versions of RHEL. Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL * Serve URI records to clients using previous versions of BIND in RHEL However, BIND in RHEL 7.4 still can: * Cache and receive records from both earlier and future versions of BIND in RHEL * Serve records in the old URI format encoded as Unknown DNS Resource Record (see RFC 3597 for details) After this update, you do not need to make any change to the DNS zone files. | BIND changes the way it handles URI resource records, impacting also URI backward compatibility Previously, the BIND suite added an additional length byte to a value field when using a URI resource record. With this update, BIND no longer adds the length byte. This also means that BIND in Red Hat Enterprise Linux (RHEL) 7.4 communicates only in the later format described in RFC 7553. See https://tools.ietf.org/html/rfc7553 for details. Note that this update makes new URI records incompatible with records created using BIND in previous versions of RHEL. Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL * Serve URI records to clients using previous versions of BIND in RHEL However, BIND in RHEL 7.4 still can: * Cache and receive records from both earlier and future versions of BIND in RHEL * Serve records in the old URI format encoded as Unknown DNS Resource Record (see RFC 3597 for details) After this update, you do not need to make any change to the DNS zone files. |
| Aneta Šteflová Petrová | 2017-05-16 12:48:40 UTC | Doc Text | BIND changes the way it handles URI resource records, impacting also URI backward compatibility Previously, the BIND suite added an additional length byte to a value field when using a URI resource record. With this update, BIND no longer adds the length byte. This also means that BIND in Red Hat Enterprise Linux (RHEL) 7.4 communicates only in the later format described in RFC 7553. See https://tools.ietf.org/html/rfc7553 for details. Note that this update makes new URI records incompatible with records created using BIND in previous versions of RHEL. Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL * Serve URI records to clients using previous versions of BIND in RHEL However, BIND in RHEL 7.4 still can: * Cache and receive records from both earlier and future versions of BIND in RHEL * Serve records in the old URI format encoded as Unknown DNS Resource Record (see RFC 3597 for details) After this update, you do not need to make any change to the DNS zone files. | BIND changes the way it handles URI resource records, impacting also URI backward compatibility With this update, the BIND suite no longer adds an additional length byte to a value field when using a URI resource record. This also means that BIND in Red Hat Enterprise Linux (RHEL) 7.4 communicates only in the format described in RFC 7553: https://tools.ietf.org/html/rfc7553. Note that this update makes new URI records incompatible with records created using BIND in previous versions of RHEL. Namely, BIND in RHEL 7.4 cannot: * Understand URI records provided by previous versions of BIND in RHEL. * Serve URI records to clients using previous versions of BIND in RHEL. However, BIND in RHEL 7.4 still can: * Cache and receive records from both earlier and future versions of BIND in RHEL. * Serve records in the old URI format encoded as Unknown DNS Resource Record. See RFC 3597 for details: https://tools.ietf.org/html/rfc3597. After this update, you do not need to make any change to the DNS zone files. |
| Petr Sklenar | 2017-06-20 12:40:57 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2017-08-01 20:40:58 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-08-01 16:40:58 UTC |
Back to bug 1388534