asked on
DNS errors
Hi,
Am am getting a ton of informational entries and warnings in the DNS log which is filling it up every couple of days generating an Eventlog Service message stating, "The DNS server log is full". The messages in the log are as follows:
Warning: The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine the DNS server event log entries that precede this event. To prevent the DNS server from filling the event log too quickly, subsequent events with Event IDs higher than 3000 will be suppressed until events are no longer being generated at a high rate.
Information: The DNS server encountered an invalid domain name in a packet from 68.87.77.130. The packet will be rejected. The event data contains the DNS packet.
The warnings occur a couple times per hour and the information alerts occur every couple seconds. Sometimes multiple times during the same second.
Am am getting a ton of informational entries and warnings in the DNS log which is filling it up every couple of days generating an Eventlog Service message stating, "The DNS server log is full". The messages in the log are as follows:
Warning: The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine the DNS server event log entries that precede this event. To prevent the DNS server from filling the event log too quickly, subsequent events with Event IDs higher than 3000 will be suppressed until events are no longer being generated at a high rate.
Information: The DNS server encountered an invalid domain name in a packet from 68.87.77.130. The packet will be rejected. The event data contains the DNS packet.
The warnings occur a couple times per hour and the information alerts occur every couple seconds. Sometimes multiple times during the same second.
Windows Server 2003DNS
Last Comment
jhill777
Do you own 68.87.77.130? If not, someone is probably messing with your DNS server, trying to hack it.
ASKER
That is a Comcast DNS server. We just do the internal DNS. All external is forwarded to that DNS server. There are actually 2 diff dns servers. I get the message above about both servers.
Interesting. Are you allowing updates from that server? I can't imagine why it would need to send traffic back outside of responding to forwarded requests.
ASKER
No, not allowing updates. I only have those addresses configured as forwarders. Could it be any kind of problem related to not decommissioning a DC "properly" as it crashed and we just took it out of the mix? This server with these messages now was the server I used the commands to take over as RID Master and Operations Master. However, it didn't do this before when this server was on a T1 internet connection. We switched this one over to a Comcast 20Mbps business class line.
ASKER
Our MDaemon mail server, another DC, is still on the T1 line, if that helps. Could it have something to do with the MX records and reverse PTR still being on the ATT line?
Could be erroneous information being cached somewhere. Check out this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;241352
http://support.microsoft.com/default.aspx?scid=kb;en-us;241352
ASKER
It looks like it's enabled by default on Server 2003 though.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks, I'll try that first part. My mail is on a different server, on a different line out, with different forwarders though that are specific to the AT&T T1 it accesses the internet on.
If it is, in fact, a client computer requesting DNS info for a domain that doesn't exist, it must be a virus or spyware program that is requesting every couple seconds or multiple times a minute at least.
If it is, in fact, a client computer requesting DNS info for a domain that doesn't exist, it must be a virus or spyware program that is requesting every couple seconds or multiple times a minute at least.
ASKER
Significantly reduced messages.