Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#765 closed enhancement (wontfix)

consider building IPv6 support into bind-utils

Reported by: MMlosh Owned by: ainulindale
Priority: minor Milestone:
Component: Feed packages Version: SHR-unstable
Keywords: IPv6 Cc:

Description

busybox version of "nslookup" can do more than standalone nslookup (pkg bind-utils).

after installing package "bind-utils",
programs nslookup/dig return error message "address family unsupported".

My ISP has IPv6 DNS server that returns IPv6 addresses for google
=> there's IPv6 address in /etc/resolv.conf

Is there any reason, why there is no inet6 support compiled in?

Change History (4)

comment:1 follow-ups: Changed 8 years ago by spaetz

  • Priority changed from major to minor

busybox version of "nslookup" can do more than standalone nslookup (pkg bind-utils)

Do I get this right? busybox nslookup which is provided by default can do IPv6, right? Why is that not enough

ipv6 has been explicitely turned of in the configuration of bind, that is why it's not included. I am not sure how easy it would be to turn that on again.

comment:2 in reply to: ↑ 1 Changed 8 years ago by spaetz

Replying to spaetz:

ipv6 has been explicitely turned of in the configuration of bind, that is why it's not included.

I mean in the Openembedded upstream configuration, this is not a design choice by SHR.

comment:3 Changed 8 years ago by spaetz

  • Resolution set to wontfix
  • Status changed from new to closed

I just tried turning on ipv6 support in bind and the compilation did not suceed. Turning it off made it suceed again. So I think there was a reason for having it turned off.

Feel free to investigate this as an upstream OE issue and let us know when it can be turned on. I doubt that we can invest lots of resources into this, especially given that it's a non-standard package on the FR.

comment:4 in reply to: ↑ 1 Changed 8 years ago by MMlosh

Replying to spaetz:

Do I get this right? busybox nslookup which is provided by default can do IPv6, right? Why is that not enough

busybox nslookup can do more (even thought is says "0.0.0.0" when it asks my ipv6 server)
The trouble is, that I prefer dig to nslookup, because I believe it can do more.

But your answer is complete and OK, so I'm leaving this closed and will try to setup build environment again (failed 3 times before, just a bit skeptical)

Note: See TracTickets for help on using tickets.