failed with nslookup for www.google.com, others domain names are fine

Bug #1018094 reported by Jjeff liao
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bind9 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

failed on www.google.com with "nslookup", other domain names all returned ok.
built bind-9.1.2 myself, my named works fine with www.google.com and other domain.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bind9 1:9.8.1.dfsg.P1-4ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Tue Jun 26 15:58:58 2012
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 bind9utils 1:9.8.1.dfsg.P1-4ubuntu0.1
 apparmor 2.7.102-0ubuntu3
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jjeff liao (jl1076) wrote :
Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I failed to reproduce this using:

bind9 1:9.8.1.dfsg.P1-4
dnsutils 1:9.8.1.dfsg.P1-4

bind9 1:9.8.1.dfsg.P1-4ubuntu0.1
dnsutils 1:9.8.1.dfsg.P1-4ubuntu0.1

What makes you think that this is a bug in bind9? Do you have exact steps to reproduce, and have you verified that this happens on more than one ISP?

Changed in bind9 (Ubuntu):
status: New → Incomplete
Revision history for this message
Jjeff liao (jl1076) wrote : Re: [Bug 1018094] Re: failed with nslookup for www.google.com, others domain names are fine

Hi Robie,

Thanks for your trying.  "named" works fine today.

The named 9.1.2 on ubuntu 12.04 (desktop) works fine today with nslookup (same harddrive).
Returning all domains correctly, including google.com.
Look like my bug report was a false alarm.

Good job, I love ubuntu. thanks

Jeff Liao

--- On Thu, 6/28/12, Robie Basak <email address hidden> wrote:

From: Robie Basak <email address hidden>
Subject: [Bug 1018094] Re: failed with nslookup for www.google.com, others domain names are fine
To: <email address hidden>
Date: Thursday, June 28, 2012, 5:59 PM

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

I failed to reproduce this using:

bind9    1:9.8.1.dfsg.P1-4
dnsutils    1:9.8.1.dfsg.P1-4

bind9    1:9.8.1.dfsg.P1-4ubuntu0.1
dnsutils    1:9.8.1.dfsg.P1-4ubuntu0.1

What makes you think that this is a bug in bind9? Do you have exact
steps to reproduce, and have you verified that this happens on more than
one ISP?

** Changed in: bind9 (Ubuntu)
       Status: New => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1018094

Title:
  failed with nslookup for www.google.com, others domain names are fine

Status in “bind9” package in Ubuntu:
  Incomplete

Bug description:
  failed on www.google.com with "nslookup", other domain names all returned ok.
  built bind-9.1.2 myself, my named works fine with www.google.com and other domain.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bind9 1:9.8.1.dfsg.P1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Tue Jun 26 15:58:58 2012
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   bind9utils 1:9.8.1.dfsg.P1-4ubuntu0.1
   apparmor   2.7.102-0ubuntu3
  SourcePackage: bind9
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1018094/+subscriptions

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.]

Changed in bind9 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.