MrIch
13.11.02, 10:19
Hallo!
Ich versuche zur Zeit diese Softare unter SuSE 8.1 einzurichten:
bind-9.2.1.tar bind-sdb-ldap-0.9.tar, openldap2-2.1.4-26
Doch wenn ich einen nslookup machen kommt folgendes:
tail /var/log/messages:
Nov 13 09:13:15 C130230 slapcat: >>> dnPretty: <cn=Manager,dc=stua-lp,dc=nrw,dc=de>
Nov 13 09:13:15 C130230 slapcat: <<< dnPretty: <cn=Manager,dc=stua-lp,dc=nrw,dc=de>
Nov 13 09:13:15 C130230 slapcat: <= str2entry(relativeDomainName=C130216,dc=stua-lp,dc=nrw,dc=de) -> 0x818ded8
Nov 13 09:13:15 C130230 slapcat: slapcat shutdown: initiated
Nov 13 09:13:15 C130230 slapcat: ldbm backend syncing
Nov 13 09:13:15 C130230 slapcat: ldbm flushing db (id2entry.dbb)
Nov 13 09:13:15 C130230 slapcat: ldbm closing db (id2entry.dbb)
Nov 13 09:13:15 C130230 slapcat: ldbm backend done syncing
Nov 13 09:13:15 C130230 slapcat: ====> cache_release_all
Nov 13 09:13:15 C130230 slapcat: slapcat shutdown: freeing system resources.
C130230:/ # nslookup C130216
Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 10.242.130.230
Address: 10.242.130.230#53
** server can't find C130216: SERVFAIL
So sieht es im ldap aus:
dn: ou=dns,dc=stua-lp,dc=nrw,dc=de
objectClass: organizationalUnit
ou: dns
structuralObjectClass: organizationalUnit
entryUUID: 5b7fd7ba-8a91-1026-8eaa-9e37783de528
creatorsName: cn=Manager,dc=stua-lp,dc=nrw,dc=de
createTimestamp: 20021112134950Z
entryCSN: 2002111213:49:50Z#0x0001#0#0000
modifiersName: cn=Manager,dc=stua-lp,dc=nrw,dc=de
modifyTimestamp: 20021112134950Z
dn: relativeDomainName=C130216,dc=stua-lp,dc=nrw,dc=de
objectClass: dNSZone
relativeDomainName:: QzEzMDIxNiA=
zoneName:: c3R1YS1scC5ucncuZGUg
dNSTTL: 86400
dNSClass: IN
aRecord: 10.242.130.216
structuralObjectClass: dNSZone
entryUUID: 46667e04-8b24-1026-9bc5-e48dc2c0f616
creatorsName: cn=Manager,dc=stua-lp,dc=nrw,dc=de
createTimestamp: 20021113072130Z
entryCSN: 2002111307:21:30Z#0x0001#0#0000
modifiersName: cn=Manager,dc=stua-lp,dc=nrw,dc=de
modifyTimestamp: 20021113072130Z
cat /etc/named.conf
options {
pid-file "named.pid";
listen-on { 10.242.130.230; };
listen-on-v6 { none; };
recursion no;
};
zone "." {
type master;
file "root.db";
};
zone "stua-lp.nrw.de" {
type master;
database "ldap ldap://localhost/dc=stua-lp,dc=nrw,dc=de,o=DNS,dc=stua-lp,dc=nrw,dc=de 172800";
};
Ich weiß nun leider nicht ob es an ldap oder bind liegt...
Hat jemand eine Idee?
Ich versuche zur Zeit diese Softare unter SuSE 8.1 einzurichten:
bind-9.2.1.tar bind-sdb-ldap-0.9.tar, openldap2-2.1.4-26
Doch wenn ich einen nslookup machen kommt folgendes:
tail /var/log/messages:
Nov 13 09:13:15 C130230 slapcat: >>> dnPretty: <cn=Manager,dc=stua-lp,dc=nrw,dc=de>
Nov 13 09:13:15 C130230 slapcat: <<< dnPretty: <cn=Manager,dc=stua-lp,dc=nrw,dc=de>
Nov 13 09:13:15 C130230 slapcat: <= str2entry(relativeDomainName=C130216,dc=stua-lp,dc=nrw,dc=de) -> 0x818ded8
Nov 13 09:13:15 C130230 slapcat: slapcat shutdown: initiated
Nov 13 09:13:15 C130230 slapcat: ldbm backend syncing
Nov 13 09:13:15 C130230 slapcat: ldbm flushing db (id2entry.dbb)
Nov 13 09:13:15 C130230 slapcat: ldbm closing db (id2entry.dbb)
Nov 13 09:13:15 C130230 slapcat: ldbm backend done syncing
Nov 13 09:13:15 C130230 slapcat: ====> cache_release_all
Nov 13 09:13:15 C130230 slapcat: slapcat shutdown: freeing system resources.
C130230:/ # nslookup C130216
Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 10.242.130.230
Address: 10.242.130.230#53
** server can't find C130216: SERVFAIL
So sieht es im ldap aus:
dn: ou=dns,dc=stua-lp,dc=nrw,dc=de
objectClass: organizationalUnit
ou: dns
structuralObjectClass: organizationalUnit
entryUUID: 5b7fd7ba-8a91-1026-8eaa-9e37783de528
creatorsName: cn=Manager,dc=stua-lp,dc=nrw,dc=de
createTimestamp: 20021112134950Z
entryCSN: 2002111213:49:50Z#0x0001#0#0000
modifiersName: cn=Manager,dc=stua-lp,dc=nrw,dc=de
modifyTimestamp: 20021112134950Z
dn: relativeDomainName=C130216,dc=stua-lp,dc=nrw,dc=de
objectClass: dNSZone
relativeDomainName:: QzEzMDIxNiA=
zoneName:: c3R1YS1scC5ucncuZGUg
dNSTTL: 86400
dNSClass: IN
aRecord: 10.242.130.216
structuralObjectClass: dNSZone
entryUUID: 46667e04-8b24-1026-9bc5-e48dc2c0f616
creatorsName: cn=Manager,dc=stua-lp,dc=nrw,dc=de
createTimestamp: 20021113072130Z
entryCSN: 2002111307:21:30Z#0x0001#0#0000
modifiersName: cn=Manager,dc=stua-lp,dc=nrw,dc=de
modifyTimestamp: 20021113072130Z
cat /etc/named.conf
options {
pid-file "named.pid";
listen-on { 10.242.130.230; };
listen-on-v6 { none; };
recursion no;
};
zone "." {
type master;
file "root.db";
};
zone "stua-lp.nrw.de" {
type master;
database "ldap ldap://localhost/dc=stua-lp,dc=nrw,dc=de,o=DNS,dc=stua-lp,dc=nrw,dc=de 172800";
};
Ich weiß nun leider nicht ob es an ldap oder bind liegt...
Hat jemand eine Idee?