On 26/01/17 00:38, Alan McAlexander wrote: > I've been having a heck of a couple days trying to stand up Foreman 1.14 > on Ubuntu 14.04. I have everything setup like another environment, but > for whatever reason, I keep getting crazy errors. I've checked out the > rndc key, to no avail as everything matches up. But yet I keep getting > these errors.
Can you show the BIND configuration? [..] > I, [2017-01-26T00:31:22.325780 ] INFO -- : 10.x.x.2 - - [26/Jan/2017 > 00:31:22] "POST /dhcp/10.16.37.0 HTTP/1.1" 200 - 0.0169 > > E, [2017-01-26T00:31:22.463041 ] ERROR -- : Update errors: Answer: > > ;; ->>HEADER<<- opcode: UPDATE, status: REFUSED, id: 49597 REFUSED indicates the BIND server is not permitting the update. What zone configuration does it have? > ;; flags: qr ra; ZONE: 1, PREREQ: 0, UPDATE: 0, ADDITIONAL: 1 > > ;; ZONE SECTION: > > ;10.in-addr.arpa. IN SOA This indicates the zone is 10.in-addr.arpa, check that's what's configured in BIND. If you have a more specific zone, then change the subnet configuration (prefix length/netmask) in Foreman to match. -- Dominic Cleal [email protected] -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
