slow IXFR updates

[Rainer Duffner]

Chris Buxton wrote:

> Sounds to me like a problem with DNS notify. Is the customer  

> correctly referencing your name server in an NS record in each of his  

> zones?

> 



I looked at this and it seemed OK.



> As a quick and dirty workaround, have the customer add the following  

> to his options statement:

> 

> 	also-notify { ip-addr; };

> 

> where "ip-addr" is the IP address of your name server. If he already  

> has an also-notify substatement, have him instead add your name  

> server to the existing list. Note that this can be overridden in each  

> zone statement, so if he has also-notify substatements in his zone  

> statements, he'll need to modify those instead.

> 



I didn't do this (yet), but when someone else told me how to enable 

logging (which I couldn't find any quick info about, when browsing 

through the admin-manual), I saw that the notifies came from a host that 

is not one of the two primaries.

At least BIND said so.



whois(1) still list the two "main" DNS-servers (where our 2ndary can do 

AXFRs from) as primaries, so I believe this is an error in the customers 

firewall-configuration. Some broken bi-directional NAT setting or so.



Unfortunately, we probably cannot bill all the lost time and nerves to 

them ;-)





Still, thanks for your help.







Best Regards

Rainer