Closed Bug 145953 Opened 22 years ago Closed 22 years ago

Wrong DNS lookup after DNS server address has been changed

Categories

(Core :: Networking, defect)

x86
Linux
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 64857

People

(Reporter: takahide, Unassigned)

Details

Since I'm using mozilla on linux laptops, /etc/resolv.conf is often changed by
getting DHCP leases from different networks. Since Mozilla seems to cache IP
address of DNS server only at boot time, Mozilla can't resolve URLs after such
an update of /etc/resolv.conf if the cached DNS server address is not reachable.
 
For example, If I boot mozilla at my office, DNS server address, which is
192.168.1.1, is cached. When I go home, or go to conference room with wireless
LAN card, my laptop gets new DHCP lease but Mozilla does not update cached DNS
server address. If 192.168.1.1 is not reachable from there, Mozilla no longer
resolve URLs and I have to restart it.
Dupe of bug 64857

*** This bug has been marked as a duplicate of 64857 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.