Back to bug 1039304

Who When What Removed Added
Kamil Dudka 2013-12-07 21:35:42 UTC CC claudiu.raveica
Flags needinfo?(claudiu.raveica)
Claudiu RAVEICA 2013-12-07 22:13:02 UTC Flags needinfo?(claudiu.raveica)
Kamil Dudka 2013-12-08 09:26:25 UTC CC ashankar, pfrankli, spoyarek
Component curl glibc
Assignee kdudka codonell
QA Contact qe-baseos-security qe-baseos-tools
Carlos O'Donell 2013-12-27 23:19:12 UTC Flags needinfo?(claudiu.raveica)
Claudiu RAVEICA 2014-01-07 17:23:01 UTC Flags needinfo?(claudiu.raveica)
John Skeoch 2015-09-14 00:25:59 UTC CC spoyarek mnewsome
Florian Weimer 2016-02-04 06:24:30 UTC CC fweimer
Michal Hlavinka 2017-01-09 16:36:43 UTC Doc Type Bug Fix If docs needed, set a value
Carlos O'Donell 2017-01-19 14:07:49 UTC Assignee codonell glibc-bugzilla
Carlos O'Donell 2017-09-06 02:31:24 UTC CC codonell
Florian Weimer 2017-11-08 09:48:33 UTC Link ID Sourceware 22409
Summary curl, ping can not resolve hosts like "hostname-.domain.com" glibc: curl, ping can not resolve hosts like "hostname-.example.com"
Red Hat Bugzilla Rules Engine 2017-11-08 09:48:38 UTC Status NEW CLOSED
Resolution --- WONTFIX
Last Closed 2017-11-08 04:48:38 UTC
Florian Weimer 2017-11-08 09:50:03 UTC Status CLOSED NEW
Target Release --- 7.6
Component glibc glibc
Version 6.5 7.0
Resolution WONTFIX ---
Product Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7
Target Milestone rc pre-dev-freeze
Keywords Reopened
Florian Weimer 2017-11-11 11:02:33 UTC Keywords Reopened Patch
Florian Weimer 2018-11-20 09:57:18 UTC Status NEW ASSIGNED
Carlos O'Donell 2018-12-05 05:02:20 UTC Blocks 1655768
Martin Cermak 2018-12-06 16:11:29 UTC CC mcermak
Florian Weimer 2019-02-28 11:16:00 UTC Assignee glibc-bugzilla fweimer
Florian Weimer 2019-03-01 11:15:12 UTC Status ASSIGNED MODIFIED
Fixed In Version glibc-2.17-275.el7
Doc Text Cause: The DNS stub resolver in glibc rejected certain valid host names, such as dash-.example.com, and accepted some invalid names.

Consequence: As a result, some host names on the Internet could not be resolved.

Fix: The DNS name validation functions (including res_hnok) have been adjusted to match user expectations and specifications more closely.

Result: Host names of the form dash-.example.com can now be resolved successfully if they exist in DNS.
Summary glibc: curl, ping can not resolve hosts like "hostname-.example.com" glibc: More precise DNS name checks (accepting dash-.example.com, among other things)
Doc Type If docs needed, set a value Bug Fix
errata-xmlrpc 2019-03-19 18:38:01 UTC Status MODIFIED ON_QA
Sergey Kolosov 2019-03-26 14:16:51 UTC Status ON_QA VERIFIED
CC skolosov
QA Contact qe-baseos-tools skolosov
Vladimír Slávik 2019-05-28 10:22:24 UTC CC vslavik
Docs Contact vslavik
Vladimír Slávik 2019-05-28 11:24:19 UTC Docs Contact vslavik elpereir
Eliane Ramos Pereira 2019-05-28 15:05:29 UTC Doc Text Cause: The DNS stub resolver in glibc rejected certain valid host names, such as dash-.example.com, and accepted some invalid names.

Consequence: As a result, some host names on the Internet could not be resolved.

Fix: The DNS name validation functions (including res_hnok) have been adjusted to match user expectations and specifications more closely.

Result: Host names of the form dash-.example.com can now be resolved successfully if they exist in DNS.
.The DNS stub resolver in glibc rejected certain valid host names

The DNS stub resolver in glibc rejected certain valid host names, such as dash-.example.com, and accepted some invalid names. As a consequence, some host names on the Internet could not be resolved.
To fix that, the DNS name validation functions (including res_hnok) have been adjusted to match user expectations and specifications more closely. As a result, Host names of the form dash-.example.com can now be resolved successfully if they exist in DNS.
Flags needinfo?(fweimer)
Florian Weimer 2019-05-28 15:21:09 UTC Flags needinfo?(fweimer)
Eliane Ramos Pereira 2019-05-28 15:58:09 UTC Doc Text .The DNS stub resolver in glibc rejected certain valid host names

The DNS stub resolver in glibc rejected certain valid host names, such as dash-.example.com, and accepted some invalid names. As a consequence, some host names on the Internet could not be resolved.
To fix that, the DNS name validation functions (including res_hnok) have been adjusted to match user expectations and specifications more closely. As a result, Host names of the form dash-.example.com can now be resolved successfully if they exist in DNS.
.The DNS stub resolver in glibc rejected certain valid host names

The DNS stub resolver in glibc rejected certain valid host names, such as dash-.example.com, and accepted some invalid names. As a consequence, some host names on the Internet could not be resolved.
To fix that, the DNS name validation functions (including res_hnok) have been adjusted to match user expectations and specifications more closely. As a result, host names of the form dash-.example.com can now be resolved successfully if they exist in DNS.
Eliane Ramos Pereira 2019-05-29 08:37:07 UTC Doc Text .The DNS stub resolver in glibc rejected certain valid host names

The DNS stub resolver in glibc rejected certain valid host names, such as dash-.example.com, and accepted some invalid names. As a consequence, some host names on the Internet could not be resolved.
To fix that, the DNS name validation functions (including res_hnok) have been adjusted to match user expectations and specifications more closely. As a result, host names of the form dash-.example.com can now be resolved successfully if they exist in DNS.
.The DNS stub resolver in `glibc` no longer rejects valid host names, such as hostname-.example.com

The DNS stub resolver in `glibc` rejected certain valid host names, such as hostname-.example.com, and accepted some invalid names. As a consequence, some host names on the Internet could not be resolved.
To fix the problem, the DNS name validation functions, such as `res hnok`, have been adjusted to match user expectations and specifications more closely. As a result, host names of the form hostname-.example.com can now be resolved successfully if they exist in DNS.
errata-xmlrpc 2019-08-06 00:29:38 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2019-08-06 12:48:58 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-11-08 09:48:38 UTC 2019-08-06 12:48:58 UTC
errata-xmlrpc 2019-08-06 12:49:28 UTC Link ID Red Hat Product Errata RHSA-2019:2118

Back to bug 1039304