pfSense bugtracker: Issueshttps://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162011-03-10T15:41:45ZpfSense bugtracker
Redmine pfSense - Bug #1345 (Closed): Static routes to DNS on local subnet should not be addedhttps://redmine.pfsense.org/issues/13452011-03-10T15:41:45ZFuren Xiaoxfuren@gmail.com
<p>In /sbin/dhclient-script : add_new_resolv_conf(),<br />it says:<br />@
# Add a route to the nameserver out the correct interface
# so that mulitple wans work correctly with multiple dns
# also backup the nameserver for later route removal<br /> echo $nameserver >>/var/etc/nameserver_$interface<br /> $ROUTE add $nameserver -iface $interface<br /><code><br />Unfortunately, adding these routes will cause problems if the nameservers are not in the same network of that interface.<br />For example,<br /></code><br />dhclient: New IP Address (re1): 172.16.26.99<br />dhclient: New Subnet Mask (re1): 255.255.255.0<br />dhclient: New Broadcast Address (re1): 172.16.26.255<br />dhclient: New Routers (re1): 172.16.26.254<br />dhclient: Adding new routes to interface: re1<br /><code><br />will add some direct routes like<br /></code><br />172.16.3.95 1a:8b:41:87:38:99 UHS 0 0 1500 re1 <br />172.16.3.96 1a:8b:41:87:38:99 UHS 0 0 1500 re1 <br />@<br />, where 172.16.3.95 and 172.16.3.96 are the nameservers.<br />However, these servers are not in the same network and need another router to reach.<br />So these servers become unreachable.</p>