Javier
Not sure I quite understand your original bug report.
Are you saying that dig does not honour the search path in
/etc/resolv.conf? That is default behavior for dig and if you specify a
simple hostname only if will try the ROOT servers - which normally
fails.
Use the +search option to
Sorry, I have misunderstood the man. I didn't understand that the
configuration from resolv.conf was taken depending on the parameters. It
uses just the servers in resolv.conf by default, not the entire
configuration.
** Changed in: bind9 (Ubuntu)
Status: Incomplete = Invalid
--
You
I changed twice the package to dnsutils but launchpad changed it :(
Have you tested it?
--
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/1007916
Title:
dig doesn't resolve domain
--
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/1007916
Title:
dig doesn't resolve domain hostnames
To manage notifications about this bug go to:
dig is provided by dnsutils
--
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/1007916
Title:
dig doesn't resolve domain hostnames
To manage notifications about this bug go to:
and bind9 is the source package for that, so nevermind!
--
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/1007916
Title:
dig doesn't resolve domain hostnames
To manage notifications
