First Last Prev Next    This bug is not in your last search results.
Bug 2806 - DNS broken: No default nameserver in resolv.conf
DNS broken: No default nameserver in resolv.conf
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: caching-nameserver (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 1999-05-13 20:34 EDT by warwick
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-05-15 16:23:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description warwick 1999-05-13 20:34:24 EDT 
Changing from 5.1 to 6.0, with no `nameserver' line in
/etc/resolv.conf for either install, 5.1's DNS defaults to
localhost, but 6.0's just fails. (Lynx, Netscape, ping...)

Add `nameserver 127.0.0.1' to resolv.conf.

resolv.conf isn't owned by any package, but this seems to be
something you'd want if you run a caching nameserver
locally.
Comment 1 warwick 1999-05-13 20:36:59 EDT 
Sorry, I said `changing from 5.1 to 6.0'. I meant `observed difference
from 5.1 in a fresh install of 6.0'
Comment 2 Jeff Johnson 1999-05-15 16:23:59 EDT 
The installer (and ultimately the user) is responsible for
configuring the DNS client. Assuming that there is a nameserver
running on localhost is not the Right Thing To Do.

------- Email Received From  Tim Baverstock <warwick@sable.demon.co.uk> 05/15/99 18:43 -------
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.