Re: idmapd Domain issue

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

 



Sorry for the delay.... 

On 8/10/20 10:26 AM, Joakim Tjernlund wrote:
> On Mon, 2020-08-10 at 10:13 -0400, Steve Dickson wrote:
>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>
>>
>> On 8/8/20 6:21 AM, Joakim Tjernlund wrote:
>>> We got an old, non existing, domain configured for idmapd, like so:
>>>   Domain = x.y
>>>
>>> Now I would like to change that to our new domain but I cannot
>>> change all computers using the old domain at the same time.
>>>
>>> Ideally I would like to just add the new domain and then change
>>> clients gradually as time permits.
>>>
>>> Currently idmapd does not seems to support this ?
>> I not sure if that helps... but rpc.idmapd does query DNS
>> looking for the _nfsv4idmapdomain text record...  Add
>>      _nfsv4idmapdomain IN TXT "domainname"
>>  recorded to your DNS
> 
> You mean:
>  1) Add _nfsv4idmapdomain IN TXT "x.y" to DNS
>  2) Rm all Domain = x.y idmapd conf
>  3) Change nfsv4idmapdomain IN TXT "new.com" (do I need to restart idmapd here too?)
Yes, yes and yes... That should work... 

steved.
> ?
> 
>>
>>> Could multiple domains be added ?
>> Patches are always welcome! ;-) But I don't see
>> how the would ever work and its probably break
>> a few specs.
> 
> They didn't consider rename migration when those specs where written :)
> 
>  Jocke
> 
>>
>> steved.
>>>
>>>  Jocke
>>>
>>
> 




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux