0000889: DHCP assigned DNS servers. If first DNS lookup fails, it does not seem to check the rest.

Notes
(0000837) paul_va3pc (reporter) 2008-06-09 10:44	It appears that the bug system takes the number sign as a shortcut to an existing bug report. Please do not take the hyperlinks literally, and just refer the numbers to the DNS servers as listed in the webconfig page.

(0000838) peter (administrator) 2008-06-09 11:33	You will see that behavior when a DNS server is responding, but responding with "DNS record does not exist". There's no need to check DNS no.2 and no.3 if the first one responded. There are two common causes: 1) The upstream DNS server is broken. 2) The upstream DNS server is an authoritative server, not a caching/forwarding server. Only use DNS servers provided by your ISP (or some other caching service). Using something like ns1.pointclark.net (an authoritative DNS server) is... bad. Hmmmm... the warning on the IP settings page should really read something like "DNS did not return information" instead of "DNS server is not responding". There's a subtle difference.

(0000839) paul_va3pc (reporter) 2008-06-09 13:30	I agree - the upstream DNS server is sometimes broken ;-) These are the DNS's from my ISP (as given by DHCP on wan). Whenever things bog down, I change the non-responsive DNS to an openDNS address and after restarting services, things are OK until my network restarts.