<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 20/02/2026 à 13:38, Frank Habicht a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:cfe49a69-f862-4fc4-89d5-1ffd5aefaa67@geier.ne.tz">
<br>
<br>
On 2/20/2026 1:48 PM, Sylvain BAYA wrote:
<br>
<blockquote type="cite">Le 20/02/2026 à 07:34, Frank Habicht a
écrit :
<br>
<blockquote type="cite">Hi,
<br>
<br>
On 2/20/2026 3:16 AM, Sylvain BAYA wrote:
<br>
<blockquote type="cite">Le 19/02/2026 à 14:41, Frank Habicht a
écrit :
<br>
<blockquote type="cite">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?
<br>
<br>
</blockquote>
<br>
No! imho, i see less interest and not existing
<br>
documentation to support such a process.
<br>
<br>
Maybe you have more context to share, then i
<br>
need to figure it out. Do kindly provide more
<br>
element, for me to eventually reconsider my
<br>
actual PoV (Point of View).
<br>
<br>
</blockquote>
<br>
I admit and agree that the current letter-of-the-law does
allow
<br>
>> nserver: ns1.ibits.xyz
<br>
>> nserver: ns1.ibits.xyz
<br>
<br>
but is this really possibly the intend of the originator of
this data?
<br>
<br>
</blockquote>
<br>
Hi Frank,
<br>
<br>
Good question and my answer is: yes!
<br>
<br>
Possible scenario:
<br>
<br>
--if the implementation of that class attribute
<br>
is of the kind:
<br>
--multiple means two or more;
<br>
</blockquote>
<br>
<a class="moz-txt-link-freetext" href="https://afrinic.net/support/whois/getting-started">https://afrinic.net/support/whois/getting-started</a>
<br>
'An attribute that is "multiple" can be used more than once in an
object.'
<br>
So it's _once_ or more. <br>
<br>
</blockquote>
<br>
Hi Frank,<br>
...i went to your email again and it's clearer to <br>
me now: the key word is "*can*". The manual <br>
is saying what you said...i misunderstood it on <br>
the first read :'-( again: my english! i apologize!<br>
<br>
...then, if it's allowed to insert/create only *one* <br>
'nserver:' attribute to a domain object; therefore <br>
it become more difficult to fix the problems <br>
[1,2,3] you are pointing us to.<br>
__<br>
[1]: Having only one 'nserver:' attribute is still <br>
allowed!<br>
[2]: Allowing two same 'nserver:' attributes is <br>
not good, while considering the BCOP which <br>
recommends to have two DNS authoritative <br>
nameservers within two separate ASs ;-).<br>
[3]: It's worse if the two 'nserver:' attributes <br>
whith the same content is a lame delegation.<br>
<br>
_Questions_: <br>
What's the actual intent of the rule? <br>
What should be now the intent of the rule?<br>
<br>
<br>
<blockquote type="cite"
cite="mid:cfe49a69-f862-4fc4-89d5-1ffd5aefaa67@geier.ne.tz"><br>
I found for instance 198.29.196.in-addr.arpa and its neighbors to
have only one. (Due to deletion due to lameness)
<br>
<br>
<blockquote type="cite">--then a user with only one DNS
authoritative
<br>
server, at the moment,
<br>
--would be tempted to fill the same data to a
<br>
--secondary *mandatory* attribute.
<br>
--.
<br>
</blockquote>
<br>
I think the reason doesn't apply.... <br>
<br>
</blockquote>
<br>
Brother, if you are right; then i think the context <br>
is worse imho :'-( <br>
you have two attributes in one and your DNS <br>
authoritative server is lame...<br>
...what's different if you had only one attribute? <br>
:-/ ...i imagine that:<br>
<br>
i1. a Whois domain object with a single <br>
'nserver' attribute is more inclined to <br>
lameness; than with two of such attributes.<br>
i2. a good fix should consider to first start by <br>
disallowing single 'nserver' attribute<br>
i3. a next step could be to implement a diff of <br>
two 'nserver' attributes when a domain object <br>
is created. <br>
i4. after that, it could be useful to make sure <br>
that fixing lameness is at the core of any of the <br>
recommended changes<br>
i5. prior to all these changes, i think we need <br>
a BCOP document on "<i><b>DNS Auth Nameserver <br>
Requirements for 'nserver:' attributes</b></i>".<br>
i6. then a tool like container image to deploy <br>
such Auth nameservers (at least 2 in different <br>
locations).<br>
<br>
Shalom,<br>
--sb.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:cfe49a69-f862-4fc4-89d5-1ffd5aefaa67@geier.ne.tz"><br>
Frank
<br>
<br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<font size="2"><br>
Best Regards !<br>
</font>
<font size="2"><br>
baya.sylvain [AT cmNOG DOT cm] | <br>
<a href="https://www.cmnog.cm/dokuwiki/Structure">cmNOG's
Structure</a> | <a href="https://www.camix.cm/"
moz-do-not-send="true">CAMIX's Website</a> | <a
href="https://tools.std.douala-ix.net/lg">Douala-IX's Looking
Glass</a> | <br>
<a href="https://survey2.cmnog.cm/">cmNOG's Surveys</a> |
Subscribe to <a
href="https://lists.cmnog.cm/mailman/listinfo/cmnog">cmNOG's
Mailing List</a> | <br>
__
<br>
#LASAINTEBIBLE|#Ephé<a class="moz-txt-link-freetext" href="siens5:18,15-21«">siens5:18,15-21«</a>[...] 18 Et <b><u>ne vous
enivrez</u></b> pas <b><u>de vin</u></b>, en quoi <b><u>il
y a de la dissolution</u></b>; mais <b><u>soyez remplis de
l'Esprit</u></b>, [...]» <br>
#LASAINTEBIBLE|#Hé<a class="moz-txt-link-freetext" href="breux13:9,5-15«">breux13:9,5-15«</a>[...] 9 <u><b>Ne soyez pas
seduits par</b></u> des <u><b>doctrines diverses</b></u> et
<u><b>etrangeres</b></u>, car il est bon <u><b>que le coeur
soit affermi par la grace</b></u>, non par les viandes,
lesquels n'ont pas profite à ceux qui y ont marche. [...]»
<br>
#AMEN,#Maranatha,#MerciJÉSUS! #MaPrière est que tu naisses de
nouveau.#Chrétiennement</font><br>
</div>
<br>
</body>
</html>