[DBWG] in domain obj, identical nserver: attributes

[Frank Habicht]

On 2/20/2026 1:48 PM, Sylvain BAYA wrote:
> Le 20/02/2026 à 07:34, Frank Habicht a écrit :
>> Hi,
>>
>> On 2/20/2026 3:16 AM, Sylvain BAYA wrote:
>>> Le 19/02/2026 à 14:41, Frank Habicht a écrit :
>>>> should there also be a check that for any new domain object there 
>>>> are not two nserver: attributes pointing to the exact same server name?
>>>>
>>>
>>> No! imho, i see less interest and not existing
>>> documentation to support such a process.
>>>
>>> Maybe you have more context to share, then i
>>> need to figure it out. Do kindly provide more
>>> element, for me to eventually reconsider my
>>> actual PoV (Point of View).
>>>
>>
>> I admit and agree that the current letter-of-the-law does allow
>> >> nserver:        ns1.ibits.xyz
>> >> nserver:        ns1.ibits.xyz
>>
>> but is this really possibly the intend of the originator of this data?
>>
> 
> Hi Frank,
> 
> Good question and my answer is: yes!
> 
> Possible scenario:
> 
> --if the implementation of that class attribute
> is of the kind:
> --multiple means two or more;

https://afrinic.net/support/whois/getting-started
'An attribute that is "multiple" can be used more than once in an object.'
So it's _once_ or more.

I found for instance 198.29.196.in-addr.arpa and its neighbors to have 
only one. (Due to deletion due to lameness)

> --then a user with only one DNS authoritative
> server, at the moment,
> --would be tempted to fill the same data to a
> --secondary *mandatory* attribute.
> --.

I think the reason doesn't apply....

Frank