<!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 19/02/2026 à 14:41, Frank Habicht a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:def33990-76d2-404e-8911-c3b0fec746b5@geier.ne.tz">Dear
AfriNIC staff,
<br>
<br>
<hat=off>
<br>
when adding domain objects, certain checks are done, right?
<br>
<br>
Maybe you could share or point to a resource which these are. <br>
<br>
</blockquote>
<br>
Dear Frank,<br>
Thanks for keeping the WG active, brother!<br>
<br>
<off_topic><br>
Cochairs, can we start quickly fifteen minutes <br>
weekly meeting? <br>
<br>
--we gather and we ask if there is a topic, <br>
--if not, fine! then we end the meeting and <br>
--come back the next week.<br>
--cochairs can recall the topics they need <br>
feedback/reaction/contribution on<br>
--staff can share on their implementation's <br>
challenges and ask for help/feedback<br>
--agenda can be drafted beforehand <br>
--focus can be defined on a couple of topics<br>
--this is a personal brainstorming.<br>
</off_topic><br>
<br>
<blockquote type="cite"
cite="mid:def33990-76d2-404e-8911-c3b0fec746b5@geier.ne.tz"><br>
All:
<br>
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 type="cite"
cite="mid:def33990-76d2-404e-8911-c3b0fec746b5@geier.ne.tz"><br>
If on domain object creation two nserver: attributes have the
exact same content, should creation be rejected (because of most
likely human error) ? <br>
<br>
</blockquote>
<br>
Why? even more here. It's a "no" for me. <br>
...as you shared, that "domain" class attribute <br>
description; and i can add (if minimum is 2?):<br>
<br>
cacty@<a class="moz-txt-link-freetext" href="shalom:~$">shalom:~$</a> TZ='UTC' date --rfc-3339='seconds' && \<br>
whois -h whois.afrinic.net -- -t domain | \<br>
grep nserver \<br>
# from AS15964 at Bhome<br>
2026-02-19 23:59:22+00:00<br>
nserver: [mandatory] [multiple] [inverse key]<br>
cacty@<a class="moz-txt-link-freetext" href="shalom:~$">shalom:~$</a> <br>
<br>
Is there a persevered problem? please clarify, <br>
to allow me to better understand, brother.<br>
<br>
Thanks again.<br>
Remain blessed; with all yours!<br>
<br>
Shalom,<br>
--sb. <br>
<br>
<blockquote type="cite"
cite="mid:def33990-76d2-404e-8911-c3b0fec746b5@geier.ne.tz"><br>
Thanks,
<br>
Frank
<br>
not as chair
<br>
<br>
<br>
this new object triggered my question:
<br>
<br>
$ whoisaf -- -B -r 8.c.4.f.f.0.c.2.ip6.arpa
<br>
[Querying whois.afrinic.net]
<br>
[whois.afrinic.net]
<br>
% This is the AfriNIC Whois server.
<br>
% The AFRINIC whois database is subject to the following terms of
Use. See <a class="moz-txt-link-freetext" href="https://afrinic.net/whois/terms">https://afrinic.net/whois/terms</a>
<br>
<br>
% Information related to '8.c.4.f.f.0.c.2.ip6.arpa'
<br>
<br>
domain: 8.c.4.f.f.0.c.2.ip6.arpa
<br>
descr: Reverse DNS
<br>
nserver: ns1.ibits.xyz
<br>
nserver: ns1.ibits.xyz
<br>
org: ORG-IIL1-AFRINIC
<br>
admin-c: WJM1-AFRINIC
<br>
tech-c: WJM1-AFRINIC
<br>
zone-c: WJM1-AFRINIC
<br>
mnt-by: IBITS-MNT
<br>
mnt-lower: IBITS-MNT
<br>
changed: <a class="moz-txt-link-abbreviated" href="mailto:tnoc@ibits.co">tnoc@ibits.co</a> 20260218
<br>
source: AFRINIC
<br>
<br>
<br>
<br>
available documentation:
<br>
<br>
$ whoisaf -- -v domain | grep -A 14 '^nserver$'
<br>
nserver
<br>
<br>
Specifies the nameservers of the domain.
<br>
<br>
Nameserver name as specified in RFC 1034 with or without
<br>
trailing dot ("."). The total length should not exceed
<br>
254 characters (octets).
<br>
<br>
The nameserver name may be optionally followed by IPv4
address
<br>
in decimal dotted quad form (e.g. 192.0.2.1) or IPv6 address
<br>
in lowercase canonical form (Section 2.2.1, RFC 4291).
<br>
<br>
The nameserver name may be followed by an IP address only
when
<br>
the name is inside of the domain being delegated.
<br>
<br>
$
<br>
<br>
_______________________________________________
<br>
DBWG mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:DBWG@afrinic.net">DBWG@afrinic.net</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo/dbwg">https://lists.afrinic.net/mailman/listinfo/dbwg</a>
<br>
</blockquote>
<br>
<div class="moz-signature">-- <font size="2"><br>
<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://web.archive.org/web/20240706030230/http://www.camix.cm/">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>