This is fixed in cosmic:
https://launchpad.net/ubuntu/+source/bind9/1:9.11.4+dfsg-3ubuntu1
** Changed in: bind9 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/351764
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/175316
Title:
no IDN in
This will be fixed in cosmic in the next upload:
root@cosmic-bind9-merge-9114:~# dig @127.0.0.1 +idnout räksmörgås.se
; <<>> DiG 9.11.4-3ubuntu1~ppa2-Ubuntu <<>> @127.0.0.1 +idnout räksmörgås.se
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status:
Debian enabled building with libidn2: https://salsa.debian.org/dns-
team/bind9/commit/3e72f1a0c5cd695b7bcdefa458869cf5566198bd
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/175316
Title:
The bionic task is fix released in the sense that the fix is published
in the official archive and available to users.
The one issue I can see wrt a fix for xenial or any other stable release
is the introduction of a new dependency via the update, that is, libidn.
But I've seen that done in the
When the bug task does not mention a specific ubuntu release, it means
"whatever is devel at the time". Now that means bionic, where it's fixed
and available, that's why the task was marked as fix released.
To have it fixed in Xenial and other stable releases, the procedure
outlined in
iputils-ping in bionic and artful is linked with libidn:
andreas@nsnx:~$ dpkg -S /bin/ping
iputils-ping: /bin/ping
andreas@nsnx:~$ ldd /bin/ping|grep idn
libidn.so.11 => /lib/x86_64-linux-gnu/libidn.so.11 (0x7f21be77)
andreas@nsnx:~$ ping -c 1 räksmörgås.se
PING räksmörgås.se
8 years passed for such an issue. :(
May be somebody will fix it at last?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/175316
Title:
no IDN in nslookup and host
To manage
Hi,
IDN is not optional on the internet today.
The IANA is publishing several IDN top level domains:
http://www.iana.org/domains/root/db
As it currently stands, I am having a difficult time using Ubuntu as a
professional internet operator at an ISP, because my only choice is
hacks like this:
!ping :) - dnsutils 1:9.7.3.dfsg-1ubuntu4.1
From the man page in ubuntu 11.10 oneiric:
IDN SUPPORT
If dig has been built with IDN (internationalized domain name) support,
it can accept and
display non-ASCII domain names. dig appropriately converts character
encoding of domain
Hm, perhaps I'm wrong, should dig tool be used with idn?
Or should it be able to translate utf-8 characters to punycode directly?
It works with punycode entered through idn command line tool, e.g. dig `idn
њњњ.срб`
--
You received this bug notification because you are a member of Ubuntu
Server
ah.. I assume idnkit (which is not packaged) is required:
dighost.c:41:24: fatal error: idn/result.h: No such file or directory
compilation terminated.41:24: fatal error: idn/result.h: No such file or
directory
compilation terminated.
--
You received this bug notification because you are a
** Changed in: bind9 (Ubuntu)
Importance: Undecided = Wishlist
--
no IDN in nslookup and host
https://bugs.launchpad.net/bugs/175316
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs mailing list
13 matches
Mail list logo
