[ntp:hackers] Re: IPv6 Multicasting
David L. Mills
mills at udel.edu
Thu Jun 30 08:20:08 PDT 2005
You are exactly right. If our local staff is to maintain my Solaris
machines, I need to use the "standard" libraries and configurations. For
that matter, if I am the resource to build/configure the FreeBSD
machines here, I need to use whatever comes out of the standard box.
The NTP sandbox here is a wart on the side of the department in that the
department NIS defines the campus and department environment - users,
groups, host names, netgroups, etc., while the additional users, groups,
etc., for the NTP corps is defined on the pogo NIS maps and exported to
malarky and whimsy. The design is to use NIS from pogo and the
department machines, including pogo, to establish the NTP sandbox via
NIS and when that fails on pogo to revert to DNS. The problem is that
pogo DNS fails for whatever cause. I have no idea what to do about that,
especially since it once worked.
It would seem the root cause here is the interface between NIS and DNS
on pogo. Interestingly enough, dig does resolve pogo-ip6 on pogo, but
not on our department machines, which allegedly have the same
configuration. I am told Sun is to deprecate NIS in favor of LDAP. I am
also told the campus DNS is maintained via a Sybase database system and
providing IPv6 requires considerable investment. Having said that, I am
told the campus guys expect to do what needs when the time comes. I will
try to convince them the time is now.
If there is something we can do on pogo as workaround until a more
generic solution is available, please advise.
Danny Mayer wrote:
> David L. Mills wrote:
>> I am told the nslookup and dig programs have compiled-in DNS
>> interfaces and some other programs like ping use the system library,
>> which may use something different. Machines other than pogo and
>> whimsy normally use NIS to resolve a name. If pogo and whimsy can't
>> resolve a name via NIS then they (only) fall back to DNS. That's as
>> far as I go. I don't know why the default library operates
>> differently than nslookup/dig and I don't know why it once did and
>> now no loger does.
> Dave, nslookup and dig as built from the ISC sources use the standard
> libbind (BIND 8) libraries or BIND 9 libraries for running queries and
> don't use any local resolver code to do the lookups. programs like ping,
> traceroute, etc. almost certainly use the local system resolver code.
> I'd like to recommend that you don't use NIS but there are usually other
> things going on on the machines that would prevent you doing that not to
> mention the support people need standard configurations on all their
> machines otherwise support becomes a nightmare.
> Is there some issue with NTP that needs to be resolved or are you
> dealing with other issues?
More information about the hackers