Search Again: Re: DNS problem From: Men & Mice Support Date: Wednesday, May 26, 1999 Time: 5:38:00 am >We have encountered a problem that we have been unable to solve. > >Our proxy sever and web server halt at intermittent times and on the event >log we get the following error message. > >"DNS Server encountered a packet addressed to itself -- IP address >203.58.14.7. The DNS server should never be sending a packet to itself. >This situation usually indicates a configuration error. Check the following >areas for possible self-send configuration errors: 1) Forwarders list. >(DNS servers should not forward to themselves). 2) Master lists of >secondary zones. 3) Notify lists of primary zones. 4) Delegations of >subzones. Must not contain NS record for DNS server Example: -> >This DNS server dns1.foo.com is the primary for the zone foo.com. -> You >have delegated the zone bar.foo.com to bardns.bar.foo.com. and are >NOT running the bar.foo.com zone on this DNS (dns1.foo.com). -> >bar.foo.com MUST NOT have an NS record that points at dns1.foo.com. >Note, you should make this check (with nslookup or DNS manager) both on >this DNS server and on the server(s) you delegated the subzone to. It is >possible that the delegation was done correctly, but that the primary >DNS for the subzone, has any incorrect NS record pointing back at this >server. If this incorrect NS record is cached at this server, then the >self-send could result. If found, the subzone DNS server admin should >remove the offending NS record". > >The servers still run however our web sites seize. Is there any particular >errors that you can suggest we focus on?? One possible reason is if your server has been the victim of a DNS spoofing attack. I notice that your servers are vulnerable to this. You should upgrade to the latest version of QuickDNS Pro, which isn't vulnerable this way. The upgrade is free to owners of version 2.x. After looking over your zone files, I don't see any other reason for this behavior. Make sure the proxy server isn't trying to do anything in terms of DNS service. I assume you've checked the forwarders list in QuickDNS Admin, as well as the Secondary Domains file. If you're using the WebSTAR proxy server, and the proxy server locks up, that would explain why the web server fails. If the proxy server locks when trying to do something DNS related, that might explain why QuickDNS Pro is reporting a problem. Off topic: I noticed that the SOA record (domain info) for intelligent.com.au has an exceedingly large TTL: 1762590720. That translates to around 55 years. I hope you never need to change any of your other SOA values, because they'll be cached for a long, long time. Hope this helps. ____________________________________________________________________ Chris Buxton Men & Mice cbuxton@menandmice.com http://www.menandmice.com

Messages In This Thread: DNS problem by Marconi on Jun 3, 1997 at 12:30:00 am Re: DNS problem by Allan C. Reichert on Jun 3, 1997 at 11:23:00 am DNS problem by ian on May 26, 1999 at 4:53:00 am Re: DNS problem by Men & Mice Support on May 26, 1999 at 5:38:00 am DNS problem by Dennis J. Bonsall, Jr. on Jan 23, 2001 at 7:01:04 pm Re: DNS problem by Men & Mice Support on Jan 23, 2001 at 7:08:09 pm DNS problem by Mark Workman on Jun 22, 2001 at 1:15:39 pm Re: DNS problem by Global Homes Webmaster on Jun 22, 2001 at 1:21:50 pm Re: DNS problem by Lawrence W. Churchill on Jun 22, 2001 at 1:23:07 pm Re: DNS problem by Suzanne Swift on Jun 22, 2001 at 1:40:58 pm Re: Re: DNS problem by mail.hgcpc.com on Jun 23, 2001 at 4:54:43 pm Re: Re: DNS problem by Mia''s Virtual Post Office on Jun 25, 2001 at 11:43:39 am Re: Re: DNS problem by Men & Mice Support on Jun 25, 2001 at 6:53:06 pm Re: Re: DNS problem by Mia''s Virtual Post Office on Jun 25, 2001 at 9:55:12 pm Re: DNS problem by Bennie Warren on Jun 25, 2001 at 10:04:29 pm Re: DNS Problem by Jody McAlister on Nov 1, 2004 at 10:06:22 am Re: DNS Problem by Scott Haneda on Nov 1, 2004 at 3:42:40 pm