[DBWG] in domain obj, identical nserver: attributes
Sylvain BAYA
baya.sylvain at cmnog.cm
Fri Feb 20 10:48:31 UTC 2026
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;
--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.
--.
>
> In my opinion this is very most likely the result of a human mistake
>
Probably; but please see above for another
possible cause!
>
> and it is also a likely cause for following human misunderstanding.
>
> Someone looking at this casually might think there are 2 nservers set.
>
...anycasted ;-)
>
> AfriNIC auth DNS server gives one answer - not 2 identical ones. [1]
>
...then, they seem to be doing a prior check :-/
We really need to better understand how they
manage that class attribute: record & response.
>
> My intention is to see if we can help avoid someone (e.g.
> tnoc at ibits.co) mistakenly understanding the whois data as having
> effectively two auth DNS servers and thus some degree of redundancy.
>
Sure, we should! then, could we include follow-up
support to the existing training+assistance done
already by AfriNIC Capacity Building & HelpDesk?
Getting better your point now, i agree there is
a need to check for improvement.
...then i have a question, to the Staff:
What's the meaning of "mutiple" in considering
your implementation of nserver: attribute of the
domain class?
==> i kindly remind you my off-topic suggestion;
dear cochairs :-)
>
>
>>> If on domain object creation two nserver: attributes have the exact
>>> same content, should creation be rejected (because of most likely
>>> human error) ?
>>>
>>
>> Why? even more here. It's a "no" for me.
>> ...as you shared, that "domain" class attribute
>> description; and i can add (if minimum is 2?):
>>
>> cacty at shalom:~$ TZ='UTC' date --rfc-3339='seconds' && \
>> whois -h whois.afrinic.net -- -t domain | \
>> grep nserver \
>> # from AS15964 at Bhome
>> 2026-02-19 23:59:22+00:00
>> nserver: [mandatory] [multiple] [inverse key]
>> cacty at shalom:~$
>>
>> Is there a persevered problem? please clarify,
>> to allow me to better understand, brother.
>>
> see above.
>
> PS: the auth server is this example is also LAME :-( - [2]
>
...sad too! though it reminds me to do my own
home work; as we have not yet configured any
reverse DNS record :'-( but i know that Nishal
would help us! or Willy! thanks to you guys.
Is the contacts reachable? then following apply:
https://afrinic.net/support/whois/resolve-lame-delegation
and
https://www.afrinic.net/services/lame-delegation
...and this is my next question, to the Staff:
is the cited nserver: attributes content present,
on the raw data, here [*] already?
__
[*]: Lame Delegation | AfriNIC Statistics Portal
<https://stats.afrinic.net/lamerdns/>
Shalom,
--sb.
>
> Regards,
> Frank
>
>
>
> [1]
> $ dig @ns1.afrinic.net. 8.c.4.f.f.0.c.2.ip6.arpa ns +norec
>
> ; <<>> dig 9.10.8-P1 <<>> @ns1.afrinic.net. 8.c.4.f.f.0.c.2.ip6.arpa
> ns +norec
> ; (2 servers found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63543
> ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ;; QUESTION SECTION:
> ;8.c.4.f.f.0.c.2.ip6.arpa. IN NS
>
> ;; AUTHORITY SECTION:
> 8.c.4.f.f.0.c.2.ip6.arpa. 172800 IN NS ns1.ibits.xyz.
>
>
> [2]
> $ dig @ns1.ibits.xyz. 8.c.4.f.f.0.c.2.ip6.arpa soa
> ...
> ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 5581
>
>
> _______________________________________________
> DBWG mailing list
> DBWG at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/dbwg
--
Best Regards !
baya.sylvain [AT cmNOG DOT cm] |
cmNOG's Structure <https://www.cmnog.cm/dokuwiki/Structure> | CAMIX's
Website
<https://web.archive.org/web/20240706030230/http://www.camix.cm/> |
Douala-IX's Looking Glass <https://tools.std.douala-ix.net/lg> |
cmNOG's Surveys <https://survey2.cmnog.cm/> | Subscribe to cmNOG's
Mailing List <https://lists.cmnog.cm/mailman/listinfo/cmnog> |
__
#LASAINTEBIBLE|#Ephésiens5:18,15-21«[...] 18 Et *_ne vous enivrez_* pas
*_de vin_*, en quoi *_il y a de la dissolution_*; mais *_soyez remplis
de l'Esprit_*, [...]»
#LASAINTEBIBLE|#Hébreux13:9,5-15«[...] 9 _*Ne soyez pas seduits par*_
des _*doctrines diverses*_ et _*etrangeres*_, car il est bon _*que le
coeur soit affermi par la grace*_, non par les viandes, lesquels n'ont
pas profite à ceux qui y ont marche. [...]»
#AMEN,#Maranatha,#MerciJÉSUS! #MaPrière est que tu naisses de
nouveau.#Chrétiennement
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/dbwg/attachments/20260220/2a515473/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x0387408365AC8594.asc
Type: application/pgp-keys
Size: 14591 bytes
Desc: OpenPGP public key
URL: <https://lists.afrinic.net/pipermail/dbwg/attachments/20260220/2a515473/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://lists.afrinic.net/pipermail/dbwg/attachments/20260220/2a515473/attachment-0001.sig>
More information about the DBWG
mailing list