DNS Errors in Event Log

[Sgriff]

Hi ,
our DNS server reports the folowing errors a number of times a day for
various IP addresses that are *not* in our Forwarders list...

any ideas?

thanks

Stephen


The DNS server is configured to forward to a non-recursive DNS server at
192.93.0.4.
DNS servers in forwarders list MUST be configured to process recursive
queries.
Either
1) fix the forwarder (192.93.0.4) to allow recursion
- connect to it with DNS Manager
- bring up server properties
- open "Advanced" tab
- uncheck "Disable Recursion"
- click OK
OR
2) remove this forwarder from this servers forwarders list
- DNS Manager
- bring up server properties
- open "Forwarders" tab
- remove (192.93.0.4) from list of forwarders
- click OK

 

[Larry Brasher]

Hello Stephen,

All this states is that your DNS is forwarding to a server that does not
process recursive queries. What is IP address 192.93.0.4 to? Is it your
ISP DNS?
Try this:
1.) You should be able to remove that forwarder and rely on the root hints
for recursive queries.
2.) Perform netdiag /testdns: <server name>
3.) Clear the DNS server's cache
4.) Set option: DNS Manager, server properties, Advanced tab, Secure cache
against pollution.

If the netdiag comes back clean, then there is nothing seriously wrong. If
you need to forward to a DNS server that performs recursive queries, then
use the root hints and/or choose another DNS server to forward to.




Shane Brasher
MCSE (2000,NT),MCSA, A+
Microsoft Platforms Support
Windows NT/2000 Networking

 

[Marina Roos]

How many nics in the server and did you put the server-IP in the DNS-field
(TCP/IP properties nic)?
In the DNS-server you should put the ISP-DNS-numbers in the forwarders.

Marina

 

[Brian Oakes [MSFT]]

I would read that error as one of the servers you forward to doesn't support
recursion. So an idea would be to switch a forwarder or 2, and then you can
narrow down which one it is, or you can so some nslookup queries to simulate
traffic and point nslookup to each of your forwards - one at a time - and
then see when the error comes back.
--

Best regards,
Brian Oakes, MCSE
Microsoft Product Support
Windows 2000 Server Networking Team

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.