On Thu, 13 Jun 2002 23:25:14 -0500 "Michael D. Schleif" <[EMAIL PROTECTED]> wrote:
[ snip ] > Let's slow down and look at this carefully. > I assume that 24.118.176.137 is your external address -- right? Correct. [ snip ] > Now, if you were using only attbi's dns servers that they assigned to > you, there is no reason that your system would be contacting them for > dns. >From memory, when we used to have the old one way cable modem (dial in with phone, receive data thru cable modem) we were assigned a dns IP number. However, since they upgraded us to a two way cable modem, they do not supply a dns IP. On AT&T's web site, they actually state to disable DNS for windows 9x users. dnscache shouldn't interfer with that should it? > Therefore, it is reasonable to assume that your system is mis-configured > for dns. Are you using dnscache? tinydns? bind? dnscache only. However I do not recall ever doing any configuration for that. I am using basic Dachstein with the following packages; root 4.0.6 etc 4.0.1 ramlog 1.1 local 4.0.6 modules 4.0.6 dhclient 2.0pl5 dhcpd 2.0pl5 dnscache 1.05a weblet 1.2.0 psentry 1.0 libz sshd 3.0p1 ssh 3.0p1 > The fact that you say that these connections are only a subset of an > overwhelming number of identical connections indicates a serious > configuration problem on your gateway box. I do not know enough to say I know for sure, but I believe the configuration problem lies in ATTBI's area. See, when I have these "unable to connect to the net" problems, so does everyone else in my neighborhood, it has been documented - plus I know of some people with slightly different IP numbers than mine that are AT&T customers and they have connection problems at the same time I do. All I do, is check weblet out to see what is going on, and thats the only thing I find out of the ordinary is multiple established connections to my router, to external port 53 domain servers. Guitarlynn sent me this info; "By default Dachstein has: ## UDP Services open to outside world # Space seperated list: srcip/mask_dstport # NOTE: bootpc port is used for dhcp client EXTERN_UDP_PORTS="0/0_domain 0/0_bootpc" Remove the "0/0_domain" entry, but leave the "0/0_bootpc" if you are using DHCP to connect to your ISP. I have had this problem once or twice.... other DNS servers are trying to connect to your DNS server on the router (dnscache, tinydns, bind, whatever). I've never had it choke out a router, but dropping the open port will stop them." I did just that, and so far so good. Even the net seems to be a tad faster now. > Do you know _why_ your system might be contacting these root domain > servers? > > What do you think? Not too sure what is going on. Just seems odd that when our ability to connect to the web is shot, everybody elses seems to be also. Can't imagine my lil ole LRP router is bringing down the Internet in the Minneapolis area! Thanks for your help again Michael _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
