Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Punycode TLDs not works on OpenNIC root servers

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Chronological Thread  
  • From: Joel Strasser <strasser999 AT gmail.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] Punycode TLDs not works on OpenNIC root servers
  • Date: Tue, 9 Jun 2026 09:12:17 +0200

Thank you! You are awesome! :)

>> resolve-dns -Query "vermögensberater" -QueryType NS -NameServer korridor.semia-infra.net | Select-Object -ExpandProperty AllRecords

DomainName        TimeToLive RecordClass RecordType RecordData
----------        ---------- ----------- ---------- ----------
vermögensberater. 172752     IN          NS         b.nic.xn--vermgensberater-ctb.
vermögensberater. 172752     IN          NS         d.nic.xn--vermgensberater-ctb.
vermögensberater. 172752     IN          NS         a.nic.xn--vermgensberater-ctb.
vermögensberater. 172752     IN          NS         c.nic.xn--vermgensberater-ctb.
.                 0          1232        OPT

As expected!

On Sun, 7 Jun 2026 at 01:25, Jeff Taylor <shdwdrgn AT sourpuss.net> wrote:
Sorry everyone, I totally missed this thread but someone poked me on IRC about the issue.  So it turns out that somewhere between dig 9.8 and 9.11 it started ignoring the punycode entries.  The solution appears to be including the +noidnout flag.

I just generated a new root zone and it is including the xn-- TLDs again, so I think we're in good shape.  The new zone should be propagating out and should reach everyone within the hour, hopefully it didn't break something else, but the file size seems appropriate.



On 3/15/26 06:00, R4SAS wrote:

May be, but I can see that punycode didn't work too:

; <<>> DiG 9.18.44-1~deb12u1-Debian <<>> +nocomments NS xn--90ae. @ns0.opennic.glue
;; global options: +cmd
;бг.                            IN      NS
.                       3600    IN      SOA     ns0.opennic.glue. hostmaster.opennic.glue. 2026031510 1800 900 604800 3600
;; Query time: 24 msec
;; SERVER: 2a01:4f8:c17:fa94::#53(ns0.opennic.glue) (UDP)
;; WHEN: Sun Mar 15 11:57:11 UTC 2026
;; MSG SIZE  rcvd: 127
 

; <<>> DiG 9.18.44-1~deb12u1-Debian <<>> +nocomments NS xn--90ae. @8.8.8.8
;; global options: +cmd
;бг.                            IN      NS
бг.                     21600   IN      NS      c.nic.bg.
бг.                     21600   IN      NS      b.nic.bg.
бг.                     21600   IN      NS      a.nic.bg.
бг.                     21600   IN      NS      d.nic.bg.
бг.                     21600   IN      NS      e.nic.bg.
бг.                     21600   IN      NS      p.nic.bg.
;; Query time: 168 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Mar 15 11:57:05 UTC 2026
;; MSG SIZE  rcvd: 139
 

"jose morales jr" djem AT hotmail.com – March 15, 2026 2:28 PM
 

If not mistaken the dns holds the punycode version, the registry holds both versions of and translates it, registry must have support for the language encoding to translate on their root dns resolver.


 

Get Outlook for Android

From: discuss-request AT lists.opennicproject.org <discuss-request AT lists.opennicproject.org> on behalf of R4SAS <r4sas AT i2pd.xyz>
Sent: Sunday, March 15, 2026 6:10:44 PM
To: discuss AT lists.opennicproject.org <discuss AT lists.opennicproject.org>
Subject: [opennic-discuss] Punycode TLDs not works on OpenNIC root servers

Hello. I got message from one of users that all OpenNIC servers do not work with ccTLDs, which must itself written with punycode.

For example: I trying to use Bulgarian zone бг. with TIER0 and TIER1 servers and no one responds correctly.
Here you can see bg. SOA:
; <<>> DiG 9.18.44-1~deb12u1-Debian <<>> +nocomments NS bg. @ns2.opennic.glue
;; global options: +cmd
;bg.                            IN      NS
bg.                     172800  IN      NS      b.nic.bg.
bg.                     172800  IN      NS      p.nic.bg.
bg.                     172800  IN      NS      d.nic.bg.
bg.                     172800  IN      NS      a.nic.bg.
bg.                     172800  IN      NS      e.nic.bg.
bg.                     172800  IN      NS      c.nic.bg.
a.nic.bg.               172800  IN      A       192.92.129.99
a.nic.bg.               172800  IN      AAAA    2a02:6a80::192:92:129:99
b.nic.bg.               172800  IN      A       193.68.3.232
b.nic.bg.               172800  IN      AAAA    2a02:6a80::193:68:3:232
c.nic.bg.               172800  IN      A       193.68.99.99
c.nic.bg.               172800  IN      AAAA    2a02:6a80::193:68:99:99
d.nic.bg.               172800  IN      A       194.0.32.1
d.nic.bg.               172800  IN      AAAA    2001:678:3c::1
e.nic.bg.               172800  IN      A       185.143.80.1
e.nic.bg.               172800  IN      AAAA    2a02:6a80:530e::1
p.nic.bg.               172800  IN      A       204.61.216.110
p.nic.bg.               172800  IN      AAAA    2001:500:14:6110:ad::1
;; Query time: 148 msec
;; SERVER: 2001:470:4212:10:0:100:53:10#53(ns2.opennic.glue) (UDP)
;; WHEN: Sun Mar 15 11:02:17 UTC 2026
;; MSG SIZE  rcvd: 395

and at same time бг.:
; <<>> DiG 9.18.44-1~deb12u1-Debian <<>> +nocomments NS бг. @ns0.opennic.glue
;; global options: +cmd
;бг.                            IN      NS
.                       3600    IN      SOA     ns0.opennic.glue. hostmaster.opennic.glue. 2026031510 1800 900 604800 3600
;; Query time: 32 msec
;; SERVER: 2a01:4f8:c2c:e789::#53(ns0.opennic.glue) (UDP)
;; WHEN: Sun Mar 15 11:02:39 UTC 2026
;; MSG SIZE  rcvd: 127
And here correct response from Google:
; <<>> DiG 9.18.44-1~deb12u1-Debian <<>> +nocomments NS бг. @8.8.8.8
;; global options: +cmd
;бг.                            IN      NS
бг.                     21600   IN      NS      d.nic.bg.
бг.                     21600   IN      NS      p.nic.bg.
бг.                     21600   IN      NS      e.nic.bg.
бг.                     21600   IN      NS      c.nic.bg.
бг.                     21600   IN      NS      b.nic.bg.
бг.                     21600   IN      NS      a.nic.bg.
;; Query time: 124 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Sun Mar 15 11:08:09 UTC 2026
;; MSG SIZE  rcvd: 139

Jeff, can you check what's going on with them?
 


--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org



--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org



Archive powered by MHonArc 2.6.24.

Top of Page