Bug #838
closed
DNS servers are not cleared from resolv.conf when link comes down
Added by Marcus Brown over 14 years ago.
Updated about 14 years ago.
Description
When bringing down PPP,PPPoE,PPTP,L2TP we don't clear the DNS server IPs associated with those links from the /var/etc/resolv.conf file.
Maybe add system_hosts_generate() to the interface_bring_down function? There should probably be more to it than that since they should probably be cleared is the link comes down due to other factors like ISP problems of cable problems between ISP and pfSense.
This causes problems for our cable modem friends in Israel in this thread: http://forum.pfsense.org/index.php/topic,25465.0.html
I'm not sure what to do so this can be a discussion about it, or if others feel confident to just make the change then that works too.
- Category set to Interfaces
- Target version set to 2.0
- Affected Version set to 2.0
- Status changed from New to Feedback
The file gets generated (/tmp/resolv_conf_generate) but /usr/local/sbin/check_reload_status doesn't know how to handle it, and nameservers don't get cleared.
There is not yet a new snapshot that includes the rebuilt check_reload_status that can handle this. It's building now. It will show up in several hours.
Mmm. Yes, I see I missed that detail. :)
It doesn't look like it's going to work.
Patch: (rc.rc.resolv_conf_generate)
{ "/tmp/resolv_conf_generate", "/etc/rc.rc.resolv_conf_generate",
101 "Rewriting resolv.conf", CYCLE}
Works now.
Is there any efficient way to make adding and removing nameservers faster?
What do you mean efficent?
I mean, I presume that this nameserver handling is done this way to keep the GUI responsive, so is there a way to get the nameservers updated(added and removed to /etc/hosts) faster while still keeping the GUI fast too?
What is the reason to handle nameserver updates through check_reload_status?
This works now. This issue can be closed.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF