Same here. From what I've read in various locations is that when MS DNS asks for information from a BIND server, sometimes the BIND server will send back "too much" information or information that is not "technically" correct. It's not an issue with BIND or MS DNS. In the one I spent too long investigating, the admin of the BIND server set up bad info on the his server. When MS went to put the information into the cache, it saw the incorrect set up and popped up the message below.
To make a long story short, it's nothing to really worry about. > -----Original Message----- > From: Martin Blackstone [SMTP:[EMAIL PROTECTED]] > Sent: Tuesday, October 16, 2001 12:59 PM > To: MSWinNT Discussions > Subject: RE: DNS problem > > Hmmm. I usually ignore it. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Anthony L. > Sollars > Sent: Tuesday, October 16, 2001 9:56 AM > To: MSWinNT Discussions > Subject: RE: DNS problem > > > I've noticed similar errors many times and have experimented with > packet sniffing the offending traffic. MS's DNS server has some > serious problems with logging errors. In many cases the following > will occur: > > > 1) bad dns request comes from x.x.x.x > 2) local dns server passes bad request along to root name server > (or other authoritative dns server) y.y.y.y > 3) y.y.y.y responds, question section still contains a copy of > the bad dns request. > 4) local ms dns finally checks validity of request, logs error > as having come from y.y.y.y, _not_ x.x.x.x > > > When this happens packet sniffing is the only way I've found to > identify the actual offender. > > -TOny > > -----Original Message----- > From: Mike Tree [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 16, 2001 2:13 AM > To: MSWinNT Discussions > Subject: DNS problem > > > I asked this question a few weeks ago but nobody replied, so Ill try > again as the problem is happening again. > > I get the following error in my Event log on my DNS servers > > > DNS Server encountered invalid domain name in packet from > 195.66.240.130.Packet is rejected. > > The IP addresses change, but I think they're all root nameservers. > > The problem occurs for a few days producing dozens of errors & then > stops > > Anyone any ideas? > > Mike Tree > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
