.med TLD 99.98% lame delegations?
The current state of the .med TLD is rather odd, with ~99.98% delegations lame! Just 9 of the almost 42000 delegations are working. Is the TLD going away? If not, what explains the almost total breakage? -- Viktor.
I bet nic.med and trust.med are among the 9 working ones… are the ones working using the same DNS servers as the ones not working ? Rubens
Em 25 de ago. de 2024, à(s) 23:52, Viktor Dukhovni via gtld-tech <gtld-tech@icann.org> escreveu:
The current state of the .med TLD is rather odd, with ~99.98% delegations lame! Just 9 of the almost 42000 delegations are working.
Is the TLD going away? If not, what explains the almost total breakage?
-- Viktor. _______________________________________________ gtld-tech mailing list -- gtld-tech@icann.org To unsubscribe send an email to gtld-tech-leave@icann.org
________________________________________________By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
On Mon, Aug 26, 2024 at 12:03:21AM -0300, Rubens Kuhl via gtld-tech wrote:
I bet nic.med and trust.med are among the 9 working ones… are the ones working using the same DNS servers as the ones not working ?
No for "nic.med", which appears to be "self-hosted", though the underlying IP addresses are with Nominet. nic.med. IN NS dns1.nic.med. nic.med. IN NS dns2.nic.med. nic.med. IN NS dns3.nic.med. nic.med. IN NS dns4.nic.med. nic.med. IN NS dnsa.nic.med. nic.med. IN NS dnsb.nic.med. nic.med. IN NS dnsc.nic.med. nic.med. IN NS dnsd.nic.med. Yes, for trust.med which like the non-working domains is delegated to one of the Google Domains server clusters. trust.med. IN NS ns-cloud-d2.googledomains.com. trust.med. IN NS ns-cloud-d1.googledomains.com. trust.med. IN NS ns-cloud-d3.googledomains.com. trust.med. IN NS ns-cloud-d4.googledomains.com. I say "delegated to", rather than "using", since with REFUSED as the response from Google Domains, it is more "misusing" than "using". Sample lame delegations: 0591-3916-68.med. NS ns-cloud-a1.googledomains.com. 0591-3916-68.med. NS ns-cloud-a2.googledomains.com. 0591-3916-68.med. NS ns-cloud-a3.googledomains.com. 0591-3916-68.med. NS ns-cloud-a4.googledomains.com. ; 30310337358905.med. NS ns-cloud-b1.googledomains.com. 30310337358905.med. NS ns-cloud-b2.googledomains.com. 30310337358905.med. NS ns-cloud-b3.googledomains.com. 30310337358905.med. NS ns-cloud-b4.googledomains.com. ; 0093-1721-01.med. NS ns-cloud-c1.googledomains.com. 0093-1721-01.med. NS ns-cloud-c2.googledomains.com. 0093-1721-01.med. NS ns-cloud-c3.googledomains.com. 0093-1721-01.med. NS ns-cloud-c4.googledomains.com. ; 69292-538-10.med. NS ns-cloud-d1.googledomains.com. 69292-538-10.med. NS ns-cloud-d2.googledomains.com. 69292-538-10.med. NS ns-cloud-d3.googledomains.com. 69292-538-10.med. NS ns-cloud-d4.googledomains.com. ; 59762-0800-2.med. NS ns-cloud-e1.googledomains.com. 59762-0800-2.med. NS ns-cloud-e2.googledomains.com. 59762-0800-2.med. NS ns-cloud-e3.googledomains.com. 59762-0800-2.med. NS ns-cloud-e4.googledomains.com. -- Viktor.
Since those are all drug codes registered to registry itself, it looks like a *-up that removed provisioning from such domains. Rubens
Em 26 de ago. de 2024, à(s) 00:33, Viktor Dukhovni via gtld-tech <gtld-tech@icann.org> escreveu:
On Mon, Aug 26, 2024 at 12:03:21AM -0300, Rubens Kuhl via gtld-tech wrote:
I bet nic.med and trust.med are among the 9 working ones… are the ones working using the same DNS servers as the ones not working ?
No for "nic.med", which appears to be "self-hosted", though the underlying IP addresses are with Nominet.
nic.med. IN NS dns1.nic.med. nic.med. IN NS dns2.nic.med. nic.med. IN NS dns3.nic.med. nic.med. IN NS dns4.nic.med. nic.med. IN NS dnsa.nic.med. nic.med. IN NS dnsb.nic.med. nic.med. IN NS dnsc.nic.med. nic.med. IN NS dnsd.nic.med.
Yes, for trust.med which like the non-working domains is delegated to one of the Google Domains server clusters.
trust.med. IN NS ns-cloud-d2.googledomains.com. trust.med. IN NS ns-cloud-d1.googledomains.com. trust.med. IN NS ns-cloud-d3.googledomains.com. trust.med. IN NS ns-cloud-d4.googledomains.com.
I say "delegated to", rather than "using", since with REFUSED as the response from Google Domains, it is more "misusing" than "using". Sample lame delegations:
0591-3916-68.med. NS ns-cloud-a1.googledomains.com. 0591-3916-68.med. NS ns-cloud-a2.googledomains.com. 0591-3916-68.med. NS ns-cloud-a3.googledomains.com. 0591-3916-68.med. NS ns-cloud-a4.googledomains.com. ; 30310337358905.med. NS ns-cloud-b1.googledomains.com. 30310337358905.med. NS ns-cloud-b2.googledomains.com. 30310337358905.med. NS ns-cloud-b3.googledomains.com. 30310337358905.med. NS ns-cloud-b4.googledomains.com. ; 0093-1721-01.med. NS ns-cloud-c1.googledomains.com. 0093-1721-01.med. NS ns-cloud-c2.googledomains.com. 0093-1721-01.med. NS ns-cloud-c3.googledomains.com. 0093-1721-01.med. NS ns-cloud-c4.googledomains.com. ; 69292-538-10.med. NS ns-cloud-d1.googledomains.com. 69292-538-10.med. NS ns-cloud-d2.googledomains.com. 69292-538-10.med. NS ns-cloud-d3.googledomains.com. 69292-538-10.med. NS ns-cloud-d4.googledomains.com. ; 59762-0800-2.med. NS ns-cloud-e1.googledomains.com. 59762-0800-2.med. NS ns-cloud-e2.googledomains.com. 59762-0800-2.med. NS ns-cloud-e3.googledomains.com. 59762-0800-2.med. NS ns-cloud-e4.googledomains.com.
-- Viktor. _______________________________________________ gtld-tech mailing list -- gtld-tech@icann.org To unsubscribe send an email to gtld-tech-leave@icann.org
________________________________________________By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
Yes, for trust.med which like the non-working domains is delegated to one of the Google Domains server clusters. trust.med. IN NS ns-cloud-d2.googledomains.com. trust.med. IN NS ns-cloud-d1.googledomains.com. trust.med. IN NS ns-cloud-d3.googledomains.com. trust.med. IN NS ns-cloud-d4.googledomains.com.
I say "delegated to", rather than "using", since with REFUSED as the response from Google Domains
Resolves from multiple places I can check trust.med. 172800 IN NS ns-cloud-d1.googledomains.com. trust.med. 172800 IN NS ns-cloud-d2.googledomains.com. trust.med. 172800 IN NS ns-cloud-d3.googledomains.com. trust.med. 172800 IN NS ns-cloud-d4.googledomains.com. trust.med. 300 IN A 34.73.231.229 And loads in a browser from desktops in uk, us, nl and sg for me. Rob
On 2024-08-26 05:11, Rob Golding wrote:
Yes, for trust.med which like the non-working domains is delegated to one of the Google Domains server clusters. trust.med. IN NS ns-cloud-d2.googledomains.com. trust.med. IN NS ns-cloud-d1.googledomains.com. trust.med. IN NS ns-cloud-d3.googledomains.com. trust.med. IN NS ns-cloud-d4.googledomains.com.
I say "delegated to", rather than "using", since with REFUSED as the response from Google Domains
Resolves from multiple places I can check
However the others (sorry missed the list 1st time round) don't resolve as you noted. Rob
On Mon, Aug 26, 2024 at 05:12:50AM +0100, Rob Golding via gtld-tech wrote:
On 2024-08-26 05:11, Rob Golding wrote:
Yes, for trust.med which like the non-working domains is delegated to one of the Google Domains server clusters. trust.med. IN NS ns-cloud-d2.googledomains.com. trust.med. IN NS ns-cloud-d1.googledomains.com. trust.med. IN NS ns-cloud-d3.googledomains.com. trust.med. IN NS ns-cloud-d4.googledomains.com.
I say "delegated to", rather than "using", since with REFUSED as the response from Google Domains
Resolves from multiple places I can check
However the others (sorry missed the list 1st time round) don't resolve as you noted.
The trust.med domain is one of the handful of exceptions. -- Viktor.
participants (3)
-
Rob Golding -
Rubens Kuhl -
Viktor Dukhovni