Foreman-managed DNS Issue

Andy_Edmonds · May 30, 2012, 12:50pm

Hi all,

I have an issue with dynamic DNS updates on Foreman 4.2. When I create a
host, the creation of DNS entries fail. See the various logs here:
http://pastebin.com/GnNnW5LK).

I've created DNS entries manually via command line and it works.

Any ideas?

Andy

Andy_Edmonds · May 30, 2012, 12:59pm

Ooops - Foreman version 0.4.2

···

On Wednesday, 30 May 2012 14:50:32 UTC+2, Andy Edmonds wrote: > > Hi all, > > I have an issue with dynamic DNS updates on Foreman 4.2. When I create a > host, the creation of DNS entries fail. See the various logs here: > http://pastebin.com/GnNnW5LK). > > I've created DNS entries manually via command line and it works. > > Any ideas? > > Andy >

Andy_Edmonds · May 30, 2012, 1:45pm

Ok this issue is caused by foreman attempting to authenticate using the
default /etc/bind/rndc.key. Foreman does not have read permissions by
default to the key and so all dynamic dns update operations will fail until
foreman is given the permissions.

Andy

···

On Wednesday, 30 May 2012 14:59:13 UTC+2, Andy Edmonds wrote: > > Ooops - Foreman version 0.4.2 :-) > > On Wednesday, 30 May 2012 14:50:32 UTC+2, Andy Edmonds wrote: >> >> Hi all, >> >> I have an issue with dynamic DNS updates on Foreman 4.2. When I create a >> host, the creation of DNS entries fail. See the various logs here: >> http://pastebin.com/GnNnW5LK). >> >> I've created DNS entries manually via command line and it works. >> >> Any ideas? >> >> Andy >> >

Andreas_Ntaflos · May 30, 2012, 1:49pm

Make sure you add the foreman-proxy user to the appropriate group so it
can read the key. In Ubuntu this is done with

adduser foreman-proxy bind

HTH Andreas

···

On 30/05/12 15:45, Andy Edmonds wrote: > Ok this issue is caused by foreman attempting to authenticate using the > default /etc/bind/rndc.key. Foreman does not have read permissions by > default to the key and so all dynamic dns update operations will fail > until foreman is given the permissions.

Andy_Edmonds1 · May 30, 2012, 3:26pm

Thanks Andreas!

Andy
andy.edmonds.be

···

On Wed, May 30, 2012 at 3:49 PM, Andreas Ntaflos wrote:

On 30/05/12 15:45, Andy Edmonds wrote:

Ok this issue is caused by foreman attempting to authenticate using the
default /etc/bind/rndc.key. Foreman does not have read permissions by
default to the key and so all dynamic dns update operations will fail
until foreman is given the permissions.

Make sure you add the foreman-proxy user to the appropriate group so it
can read the key. In Ubuntu this is done with

adduser foreman-proxy bind

HTH Andreas