help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dealing with multiple domains


From: Mark . Burgess
Subject: Re: dealing with multiple domains
Date: Tue, 11 Feb 2003 05:34:16 +0100 (MET)

>   oh, i agree with you.  since the DNS is independent of any
> host or group of hosts, the only really robust way of determining
> a machine's domain (if a machine can be said to have one) is to
> look up the PTR record for the host's IP address.  and that only
> tells you the authoritative DNS answer, which might be independent
> of what the host itself thinks (from resolv.conf, /etc/hosts, the
> hostname itself) and doesn't take into account other A records or
> CNAME records....  for luke's purposes, though if he knows what is
> in all of his resolv.conf files this should suffice.
>   other than the fact that the domain seems to be required for remote
> copies in cfengine 2, i've never found the domain useful.  at the
> customer site where i use cfengine heavily (1.6.x), we had control of
> multiple DNS domains and wanted to order the search path specifically
> for each host dependend upon physical location (which didn't correspond
> to the various domains), so i always used editfile: to maintain
> /etc/resolv.conf anyway.

This is an odd discussion. It's a chick-egg scenario. New hosts
have no /etc/resolv.conf so cfengine usually sets them based on the
definition of domain, so it certainly makes no sense to set the
domain based on what /etc/resolv.conf contains.

Why not just do this?

classes:

 subdom1 = ( 128_39_89 128_39_74 128_39_75 )                   # 128.39.89.0/24 
|| 128.39.74.0/23

 subdom2 = ( 128_39_73_1 128_39_73_2 128_39_73_3 128_39_73_4 ) # 128.39.73.0/4

control:


 subdom1::

   domain = ( domain1 )

 subdom2::

   domain = ( domain2 )



Mark

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~






reply via email to

[Prev in Thread] Current Thread [Next in Thread]