This is fixed in upstream. It's not clear if a minimal fix can be found
and applied to trusty and xenial. I've made the latest Debian version
available in my stable PPA at
https://launchpad.net/~r0lf/+archive/ubuntu/stable for people to use.
** Changed in: whois (Ubuntu)
Status: Fix Committ
** Tags added: patch server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643718
Title:
WHOIS .BM TLD server incorrect
To manage notifications about this bug go to:
https://bugs.launchpad.net
I can confirm this issue for trusty. I hope we can bbackport to trusty
and xenial.
** Changed in: whois (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16437
Please see below comment after which bug can be closed
https://github.com/rfc1036/whois/pull/44
rfc1036 commented
Thank you, in 5.2.14 I switched to a new server which I suspect will be more
stable.
** Changed in: whois (Ubuntu)
Status: New => Fix Committed
--
You received this bug no
** Changed in: whois (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643718
Title:
WHOIS .BM TLD server incorrect
To manage notifications about this bug go
Hey Robbie,
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/whois/wily-proposed/view/head:/tld_serv_list
change is not present in latest purposed,
I did also submit a patch to whois on GitHub
https://github.com/rfc1036/whois/compare/next...hwsknudsen:patch-1
for the same issue
https://
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
You did not state which version of whois you are using, so I cannot
confirm if this bug has been fixed in the development release yet.
Please can you provide this?
If this isn't yet fixed in the development releas
