# WHOIS command on DOMAIN.TV -\> No match for domain?

**URL:** <https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373>\
**Category:** Pause Café\
**Tags:** dns\
**Created:** [Juin 19, 2023, 2:14 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373 "2023-06-19T14:14:33Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon36725218](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/8e8cbc/32.png) [@anon36725218](https://www.debian-fr.org/u/anon36725218)\
**Post date:** [Juin 19, 2023, 2:14 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373/1 "2023-06-19T14:14:33Z")

</div>

Bonjour,

J’ai un problème sur mon nom de domaine [zw3b.tv](http://zw3b.tv) et (d’autres dirais-je).

**Dans WHOIS TOUT les domaines .TV ne sont pas résolvés.**

WHOIS :

```
# whois zw3b.tv
No match for domain "ZW3B.TV".
>>> Last update of WHOIS database: 2023-06-19T14:02:30Z <<<

# whois clique.tv
No match for domain "CLIQUE.TV".
>>> Last update of WHOIS database: 2023-06-19T14:03:00Z <<<

# whois apresdemain.tv
No match for domain "APRESDEMAIN.TV".
>>> Last update of WHOIS database: 2023-06-19T14:03:29Z <<<

```

* * *

Pour infos complémentaire RDAP :

- [OpenRDAP → ZW3B.TV](https://www.openrdap.org/demo?cmd=rdap+-v+zw3b.tv) : Inactive
- [OpenRDAP → APRESDEMAIN.TV](https://www.openrdap.org/demo?cmd=rdap+-v+apresdemain.tv)
- [OpenRDAP → CLIQUE.TV](https://www.openrdap.org/demo?cmd=rdap+-v+clique.tv)

DNSViz :

- [DNSViz → zw3b.tv](https://dnsviz.net/d/zw3b.tv/dnssec) DOMAIN INVISIBLE
- [DNSViz → apresdemain.tv](https://dnsviz.net/d/apresdemain.tv) DNSSEC Okay
- [DNSViz → clique.tv](https://dnsviz.net/d/clique.tv/dnssec) NO DNSSEC

Sinon DIG :

```
root@lv1.dns:~ # dig SOA zw3b.tv @1.1.1.1

; <<>> DiG 9.11.5-P4-5.1+deb10u8-Debian <<>> SOA zw3b.tv @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50871
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;zw3b.tv. IN SOA

;; AUTHORITY SECTION:
tv. 0 IN SOA a.nic.tv. admin.tldns.godaddy. 1687182145 1800 300 604800 1800

;; Query time: 27 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: lun. juin 19 15:45:26 CEST 2023
;; MSG SIZE rcvd: 97

```

…

```
15:45:26 root@lv1.dns:~ # dig SOA zw3b.tv @dns.google

; <<>> DiG 9.11.5-P4-5.1+deb10u8-Debian <<>> SOA zw3b.tv @dns.google
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24851
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;zw3b.tv. IN SOA

;; AUTHORITY SECTION:
tv. 0 IN SOA a.nic.tv. admin.tldns.godaddy. 1687182145 1800 300 604800 1800

;; Query time: 19 msec
;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
;; WHEN: lun. juin 19 15:45:33 CEST 2023
;; MSG SIZE rcvd: 97

```

Et en local sur un serveur «&nbsp;AA&nbsp;» autoritaire → flags: qr **aa** rd ra;

```
root@lv1.dns:~ # dig SOA zw3b.tv @::1

; <<>> DiG 9.11.5-P4-5.1+deb10u8-Debian <<>> SOA zw3b.tv @::1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47817
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 5

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 05138f355906fa4b6bbfaab864905c099e8888357ead0578 (good)
;; QUESTION SECTION:
;zw3b.tv. IN SOA

;; ANSWER SECTION:
zw3b.tv. 3600 IN SOA dns.lab3w.fr. hostmaster.lab3w.fr. 2022111928 300 60 420 60

;; AUTHORITY SECTION:
zw3b.tv. 3600 IN NS dns.ipv10.net.

;; ADDITIONAL SECTION:
dns.ipv10.net. 3600 IN AAAA 2607:5300:60:9389:15:1:a:1000
dns.ipv10.net. 3600 IN AAAA 2001:41d0:701:1100::6530
dns.ipv10.net. 3600 IN A 135.125.133.51
dns.ipv10.net. 3600 IN A 158.69.126.137

;; Query time: 0 msec
;; SERVER: ::1#53(::1)
;; WHEN: lun. juin 19 15:45:45 CEST 2023
;; MSG SIZE rcvd: 238

```

Ou encore sur un autre serveur/adresse IP (non local) autoritaire de [zw3b.tv](http://zw3b.tv) :

```
root@lv1.dns:~ # dig SOA zw3b.tv @2001:41d0:701:1100::6530

; <<>> DiG 9.11.5-P4-5.1+deb10u8-Debian <<>> SOA zw3b.tv @2001:41d0:701:1100::6530
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18745
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 3883640540ff6fe20100000064905e54b906cd51e3e65822 (good)
;; QUESTION SECTION:
;zw3b.tv. IN SOA

;; ANSWER SECTION:
zw3b.tv. 3600 IN SOA dns.lab3w.fr. hostmaster.lab3w.fr. 2022111928 300 60 420 60

;; Query time: 93 msec
;; SERVER: 2001:41d0:701:1100::6530#53(2001:41d0:701:1100::6530)
;; WHEN: lun. juin 19 15:55:32 CEST 2023
;; MSG SIZE rcvd: 123

```

J’ai un algorithme de cryptographie (version 13) ECDSA/SHA-256 / [DNSSEC](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions) sur mon domaine [IPv10.net](http://IPv10.net) (le Name Serveur [dns.ipv10.net](http://dns.ipv10.net)) mais bon.

Çà fonctionnait jusqu’à hier ou avant-hier.

Par contre la commande WHOIS déconne me semble-t’il ?  
Et pourquoi, mon nom de domaine .TV me retourne un status inactive (même sur RDAP ou DNSViz) ?

J’ai envoyé un mail à mon support d’enregistreur de domaine [Gandi.net](http://Gandi.net).

* * *

J’ajoute la réponse au «&nbsp;trace&nbsp;» :

```
root@lv1.dns:~ # dig SOA zw3b.tv @dns.google +trace

; <<>> DiG 9.11.5-P4-5.1+deb10u8-Debian <<>> SOA zw3b.tv @dns.google +trace
;; global options: +cmd
. 86836 IN NS m.root-servers.net.
. 86836 IN NS i.root-servers.net.
. 86836 IN NS j.root-servers.net.
. 86836 IN NS a.root-servers.net.
. 86836 IN NS b.root-servers.net.
. 86836 IN NS d.root-servers.net.
. 86836 IN NS k.root-servers.net.
. 86836 IN NS e.root-servers.net.
. 86836 IN NS f.root-servers.net.
. 86836 IN NS h.root-servers.net.
. 86836 IN NS l.root-servers.net.
. 86836 IN NS c.root-servers.net.
. 86836 IN NS g.root-servers.net.
. 86836 IN RRSIG NS 8 0 518400 20230702050000 20230619040000 60955 . IOrMJyWt1wpil4GpaDbUKrqIPJDFJ3+y765jZ/wwm6/h42Ifl7jE8NhO l9CUx7zl/4tZKq8IxmN5XpZ0LQAijUXNbnAJzKrP7b/qGxn4arfEQ84x 1KTLqKWibEn5gPO5uF2PeBG0uVvdXIUNOJxXEThLWyZ0Re3vtmWHoWKU ilp2i1JffdRzkwq64kYIYHjOJOmxiNus9ORVlPVnv5F/rCU5/TMo48/o w+10No9jnzoXImt6L6ZuduTSqlpbzxacECNQvzc7nlIPXoRboLYQ+q/D w3ojoF3smcGcrODK0FuPlCkFit0Hr14sseZdBRzVXm0xF8ED/WGEUv93 o33KJA==
;; Received 525 bytes from 2001:4860:4860::8888#53(dns.google) in 1 ms

tv. 172800 IN NS a.nic.tv.
tv. 172800 IN NS b.nic.tv.
tv. 172800 IN NS c.nic.tv.
tv. 172800 IN NS d.nic.tv.
tv. 86400 IN DS 2107 8 2 2F2DC481C07E7DB2E54A546A7A35CC16CBCF242EC76B71385A42CD7B C37E7FC8
tv. 86400 IN RRSIG DS 8 1 86400 20230702050000 20230619040000 60955 . ieS6Cz7QOOJtZV0l+wGS7UfPrSNqr70f4OXTnGaZ8c2HzLmTKmwZ2sif X5AINVixmdjKrQt4Y0p7O2JdyoSj0kuSyRDkq+uTo8AQ9OYaXX91Tgav /o+hgQvrwYjoEP2KfNdVr27O/LYM5vKGpw3bQLjIOZ71AxmXV1fw0tQX bFy/q/CVibNFpbSAH9aJP2LPZYmoHondljFWT14l7oVh3rE62tcy/P08 a9lqyS8M+nRCKfpgN6yttWba7qPxMmjPwNO/IgI2jsQZA1gHsyYShkaH taL+/oZxNzUk94ure+S0e4ibDWc2DHIcFcu3jVCxRsMKA3C8rBHXVOdV LGKpvg==
;; Received 615 bytes from 192.203.230.10#53(e.root-servers.net) in 2 ms

tv. 0 IN SOA a.nic.tv. admin.tldns.godaddy. 1687184814 1800 300 604800 1800
tv. 0 IN RRSIG SOA 8 1 900 20230719142655 20230619132655 53769 tv. 5Ch6JUq8NINd80HKgUG3AugU9k3K/SD8qRIpCCCiU78d3llZPM9dKsYq 1qX3a1Sz4ZGLhvYAc5nimci4g0aastk/B0eWHol/9x0zXUumZ/icur+r /ZMLtz6LvnPAWmA0ndkbjJAx13q33OXq2hlAVt8IvQxIsAn9KFT9thMO idQesszo1u2ZRY6ZEIwdK1uwwZIUwCc3X7D1iEdSNUXS+Q==
e7q4euc85b62pb5ajfj5j1acugc1et4q.tv. 900 IN NSEC3 1 1 0 - E82QTN8CDGTCVRGO2NPET7KN70V9NDVJ NS SOA RRSIG DNSKEY NSEC3PARAM CDS CDNSKEY TYPE65534
e7q4euc85b62pb5ajfj5j1acugc1et4q.tv. 900 IN RRSIG NSEC3 8 2 900 20230713051158 20230613042623 53769 tv. zb5suXgdRvhLuF5A6FD+tEJ/kW0nezh8DJ6xzIl4B3OZG0GLQ8LWHbSE zsIo1L40wAnuyB5all6Lg/MNyrkh361mk43MjkIjPui+d2Jz+v2nNS4I ESq/5ZqABugRRomtP6pe2ezsGjlAPOB+h5VEuz7SotyxJgSqWAYW290A ktZsmkehfocohSa5/0X7Ld4elpG+2dj4+hb9mUOevjs5TQ==
bnvf0lo0ou2fvaee6qjpcus7o0gm2v5c.tv. 900 IN NSEC3 1 1 0 - BO45UKRE7P65711TO9SCNS92FRIOVL16 NS DS RRSIG
bnvf0lo0ou2fvaee6qjpcus7o0gm2v5c.tv. 900 IN RRSIG NSEC3 8 2 900 20230715141850 20230618153151 53769 tv. MnyCac73kKo/d00uL/x+nGFMcJuRN6mT0stXkcrdnIg2wG4Og+LjVKtz ExxJzyaLIPUdMNX2TzenskfEtX1d95AswWMZg4DRWxHVHTK9kxwxxQMe kIQhFYj6hlEMPv1rKg/OLONJWUtpcnPKSnDVlDlFZCj0cxb5jcSvlf+Q VNev7NMUtTRJlVBLSsKr4c11Josy6flLv36ZKkJBUVCuYQ==
en5cgpcksfuuifrtnh9rtprrn6mhcn60.tv. 900 IN NSEC3 1 1 0 - ENC1LGJRLESNEDENRH7SLBKIV5FP8O66 NS DS RRSIG
en5cgpcksfuuifrtnh9rtprrn6mhcn60.tv. 900 IN RRSIG NSEC3 8 2 900 20230715234628 20230615231005 53769 tv. Z0XHuN25HQh7iYgZg1LC4Y8XZ3FCDzmakWet9KMHPLYf7R7PWljl48+H UN42Rd0jg2oJMnhesDQKzLWOXxxBObXv8xU3xdAP2qG1RCzzdrTTFnQM 9LOnYqwc4w7Nkf053uMWbmhASpytmu9Z4VOmfTCzo1mK5Z40QYCDKTKJ kw7TRd9e7RNHKI/0a70inMdC5wavrRznoAkBtr/0HPyyhg==
;; Received 1148 bytes from 2001:dcd:2::6#53(b.nic.tv) in 44 ms

```

Il y a une ligne «&nbsp;bizarre&nbsp;» – Je sais pas ce qui fait là celui-ci **admin.tldns.godaddy.** rien à faire là →

```
tv. 0 IN SOA a.nic.tv. admin.tldns.godaddy. 1687184814 1800 300 604800 1800`

```

🤨

Romain

---

<div class="post-metadata">

**Author:** ![Clochette](https://www.debian-fr.org/user_avatar/www.debian-fr.org/clochette/32/8757_2.png) [@Clochette](https://www.debian-fr.org/u/Clochette)\
**Post date:** [Juin 19, 2023, 2:59 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373/2 "2023-06-19T14:59:23Z")

</div>

regarde ce que t’a fais comme modif côté registrar car ton serveur de nom (si il est autoritaire à la bonne ip :

```auto
 ab  ~  dig -t A zw3b.tv @dns.lab3w.fr

; <<>> DiG 9.16.1-Ubuntu <<>> -t A zw3b.tv @dns.lab3w.fr
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41307
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 5

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 2e9b8bd97bb82d72a2b84ec864906cab54a70e410ce6eebc (good)
;; QUESTION SECTION:
;zw3b.tv. IN	A

;; ANSWER SECTION:
zw3b.tv. 3600	IN	A	158.69.126.137

;; AUTHORITY SECTION:
zw3b.tv. 3600	IN	NS	dns.ipv10.net.

;; ADDITIONAL SECTION:
dns.ipv10.net. 3600	IN	AAAA	2001:41d0:701:1100::6530
dns.ipv10.net. 3600	IN	AAAA	2607:5300:60:9389:15:1:a:1000
dns.ipv10.net. 3600	IN	A	135.125.133.51
dns.ipv10.net. 3600	IN	A	158.69.126.137

;; Query time: 87 msec
;; SERVER: 2607:5300:60:9389:15:1:a:1000#53(2607:5300:60:9389:15:1:a:1000)
;; WHEN: lun. juin 19 16:56:43 CEST 2023
;; MSG SIZE rcvd: 195

```

par contre en intérogeant google par exemple :

```auto
 ab  ~  dig -t A zw3b.tv @8.8.8.8

; <<>> DiG 9.16.1-Ubuntu <<>> -t A zw3b.tv @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24285
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;zw3b.tv. IN	A

;; AUTHORITY SECTION:
tv. 900	IN	SOA	a.nic.tv. admin.tldns.godaddy. 1687186477 1800 300 604800 1800

;; Query time: 19 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: lun. juin 19 16:57:46 CEST 2023
;; MSG SIZE rcvd: 97

```

---

<div class="post-metadata">

**Author:** ![anon36725218](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/8e8cbc/32.png) [@anon36725218](https://www.debian-fr.org/u/anon36725218)\
**Post date:** [Juin 19, 2023, 3:01 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373/3 "2023-06-19T15:01:51Z")

</div>

Merci @Clochette monsieur, je vérifie cela [SUJET RESOLU]

Tout à l’heure :

```
root@lv1.dns:~ # dig NS zw3b.tv @dns.google +short
dns.ipv10.net.

```

Après les conseils de @Clochette (j’ai remis un NS à la zone et au whois - pourtant qui pointe sur les «&nbsp;mêmes&nbsp;» IP) :

```
root@lv1.dns:~ # dig NS zw3b.tv @dns.google +short
dns.ipv10.net.
dns.lab3w.fr.

```

Pour la commande Linux WHOIS sur .TV qui retourne «&nbsp;No match for domain&nbsp;»

Sinon sur le Web :

- [Whois zw3b.tv](https://www.whois.com/whois/zw3b.tv)
- [Whois clique.tv](https://www.whois.com/whois/clique.tv)
- [Whois apresdemain.tv](https://www.whois.com/whois/apresdemain.tv)

Bizarre 😕

* * *

Parfait merci encore une fois @Clochette 💖 😍 😍 😍

```auto
root@lv1.dns:~ # dig A zw3b.tv @dns.google
; <<>> DiG 9.11.5-P4-5.1+deb10u8-Debian <<>> A zw3b.tv @dns.google
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12703
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
 ;zw3b.tv. IN A

;; ANSWER SECTION:
zw3b.tv. 3600 IN A 158.69.126.137

;; Query time: 35 msec
;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
;; WHEN: lun. juin 19 17:07:32 CEST 2023
 ;; MSG SIZE rcvd: 52

```

J’ai flippé en voyant que tous les domaines .TV me répondaient → «&nbsp;No match for domain&nbsp;» depuis ma console/commande Linux.

Bonne fin de journée.

---

<div class="post-metadata">

**Author:** ![anon36725218](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/8e8cbc/32.png) [@anon36725218](https://www.debian-fr.org/u/anon36725218)\
**Post date:** [Juin 19, 2023, 3:19 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373/4 "2023-06-19T15:19:05Z")

</div>

Mais est-ce lié à ce que le domaine/zone [IPv10.net](http://IPv10.net) est en algorithme 13 et que [lab3w.fr](http://lab3w.fr) est en algo 8 ?

Cryptographie [DNSSEC](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions) :

- RSA/SHA-256 → (version 8) → [lab3w.fr | DNSViz](https://dnsviz.net/d/lab3w.fr/dnssec/)

- ECDSA/SHA-256 → (version 13) → [ipv10.net | DNSViz](https://dnsviz.net/d/ipv10.net/dnssec/)

Et que l’extension, le NIC .TV ne supporte pas encore l’algo 13 ?

Je demande cela parce que, sur mes autres extensions .FR/.COM/.EU etc… çà fonctionne très bien, avec seulement mon NameServeur [dns.ipv10.net](http://dns.ipv10.net).

```auto
root@lv1.dns:~ # host dns.ipv10.net
dns.ipv10.net has address 135.125.133.51
dns.ipv10.net has address 158.69.126.137
dns.ipv10.net has IPv6 address 2607:5300:60:9389:15:1:a:1000
dns.ipv10.net has IPv6 address 2001:41d0:701:1100::6530

```

…

```auto
root@lv1.dns:~ # host dns.lab3w.fr
dns.lab3w.fr has address 158.69.126.137
dns.lab3w.fr has IPv6 address 2607:5300:60:9389:15:1:a:1000

```

Merci.

Romain

---

<div class="post-metadata">

**Author:** ![anon36725218](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/8e8cbc/32.png) [@anon36725218](https://www.debian-fr.org/u/anon36725218)\
**Post date:** [Juin 19, 2023, 5:42 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373/5 "2023-06-19T17:42:00Z")

</div>

Bug on commande Linux (debian et ?) Who·is - Pas résolu le sujet - title 😉

Merci @Clochette - lui c’est @Clochette, moi c’est @ZW3B 😉

---

<div class="post-metadata">

**Author:** ![anon70622873](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/278dde/32.png) [@anon70622873](https://www.debian-fr.org/u/anon70622873)\
**Post date:** [Juin 19, 2023, 5:57 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373/6 "2023-06-19T17:57:14Z")

</div>

Probablement, oui. La commande `whois` ne sait pas trouver le bon serveur pour le TLD .tv

```auto
whois -h whois.nic.tv zw3b.tv

```

---

<div class="post-metadata">

**Author:** ![anon36725218](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/8e8cbc/32.png) [@anon36725218](https://www.debian-fr.org/u/anon36725218)\
**Post date:** [Juin 19, 2023, 6:03 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373/7 "2023-06-19T18:03:04Z")

</div>

Ca doit fonctionner maintenant bruno, lui c @anon70622873 😉

Je n’ai pas de console linux sous la main 😉

---

<div class="post-metadata">

**Author:** ![anon36725218](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/8e8cbc/32.png) [@anon36725218](https://www.debian-fr.org/u/anon36725218)\
**Post date:** [Juin 19, 2023, 6:06 UTC](https://www.debian-fr.org/t/whois-command-on-domain-tv-no-match-for-domain/88373/8 "2023-06-19T18:06:45Z")

</div>

Hors sujet : sinon Godaddy ont activité les DNS record #DMARC depuis aujourd’hui pour leurs clients ? Et les autres ?

Je crois… j’entends nos Seigneurs, me semble-t-il 😉

Peut-être m’entendent-ils 😕 eux aussi 💖

Le tuto (évitent le subdomain si tu as suelement un webmail en ton nom) :

> **[Comment avoir des Records DMARC valident sur les DNS internationaux ? \*...](https://howto.zw3b.fr/linux/serveurs/comment-avoir-des-records-dmarc-valident-sur-les-dns-internationaux)**
>
> Bonne configuration des enregistrements DMARC : DNS Record found, DMARC Record found et DMARC Quarantine/Reject policy enabled

🤣
