From ba0dc2a08bd47c39880966f682fb1b7430bfb33b Mon Sep 17 00:00:00 2001 From: Ahmed Abdul Ali Date: Tue, 1 Nov 2016 18:31:30 +0500 Subject: [PATCH] section-dns.sgml: fix typo whoes -> whose --- LDP/retired/Ldap-Implementation-HOWTO/section-dns.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LDP/retired/Ldap-Implementation-HOWTO/section-dns.sgml b/LDP/retired/Ldap-Implementation-HOWTO/section-dns.sgml index 626ff566..d3d374b0 100644 --- a/LDP/retired/Ldap-Implementation-HOWTO/section-dns.sgml +++ b/LDP/retired/Ldap-Implementation-HOWTO/section-dns.sgml @@ -14,7 +14,7 @@ hosts: files, dns, ldap Think well about the order in which you specify these! It is advised always to put files as the first entry. Then, if you want ldap to override your local dns server, you have to make sure that the ip of the ldap server can be found in the /etc/hosts file. -If not, you will have a nice recursive lookup going. -- You want to look up a host, it's not in files, so we try to contact the ldap server, whoes ip we don't know, so we try to look it up in files, where we cannot find it, so we try to contact the ldap server -- get the point? You could bypass this problem entirely by referring to your ldap server with an ip number instead of a hostname (in /etc/ldap.conf, that is.) +If not, you will have a nice recursive lookup going. -- You want to look up a host, it's not in files, so we try to contact the ldap server, whose ip we don't know, so we try to look it up in files, where we cannot find it, so we try to contact the ldap server -- get the point? You could bypass this problem entirely by referring to your ldap server with an ip number instead of a hostname (in /etc/ldap.conf, that is.) Schema The schema used for this, and similar services, can be found in RFC 2307. Entries used for mapping names to ipnumbers are in an objectclass ipHost. The name part of the mapping is given ni the attribute cn, while the ip part lives in ipHostNumber.