DNS error, slow internet

  • Thread starter Thread starter Kees Timmer
  • Start date Start date
K

Kees Timmer

Suddenly we have strange entries in the DNS log of our exchange server...
Frequently we see an entry 5504 and 7063 in the DNS log... Since this is
happening we also encounter problems with our internet connection.
Has someone seen this before
Can someone help us out
 
In
Kees Timmer said:
Suddenly we have strange entries in the DNS log of our exchange
server... Frequently we see an entry 5504 and 7063 in the DNS log...
Since this is happening we also encounter problems with our internet
connection.
Has someone seen this before
Can someone help us out
Click to expand...

Event 7063 is forwarding to a non-recursive DNS server then it gives the IP
of the server is this IP in your list of forwarders?
5504 is an invalid packet which could also be an invalid character on a
machine usually a Win9x machine. If you have any Win9x machines you should
check for invalid characters in its name usually an underscore or even a
space MS DNS only supports 0-9, a-z, A-Z, . (dot), and - (hyphen) as part of
a domain name.

I have also found that you can get these errors if you have a machines
trying to register a name in a DNS zone that does not exist or is an illegal
DNS name or illegal domain name. When the registration request comes in it
is sent to a forwarder that cannot recurse the name.

The best way to keep these events from being generated is to enable DHCP
option 015 DNS domain name with the DNS name of your domain, and prevent
users from accessing the identification tab on Win9x machines after giving
the machine a legal name that DNS supports.
 
This will take some digging to track down. First, make sure that "secure cache against pollution" is enabled. Then enable DNS logging on the server. To do
this go to the properties of the DNS server from the DNS MMC. On the logging tab, enbable all the options. This will write all DNS lookup to the DNS.LOG file
in winnt\system32\dns. When the error occurs, check the DNS.LOG file at this time frame and see what query cause the event in question. Based on this info,
you can then take the necessary corrective action.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
Back
Top