I keep getting "connection failure" & "error dns lookup failed" errors in the ClearOS gui.
I'm running ClearOS 7_final with multi-WAN.
ISP1 runs static public IPs and is cleanly bridged.
ISP2 (DSL via BG210-700 router) appears to fake bridging with a passthrough mode, apparently applying its public IP via DHCP to a selected mac address.
The setup works on the surface, as the ISP's dynamic public appears in ClearOS IP settings for that wan nic. An issue arises when the auto DNS sensing picks up the router's DNS info as the private lan IP of the router 192.168.1.1. Well I'm guessing there is a crash somewhere as that private IP is not in the same subnet as the dynamic public IP assigned to clear's WAN nic. I take this to be the problem, because when I temporarily assign proper DNS server IPs the errors go away. I'll note that the internet seems to work for clients, but the gui is freaking out, leading me to question the stability and/or future of the setup.
Thoughts on making DNS server settings permanent?
I'm running ClearOS 7_final with multi-WAN.
ISP1 runs static public IPs and is cleanly bridged.
ISP2 (DSL via BG210-700 router) appears to fake bridging with a passthrough mode, apparently applying its public IP via DHCP to a selected mac address.
The setup works on the surface, as the ISP's dynamic public appears in ClearOS IP settings for that wan nic. An issue arises when the auto DNS sensing picks up the router's DNS info as the private lan IP of the router 192.168.1.1. Well I'm guessing there is a crash somewhere as that private IP is not in the same subnet as the dynamic public IP assigned to clear's WAN nic. I take this to be the problem, because when I temporarily assign proper DNS server IPs the errors go away. I'll note that the internet seems to work for clients, but the gui is freaking out, leading me to question the stability and/or future of the setup.
Thoughts on making DNS server settings permanent?
In DNS Server
Share this post:
Responses (3)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
MultiWAN has a particular problem with DNS. The short answer says you need to fix the DNS servers manually to a public DNS service such as OpenDNS, GoogleDNS or Cloudflare or other. So, for each external NIC, disable the Automatic DNS server entries. When all are disabled, the DNS Servers box button changes from something like Temporary Override to Edit.
The long answer is that many (most?) ISP's only allow you to use their DNS servers from within their network and do not allow external access. Now if ClearOS, because of load balancing, pushes traffic to ISP1's DNS servers via ISP2's network, the DNS lookup will fail. Because of this you need to use publicly accessible DNS servers so they can be accessed via either WAN.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »