BIND Errors

[Danny Mayer]

ken at mtnhosting.com wrote:
> Hello All,
> 
> I use BIND on my machine and have been using it for a while now without any problems. It is a very good software and I would like to commend you on this good product.
> 
> Recently, I was doing a cleanup and audit of my system and found several error entries in my event viewer logs. The error logged for each instance is as follows:
> 
> Event Type:	Error
> Event Source:	named
> Event Category:	None
> Event ID:	1
> Date:		04/08/2007
> Time:		20:09:37
> User:		N/A
> Computer:	SERVER1
> Description:
> The description for Event ID ( 1 ) in Source ( named ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use
> the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
client 69.246.113.49#3736: update 'elumelu.com/IN' denied.
> 

First copy the bindevt.dll to your system32 directory. It's being copied
to the wrong place by the installer.

Second, you need to look at your configuration to find out why
69.246.113.49 is being denied update access. If this is a Windows client
it's probably because you are not allowing it to update that zone.
That's common with Windows clients trying to update zones. They do this
at least every 24 hours even if they have not changed addresses.

> Am unsure as to the cause of this error but as you can see from the
error, it does say the event source is "named" which is the BIND user
account. I have researched the internet to see if I can find a solution
but have not been successful at that hence am contacting you to see if
you can give me some input or support with this issue.
> 

Microsoft decided that it would be a good idea for all Windows clients
to update the records of the zone that they are in. This is in spite of
the fact that they use DHCP to get their addresses in the first place
and the DHCP server could be the one doing the updating if necessary.
It's a far better strategy.

> By the way, the domain name shown in the error is one of the domains
> I
have set-up on my server so it is not alien or unknown to me. I am
hoping for some god feedback from you as these errors keep re-occurring
and I have to keep clearing up the logs entries. In each event, the
error reported is the same.
> 

Yes, see above.

Danny