named, update denied.

[Sten Carlsen]

Jonas Kvinge wrote:

> Yes, but why does 192.168.1.22 (which is a Windows 2000 DNS server) 
> want to update the zone on the master. And why does it do it only for 
> night-light.net and no other domains?
> 192.168.1.22 and 217.118.34.42 is the same computer to clarify that.

Ok, that is the question. W2k has a default setting in its tcpip 
properties that says "update DNS with my name and IP" something like 
that. That means it will every 10 seconds or so try to update the 
nameserver given to it to reflect its presence. If you don't want this 
to happen, you should manually turn this "feature" off in properties for 
the network port in question.

This is much more annoying when you have the nameserver on a dial-up 
connection (I had via an ISDN-router) it will call the nameserver to get 
that updated about every 10 seconds as long as it is on.

>
> At 20:52 07.07.2004, you wrote:
>
>> Jonas Kvinge wrote:
>>
>>> I get this error for some reason, I got several domains configured 
>>> like this
>>> one but only this one gives me errors. This is the log on the master.
>>>
>>> Jul  7 17:53:38 emptyglass named[145]: client 192.168.1.22#2289: update
>>> 'night-light.net/IN' denied
>>> Jul  7 18:03:20 emptyglass named[145]: client 217.118.34.42#1630: 
>>> update
>>> 'night-light.net/IN' denied
>>>
>>> zone "night-light.net" IN {
>>>        type master;
>>>        file "night-light.dns";
>>>        allow-update { none; };
>>>
>>                                                ^^^^^^^
>> Above line might be the reason you are not allowed to make an update 
>> to this zone?
>>
>>>        allow-transfer { 217.118.34.42; 192.168.1.22; 213.145.164.10; };
>>> };
>>>
>>> Jonas Kvinge
>>> http://night-light.net/
>>>
>>>
>>>
>>>
>>
>>
>> -- 
>> Best regards
>>
>> Sten Carlsen
>>
>> No improvements come from shouting:
>>
>>       "MALE BOVINE MANURE!!!"
>
>


-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"