Bug #404
closed
Create "CNAMEs" for LTER metcat and ldap
Added by David Blankman almost 23 years ago.
Updated over 22 years ago.
Description
Create CNAMEs:
suggested names: ldap.lterknb.org or ldap.knblter.org,
metacat.lterknb.org or metacat.knblter.org
ldap.lternet.edu (for new internal ldap
dc=lternet,dc=edu)
David -
I think you are a bit unclear on the concept. We're not creating a new domain
for the ldap server - we are creating an alias within the lter domain. There's
no reason to have another domain to manage for knb.
James
This is a convenience fix that I'll submit this week. These will initially point
to quark - a Sun Ultra 10 that will be the knb server.
Moved issues that we do not intend to address during the current release to the
'Postpone' milestone.
I've created the ip name knb.lternet.edu and have created the following CNAMES
to it for now:
knb-ldap IN CNAME knb.lternet.edu.
ldap IN CNAME knb.lternet.edu.
metacat IN CNAME knb.lternet.edu.
I tried pinging metacat.lternet.edu, knb-ldap.lternet.edu and ldap.lternet.edu and got the
following:
Z:\>ping metacat.lternet.edu
Unknown host
metacat.lternet.edu.
Z:\>ping ldap.lternet.edu
Unknown host
ldap.lternet.edu.
Z:\>ping knb-ldap.lternet.edu
Unknown host knb-ldap.lternet.edu.
Check your name server setting - Space has not been updating DNS properly. It's
on the list.
James
Original Bugzilla ID was 404
Also available in: Atom
PDF