Resolver Config

[Nitin Bhagnari]

Hi,

"Why not just 
populate the new 
domain with all of the information from the old
domain, and 
set the 
default domain within the resolver configs to be the
new 
domain?"

We have done exactly that. In fact thats the way the
config has been since the last 3 months. I just
thought search list would be a better way to go about
doing this.

Thanks,

Nitin

--- Kevin Darcy <kcd at daimlerchrysler.com> wrote:

> Are you asking only about syntactical correctness?
> It should be fairly 
> easy to test this configuration to see if it is
> syntactically correct or 
> not. Offhand, it looks OK to me.
> 
> Or, are you asking whether it's a good plan or not?
> In my opinion, 
> searchlists are wasteful abominations. Why not just
> populate the new 
> domain with all of the information from the old
> domain, and set the 
> default domain within the resolver configs to be the
> new domain? This 
> should be transparent both to clients which are
> using shortnames to 
> access resources, and also to clients that are using
> FQDNs, and in fact, 
> will more clearly highlight the clients which are
> accessing resources 
> using the old FQDNs so that you can follow up with
> them and get them to 
> switch over. The downside, of course, is that if you
> have clients using 
> both the old and new names for a particular
> name/record, and you need to 
> do regular maintenance on it, you have to change the
> name/record in two 
> different places. But that just gives one an added
> incentive to get 
> those clients moved over completely!
> 
>                                                     
>                     
>                                                     
>  - Kevin
> 
> 
> Nitin Bhagnari wrote:
> 
> >Hi
> >
> >Just wanted to verify if the following resolver
> config
> >is correct:
> >
> >We were initially using a single domain name which
> is
> >now to be replaced with a new one. For backward
> >compatibility, we want to keep both the domains
> >configured on our resolvers. Here is what we plan
> to
> >do:
> >
> >---------------------------------
> >new domain: abc.xyz.com
> >old domain: ab.xyz.com
> >
> >---------------------------------
> >---------------------------------
> >more /etc/resolv.conf
> >search abc.xyz.com. ab.xyz.com.
> >nameserver 172.16.4.2
> >
> >---------------------------------
> >
> >Can some one confirm that this is correct.
> >  
> >
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com