Bug 500075 - DNS don't work after restart system.
DNS don't work after restart system.
Status: CLOSED DUPLICATE of bug 453304
Product: Fedora
Classification: Fedora
Component: squid (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jiri Skala
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-05-10 13:52 EDT by Pavel Alexeev
Modified: 2014-11-09 17:31 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-11 14:25:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pavel Alexeev 2009-05-10 13:52:44 EDT
Description of problem:

All work fine just after squid restart:
service squid restart

No any DNS-relied options was be changed from default config.

If I restart full system, squid already started as planned, but can't resolve any domains and return erro 503 for users on any non-cached domains. It is means also if say I do
wget http://google.com
and then request it throught squid - all works.

I test, ALL servers, listed in /etc/resolv.conv vork and resolve domains properly. Futhermore, if I put its nameservers directly to squid config
all works fine - just after that, and after machine restart too.

Version-Release number of selected component (if applicable):
# rpm -q squid

How reproducible:

Steps to Reproduce:
1. Reboot machine
2. Try use squid
Actual results:
503 error
Comment 1 Jiri Skala 2009-05-11 09:42:19 EDT
please check for BZ #453304 (especially comment #3). I suppose this could be the same issue. Let me know  your findings.

Thanks, regards

Comment 2 Pavel Alexeev 2009-05-11 14:25:24 EDT

*** This bug has been marked as a duplicate of bug 453304 ***
Comment 3 Pavel Alexeev 2009-05-11 14:26:13 EDT
Ok, you are right, it is seems as dublicate. I'll continue in pointed bugreport.

Note You need to log in before you can comment on or make changes to this bug.