Hm Did some tests. It seems that Utm9 Dhcpd is updating my other Bind. Even if remove my request routing. Does it not update its local bind? Timeouts are appearing in logs when i use a clientdomain thats not setup in local bind. My only zhought is that this zone is not known locally.
Christian, it's difficult to follow your description. Could you restate the problem replacing the demonstative pronouns with actual items/locations? [:)]
Try to do so. I have another DNS (bind) in place which is the master for my internal zones. So utm redirects the query for these zones to the other bind. That runs fine. What i recognized was after enabling dhcp on utm is that the dhcp updates the zones on the other bind. Second what i recognized is that the dhcp tries that too for all domains i configured in dhcp even if the are not setup there. I would expect that the dhcp would update its own Dns with zones that are not forwarded.
I guess I'm confused about what dhcpd should update. I don't think it's updating your other DNS server, and I don't think that the UTM9 DNS server is updating it either.
you are confusing all here anyway UTM will not updete your localzone. UTM will ask directly you internal dns server that you configured in "Request Routing". I will recommend to not use a internal server but to look carefully on DHCP options in UTM. Or even better to wait the last UTM 9.1 In these release UTM will create dns-names for each host
2013:02:28-21:13:39 UTM9 dhcpd: if whity8.kueppersnetz.local IN A rrset doesn't exist add whity8.kueppersnetz.local 43200 IN A 192.168.10.16: RRset already exists.
28-Feb-2013 21:13:33.914 update: info: client 192.168.10.1#44163: updating zone 'kueppersnetz.local/IN': update unsuccessful: whity8.kueppersnetz.local/A: 'rrset does not exist' prerequisite not satisfied (YXRRSET) -------------- client 192.168.10.1 ist the UTM9. in my opinion it updates the DNS if Request Routing matches the domain given in dhcp.
