ClearFoundation Tracker - ClearOS
View Issue Details
0000105ClearOSapp-multiwan - Multi-WANpublic2010-06-09 12:412019-03-11 06:25
ChristoBresler 
 
normalfeaturealways
closedwon't fix 
 
 
0000105: Multi-WAN and DNS
Would like to recommend the following to improve DNS working in a Muti-WAN environment.

First each interface has to set its DNS manually to file whether given statically or via DHCP when interface in brought up. If this is difficult we can leave it with static assignments only.
/etc/resolv.conf.eth0
/etc/resolv.conf.ppp0
/etc/resolv.conf.ppp1

Looking at the weight assigned to an interface the resolve.conf file looks as follows.
/etc/resolv.conf
# Nameserver of interface eth0 Multi-WAN weight 100
Nameservers of interfave with highest weight first and at the top.
# Nameserver of interface ppp1 Multi-WAN weight 50
Nameservers of interface with middle weight.
# Nameserver of interface ppp0 Multi-WAN weight 1
Nameservers of interface with lowest weight.

If syswatch detects that an interface is dead remove nameserver for that interface from the resolv.conf file. If the first nameserver is changed restart Squid. ( I have noticed squid only looks at the first nameserver and if that name server does not work, the server will be able to do DNS resolution but not squid, squid reload does not seem to be sufficient only restart resolves the problem )

Look at current active /etc/resolv.conf file and add all active nameserver to table 50.
ip route add “namserver1” table 50 via 192.168.16.178 dev eth1
ip route add “nameserver2” table 50 via ppp1
No tags attached.
Issue History
2010-06-09 12:41ChristoBreslerNew Issue
2010-06-09 12:45user2Statusnew => confirmed
2019-03-11 06:25NickHNote Added: 0010591
2019-03-11 06:25NickHStatusconfirmed => closed
2019-03-11 06:25NickHResolutionopen => won't fix

Notes
(0010591)
NickH   
2019-03-11 06:25   
Recommended workarounds are to either use a public DNS service or for the user to create their own /usr/sbin/syswatch.local