Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Karlnet\]\s+Strange\s+DNS\s+issue\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Karlnet\]\s+Strange\s+DNS\s+issue\s*$/: 5 ]

Total 5 documents matching your query.

1. [Karlnet] Strange DNS issue (score: 1): Author: "Norm Young" <lists@applegatebroadband.net>; Date: Mon, 16 Feb 2004 22:39:28 -0800; In the last week or so, I've been getting complaints from customers who say that they have problems accessing the Internet via their web browsers, ie; page not found on a sporadic basis. On investiga; /archives//html/Karlnet/2004-02/msg00062.html (8,526 bytes)
2. Re: [Karlnet] Strange DNS issue (score: 1): Author: "Brett Hays" <bretth@htonline.net>; Date: Tue, 17 Feb 2004 07:26:21 -0500; Are the customers' routers obtaining their dns settings via dhcp from your ap's? -- Original Message -- From: "Norm Young" <lists@applegatebroadband.net> To: "Karlnet Mailing List" <karlnet@wispnotes; /archives//html/Karlnet/2004-02/msg00063.html (9,717 bytes)
3. Re: [Karlnet] Strange DNS issue (score: 1): Author: "Norm Young" <lists@applegatebroadband.net>; Date: Tue, 17 Feb 2004 09:30:45 -0800; No, the customers routers WAN's are set to a static IP, and the LAN side information that acts as the DHCP server has the DNS server information set on it manually. Customers are bridged to the APs v; /archives//html/Karlnet/2004-02/msg00064.html (11,366 bytes)
4. FW: [Karlnet] Strange DNS issue (score: 1): Author: "Andy Henckel" <andy@multibandcom.com>; Date: Tue, 17 Feb 2004 10:57:25 -0700; Is it posssible that anyone is using an APPLE airport? Apple airports, have in the past, broadcast DHCP on the wan interface causing DHCP problems. No, the customers routers WAN's are set to a static; /archives//html/Karlnet/2004-02/msg00065.html (11,806 bytes)
5. FW: [Karlnet] Strange DNS issue (score: 1): Author: "Andy Henckel" <andy@multibandcom.com>; Date: Tue, 17 Feb 2004 10:57:38 -0700; DHCP = troublesome, DNS redirect = troublesome. I have seen this problem for some time especially with Netgear routers that hand down their IP as DNS server. Often times restarting the router fixes i; /archives//html/Karlnet/2004-02/msg00066.html (9,204 bytes)

Current List: 1 - 5
Page: [1]