Bug 68480
| Summary: | lame server resolving ldap.bogusdomain.bog (in 'bog.com'?) | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Nicolas Mailhot <nicolas.mailhot> |
| Component: | nss_ldap | Assignee: | Nalin Dahyabhai <nalin> |
| Status: | CLOSED WORKSFORME | QA Contact: | Aaron Brown <abrown> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-03-11 13:15:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
way too old to be useful |
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020625 Description of problem: I've recently switched a small subnet to nss_ldap + kerberos authentication. The subnet uses a private ip class and a bogus domain bogusdomain.bog. Now the main server logs are flooded with : lame server resolving ldap.bogusdomain.bog in ('bog.com'?) messages as the system somehow decides ldap.bogusdomain.bog = ldap.bogusdomain.bog .com and tries to resolve the .com address with external dns servers. The dns setup should be ok as *all* other bogusdomain.bog adress resolve fine on all the network. In fact taping host ldap.bogusdomain.bog on any computer won't produce a "lame server" message. But nss_ldap use with the same address does Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Setup a subnet with a private bogus domain and try to use nss_ldap Additional info: domain dns, krb & ldap on the same server