[katello] DNS capsule

hi

I use the command

katello-installer --capsule-dns true --capsule-dns-forwarders

192.168.110.1 --capsule-dns-interface eth1 --capsule-dns-reverse
110.168.192.in-addr.arpa --capsule-dns-zone local.lab

but my capsule doesn't show as DNS-capable (dns.yml:

··· --- # DNS management :enabled: https # valid providers: # dnscmd (Microsoft Windows native implementation) # nsupdate # nsupdate_gss (for GSS-TSIG support) # virsh (simple implementation for libvirt) :use_provider: nsupdate # use this setting if you want to override default TTL setting (86400) :dns_ttl: 86400

while if I run the same on foreman ( s/capsule/foreman-proxy/g) I got the
expected DNS proxy (only difference. :dns_server: 127.0.0.1 under foreman,
tried to add the line to katello but no luck). What is wrong? Note that
named is running and the zones are created correctly, it’s just katello
capsule.

thanks

I see this in /var/log/foreman-proxy/proxy.log

E, [2015-10-13T12:00:09.377789 #19384] ERROR – : Couldn't enable plugin
dns: Unable to find dependency 'nsupdate' of 'dns'.

but nsupdate (the command) is installed. What am I missing again??

thanks for the replies

··· On Tuesday, October 13, 2015 at 3:22:15 PM UTC+2, Alessandro Vozza wrote: > > hi > > I use the command > > # katello-installer --capsule-dns true --capsule-dns-forwarders > 192.168.110.1 --capsule-dns-interface eth1 --capsule-dns-reverse > 110.168.192.in-addr.arpa --capsule-dns-zone local.lab > > but my capsule doesn't show as DNS-capable (dns.yml: > > --- > # DNS management > :enabled: https > # valid providers: > # dnscmd (Microsoft Windows native implementation) > # nsupdate > # nsupdate_gss (for GSS-TSIG support) > # virsh (simple implementation for libvirt) > :use_provider: nsupdate > # use this setting if you want to override default TTL setting (86400) > :dns_ttl: 86400 > > while if I run the same on foreman ( s/capsule/foreman-proxy/g) I got the > expected DNS proxy (only difference. :dns_server: 127.0.0.1 under foreman, > tried to add the line to katello but no luck). What is wrong? Note that > named is running and the zones are created correctly, it's just katello > capsule. > > thanks > >

> From: "Alessandro Vozza" <alessandro@ams0.org>
> To: "Foreman users" <foreman-users@googlegroups.com>
> Sent: Tuesday, October 13, 2015 9:19:28 AM
> Subject: [foreman-users] [katello] DNS capsule
>
> hi
>
> I use the command
>
> # katello-installer --capsule-dns true --capsule-dns-forwarders
> 192.168.110.1 --capsule-dns-interface eth1 --capsule-dns-reverse
> 110.168.192.in-addr.arpa --capsule-dns-zone local.lab
>
> but my capsule doesn't show as DNS-capable (dns.yml:

dns.yml looks fine, did you refresh the features on the smart proxy? (Infrastructure / Smart Proxies, and click the drop down to the far right)

··· ----- Original Message -----

DNS management

:enabled: https

valid providers:

dnscmd (Microsoft Windows native implementation)

nsupdate

nsupdate_gss (for GSS-TSIG support)

virsh (simple implementation for libvirt)

:use_provider: nsupdate

use this setting if you want to override default TTL setting (86400)

:dns_ttl: 86400

while if I run the same on foreman ( s/capsule/foreman-proxy/g) I got the
expected DNS proxy (only difference. :dns_server: 127.0.0.1 under foreman,
tried to add the line to katello but no luck). What is wrong? Note that
named is running and the zones are created correctly, it’s just katello
capsule.

thanks


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 foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

> From: "Stephen Benjamin" <stephen@redhat.com>
> To: foreman-users@googlegroups.com
> Sent: Tuesday, October 13, 2015 9:48:37 AM
> Subject: Re: [foreman-users] [katello] DNS capsule
>
>
>
> > From: "Alessandro Vozza" <alessandro@ams0.org>
> > To: "Foreman users" <foreman-users@googlegroups.com>
> > Sent: Tuesday, October 13, 2015 9:19:28 AM
> > Subject: [foreman-users] [katello] DNS capsule
> >
> > hi
> >
> > I use the command
> >
> > # katello-installer --capsule-dns true --capsule-dns-forwarders
> > 192.168.110.1 --capsule-dns-interface eth1 --capsule-dns-reverse
> > 110.168.192.in-addr.arpa --capsule-dns-zone local.lab
> >
> > but my capsule doesn't show as DNS-capable (dns.yml:
>
> dns.yml looks fine, did you refresh the features on the smart proxy?
> (Infrastructure / Smart Proxies, and click the drop down to the far right)

And maybe restart the foreman-proxy service before trying that.

··· ----- Original Message ----- > ----- Original Message -----

DNS management

:enabled: https

valid providers:

dnscmd (Microsoft Windows native implementation)

nsupdate

nsupdate_gss (for GSS-TSIG support)

virsh (simple implementation for libvirt)

:use_provider: nsupdate

use this setting if you want to override default TTL setting (86400)

:dns_ttl: 86400

while if I run the same on foreman ( s/capsule/foreman-proxy/g) I got the
expected DNS proxy (only difference. :dns_server: 127.0.0.1 under foreman,
tried to add the line to katello but no luck). What is wrong? Note that
named is running and the zones are created correctly, it’s just katello
capsule.

thanks


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 foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Looking at the example config in GitHub, you've got the wrong name for
the provider - it should be dns_nsupdate.

Hope it helps,
Greg

Thanks, that fixed the issue. But, I haven't specified the provider during
installation, it got the default :

--capsule-dns-provider        DNS provider (default: &quot;nsupdate&quot;)

is this a regression? Worth filing a bug?

thanks again, you made my day!

··· On Tuesday, October 13, 2015 at 4:48:24 PM UTC+2, Greg Sutcliffe wrote: > > Looking at the example config in GitHub, you've got the wrong name for > the provider - it should be dns_nsupdate. > > > https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns.yml.example#L10 > > Hope it helps, > Greg >

http://projects.theforeman.org/issues/12157

··· On Tuesday, October 13, 2015 at 5:47:35 PM UTC+2, stephen wrote: > > Yes please, that'd be much appreciated. > > > ----- Original Message ----- > > From: "Alessandro Vozza" <aless...@ams0.org > > > To: "Foreman users" <forema...@googlegroups.com > > > Sent: Tuesday, October 13, 2015 11:07:03 AM > > Subject: Re: [foreman-users] Re: [katello] DNS capsule > > > > Thanks, that fixed the issue. But, I haven't specified the provider > during > > installation, it got the default : > > > > --capsule-dns-provider DNS provider (default: "nsupdate") > > > > is this a regression? Worth filing a bug? > > > > thanks again, you made my day! > > > > On Tuesday, October 13, 2015 at 4:48:24 PM UTC+2, Greg Sutcliffe wrote: > > > > > > Looking at the example config in GitHub, you've got the wrong name for > > > the provider - it should be dns_nsupdate. > > > > > > > > > > https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns.yml.example#L10 > > > > > > Hope it helps, > > > Greg > > > > > > > -- > > 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 foreman-user...@googlegroups.com . > > To post to this group, send email to forema...@googlegroups.com > . > > Visit this group at http://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > > >

Yes please, that'd be much appreciated.

··· ----- Original Message ----- > From: "Alessandro Vozza" > To: "Foreman users" > Sent: Tuesday, October 13, 2015 11:07:03 AM > Subject: Re: [foreman-users] Re: [katello] DNS capsule > > Thanks, that fixed the issue. But, I haven't specified the provider during > installation, it got the default : > > --capsule-dns-provider DNS provider (default: "nsupdate") > > is this a regression? Worth filing a bug? > > thanks again, you made my day! > > On Tuesday, October 13, 2015 at 4:48:24 PM UTC+2, Greg Sutcliffe wrote: > > > > Looking at the example config in GitHub, you've got the wrong name for > > the provider - it should be dns_nsupdate. > > > > > > https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns.yml.example#L10 > > > > Hope it helps, > > Greg > > > > -- > 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 foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. >

While I could deploy the DNS proxy, actual deployment of discovered hosts
fail (proxy.log):

10.128.0.57 - - [15/Oct/2015 19:16:53] "POST /dns/ HTTP/1.1" 400 50 0.0016
10.128.0.57 - - [15/Oct/2015 19:16:54] "DELETE
/dhcp/10.128.0.0/74:e6:e2:86:4e:88 HTTP/1.1" 200 - 0.2025
10.128.0.57 - - [15/Oct/2015 19:19:02] "GET /tftp/serverName HTTP/1.1" 200
28 0.0024
10.128.0.57 - - [15/Oct/2015 19:19:02] "GET /dhcp/10.128.0.0/10.128.1.9
HTTP/1.1" 200 186 0.1856
10.128.0.57 - - [15/Oct/2015 19:19:02] "POST /dhcp/10.128.0.0 HTTP/1.1" 200

  • 0.2232
    E, [2015-10-15T19:19:03.009106 #2902] ERROR – : Unrecognized or missing
    DNS provider: dns_nsupdate

Hosts then reboots into the discovery image again. I would suggest a patch
if I was smart enough :frowning:

thanks

··· On Tuesday, October 13, 2015 at 8:21:36 PM UTC+2, Alessandro Vozza wrote: > > http://projects.theforeman.org/issues/12157 > > On Tuesday, October 13, 2015 at 5:47:35 PM UTC+2, stephen wrote: >> >> Yes please, that'd be much appreciated. >> >> >> ----- Original Message ----- >> > From: "Alessandro Vozza" >> > To: "Foreman users" >> > Sent: Tuesday, October 13, 2015 11:07:03 AM >> > Subject: Re: [foreman-users] Re: [katello] DNS capsule >> > >> > Thanks, that fixed the issue. But, I haven't specified the provider >> during >> > installation, it got the default : >> > >> > --capsule-dns-provider DNS provider (default: "nsupdate") >> > >> > is this a regression? Worth filing a bug? >> > >> > thanks again, you made my day! >> > >> > On Tuesday, October 13, 2015 at 4:48:24 PM UTC+2, Greg Sutcliffe wrote: >> > > >> > > Looking at the example config in GitHub, you've got the wrong name >> for >> > > the provider - it should be dns_nsupdate. >> > > >> > > >> > > >> https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns.yml.example#L10 >> > > >> > > Hope it helps, >> > > Greg >> > > >> > >> > -- >> > 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 foreman-user...@googlegroups.com. >> > To post to this group, send email to forema...@googlegroups.com. >> > Visit this group at http://groups.google.com/group/foreman-users. >> > For more options, visit https://groups.google.com/d/optout. >> > >> >

Also, changing from :dns_provider: dns_nsupdate to :dns_provider: nsupdate
in /etc/foreman-proxy/settings.d/dns.yml and restarting foreman-proxy now
gives me this:

10.128.0.57 - - [15/Oct/2015 19:29:42] "POST /dhcp/10.128.0.0 HTTP/1.1" 200

  • 0.2717
    E, [2015-10-15T19:29:42.854721 #8137] ERROR – : Update errors: Answer:

;; ->>HEADER<<- opcode: UPDATE, status: REFUSED, id: 28156

;; flags: qr ra; ZONE: 1, PREREQ: 0, UPDATE: 0, ADDITIONAL: 1

;; ZONE SECTION:

;10.in-addr.arpa. IN SOA

;; TSIG PSEUDOSECTION:

rndc-key. 0 ANY TSIG hmac-md5.sig-alg.reg.int. 1444937382 300 16
bxCxScg9/PZeJyDU+9PBHA== 28156 NOERROR 0

10.128.0.57 - - [15/Oct/2015 19:29:42] "POST /dns/ HTTP/1.1" 400 329 0.0782

Again, no clues…

thanks for any help

··· On Thursday, October 15, 2015 at 9:21:43 PM UTC+2, Alessandro Vozza wrote: > > While I could deploy the DNS proxy, actual deployment of discovered hosts > fail (proxy.log): > > 10.128.0.57 - - [15/Oct/2015 19:16:53] "POST /dns/ HTTP/1.1" 400 50 0.0016 > 10.128.0.57 - - [15/Oct/2015 19:16:54] "DELETE /dhcp/ > 10.128.0.0/74:e6:e2:86:4e:88 HTTP/1.1" 200 - 0.2025 > 10.128.0.57 - - [15/Oct/2015 19:19:02] "GET /tftp/serverName HTTP/1.1" 200 > 28 0.0024 > 10.128.0.57 - - [15/Oct/2015 19:19:02] "GET /dhcp/10.128.0.0/10.128.1.9 > HTTP/1.1" 200 186 0.1856 > 10.128.0.57 - - [15/Oct/2015 19:19:02] "POST /dhcp/10.128.0.0 HTTP/1.1" > 200 - 0.2232 > E, [2015-10-15T19:19:03.009106 #2902] ERROR -- : Unrecognized or missing > DNS provider: dns_nsupdate > > Hosts then reboots into the discovery image again. I would suggest a patch > if I was smart enough :( > > thanks > > > On Tuesday, October 13, 2015 at 8:21:36 PM UTC+2, Alessandro Vozza wrote: >> >> http://projects.theforeman.org/issues/12157 >> >> On Tuesday, October 13, 2015 at 5:47:35 PM UTC+2, stephen wrote: >>> >>> Yes please, that'd be much appreciated. >>> >>> >>> ----- Original Message ----- >>> > From: "Alessandro Vozza" >>> > To: "Foreman users" >>> > Sent: Tuesday, October 13, 2015 11:07:03 AM >>> > Subject: Re: [foreman-users] Re: [katello] DNS capsule >>> > >>> > Thanks, that fixed the issue. But, I haven't specified the provider >>> during >>> > installation, it got the default : >>> > >>> > --capsule-dns-provider DNS provider (default: "nsupdate") >>> > >>> > is this a regression? Worth filing a bug? >>> > >>> > thanks again, you made my day! >>> > >>> > On Tuesday, October 13, 2015 at 4:48:24 PM UTC+2, Greg Sutcliffe >>> wrote: >>> > > >>> > > Looking at the example config in GitHub, you've got the wrong name >>> for >>> > > the provider - it should be dns_nsupdate. >>> > > >>> > > >>> > > >>> https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns.yml.example#L10 >>> > > >>> > > Hope it helps, >>> > > Greg >>> > > >>> > >>> > -- >>> > 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 foreman-user...@googlegroups.com. >>> > To post to this group, send email to forema...@googlegroups.com. >>> > Visit this group at http://groups.google.com/group/foreman-users. >>> > For more options, visit https://groups.google.com/d/optout. >>> > >>> >>

More details: the proxy can update the normal zone but not the reverse zone:

[11:37:17] avozza: echo -e "server 10.128.0.57\nupdate add
testdeploy.cloud.net 3600 IN A 10.128.1.100\nsend\n" | nsupdate -k
/etc/rndc.key

[11:37:34] avozza: cho -e "server 127.0.0.1\nupdate add
9.1.128.10.in-addr.arpa. 86400 IN PTR mac74e6e2864e88.cloud.net\nsend\n" |
nsupdate -L 1 -k /etc/rndc.key

[11:37:38] avozza: update failed: REFUSED

but the zones.conf seems fine:

zone "0.128.10.in-addr.arpa" {

type master;

file &quot;/var/named/dynamic/db.0.128.10.in-addr.arpa&quot;;

update-policy {

        grant rndc-key zonesub ANY;

};

};

zone "cloud.net" {

type master;

file &quot;/var/named/dynamic/db.cloud.net&quot;;

update-policy {

        grant rndc-key zonesub ANY;

};

};

Any help appreciated

··· On Thursday, October 15, 2015 at 9:32:15 PM UTC+2, Alessandro Vozza wrote: > > Also, changing from :dns_provider: dns_nsupdate to :dns_provider: nsupdate > in /etc/foreman-proxy/settings.d/dns.yml and restarting foreman-proxy now > gives me this: > > 10.128.0.57 - - [15/Oct/2015 19:29:42] "POST /dhcp/10.128.0.0 HTTP/1.1" > 200 - 0.2717 > E, [2015-10-15T19:29:42.854721 #8137] ERROR -- : Update errors: Answer: > > ;; ->>HEADER< > ;; flags: qr ra; ZONE: 1, PREREQ: 0, UPDATE: 0, ADDITIONAL: 1 > > ;; ZONE SECTION: > > ;10.in-addr.arpa. IN SOA > > > > ;; TSIG PSEUDOSECTION: > > rndc-key. 0 ANY TSIG hmac-md5.sig-alg.reg.int. 1444937382 300 16 > bxCxScg9/PZeJyDU+9PBHA== 28156 NOERROR 0 > > > > 10.128.0.57 - - [15/Oct/2015 19:29:42] "POST /dns/ HTTP/1.1" 400 329 > 0.0782 > > Again, no clues... > > thanks for any help > > On Thursday, October 15, 2015 at 9:21:43 PM UTC+2, Alessandro Vozza wrote: >> >> While I could deploy the DNS proxy, actual deployment of discovered hosts >> fail (proxy.log): >> >> 10.128.0.57 - - [15/Oct/2015 19:16:53] "POST /dns/ HTTP/1.1" 400 50 0.0016 >> 10.128.0.57 - - [15/Oct/2015 19:16:54] "DELETE /dhcp/ >> 10.128.0.0/74:e6:e2:86:4e:88 HTTP/1.1" 200 - 0.2025 >> 10.128.0.57 - - [15/Oct/2015 19:19:02] "GET /tftp/serverName HTTP/1.1" >> 200 28 0.0024 >> 10.128.0.57 - - [15/Oct/2015 19:19:02] "GET /dhcp/10.128.0.0/10.128.1.9 >> HTTP/1.1" 200 186 0.1856 >> 10.128.0.57 - - [15/Oct/2015 19:19:02] "POST /dhcp/10.128.0.0 HTTP/1.1" >> 200 - 0.2232 >> E, [2015-10-15T19:19:03.009106 #2902] ERROR -- : Unrecognized or missing >> DNS provider: dns_nsupdate >> >> Hosts then reboots into the discovery image again. I would suggest a >> patch if I was smart enough :( >> >> thanks >> >> >> On Tuesday, October 13, 2015 at 8:21:36 PM UTC+2, Alessandro Vozza wrote: >>> >>> http://projects.theforeman.org/issues/12157 >>> >>> On Tuesday, October 13, 2015 at 5:47:35 PM UTC+2, stephen wrote: >>>> >>>> Yes please, that'd be much appreciated. >>>> >>>> >>>> ----- Original Message ----- >>>> > From: "Alessandro Vozza" >>>> > To: "Foreman users" >>>> > Sent: Tuesday, October 13, 2015 11:07:03 AM >>>> > Subject: Re: [foreman-users] Re: [katello] DNS capsule >>>> > >>>> > Thanks, that fixed the issue. But, I haven't specified the provider >>>> during >>>> > installation, it got the default : >>>> > >>>> > --capsule-dns-provider DNS provider (default: "nsupdate") >>>> > >>>> > is this a regression? Worth filing a bug? >>>> > >>>> > thanks again, you made my day! >>>> > >>>> > On Tuesday, October 13, 2015 at 4:48:24 PM UTC+2, Greg Sutcliffe >>>> wrote: >>>> > > >>>> > > Looking at the example config in GitHub, you've got the wrong name >>>> for >>>> > > the provider - it should be dns_nsupdate. >>>> > > >>>> > > >>>> > > >>>> https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns.yml.example#L10 >>>> > > >>>> > > Hope it helps, >>>> > > Greg >>>> > > >>>> > >>>> > -- >>>> > 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 foreman-user...@googlegroups.com. >>>> > To post to this group, send email to forema...@googlegroups.com. >>>> > Visit this group at http://groups.google.com/group/foreman-users. >>>> > For more options, visit https://groups.google.com/d/optout. >>>> > >>>> >>>

Sorry for the flood or replies :slight_smile:

I found out the problem: I have a /23 network for provisioning, but somehow
named refuses to update the second half of the CIDR (10.128.0.x updates are
working fine). Why is that? Any hint/link to where to find more information
on how to setup a /23 provisioning network?

cheers

··· On Friday, October 16, 2015 at 11:40:47 AM UTC+2, Alessandro Vozza wrote: > > More details: the proxy can update the normal zone but not the reverse > zone: > > [11:37:17] avozza: echo -e "server 10.128.0.57\nupdate add > testdeploy.cloud.net 3600 IN A 10.128.1.100\nsend\n" | nsupdate -k > /etc/rndc.key > > [11:37:34] avozza: cho -e "server 127.0.0.1\nupdate add > 9.1.128.10.in-addr.arpa. 86400 IN PTR mac74e6e2864e88.cloud.net\nsend\n" > > nsupdate -L 1 -k /etc/rndc.key > > [11:37:38] avozza: update failed: REFUSED > > > but the zones.conf seems fine: > > > zone "0.128.10.in-addr.arpa" { > > type master; > > file "/var/named/dynamic/db.0.128.10.in-addr.arpa"; > > update-policy { > > grant rndc-key zonesub ANY; > > }; > > }; > > zone "cloud.net" { > > type master; > > file "/var/named/dynamic/db.cloud.net"; > > update-policy { > > grant rndc-key zonesub ANY; > > }; > > }; > > Any help appreciated > > > On Thursday, October 15, 2015 at 9:32:15 PM UTC+2, Alessandro Vozza wrote: >> >> Also, changing from :dns_provider: dns_nsupdate to :dns_provider: >> nsupdate in /etc/foreman-proxy/settings.d/dns.yml and restarting >> foreman-proxy now gives me this: >> >> 10.128.0.57 - - [15/Oct/2015 19:29:42] "POST /dhcp/10.128.0.0 HTTP/1.1" >> 200 - 0.2717 >> E, [2015-10-15T19:29:42.854721 #8137] ERROR -- : Update errors: Answer: >> >> ;; ->>HEADER<> >> ;; flags: qr ra; ZONE: 1, PREREQ: 0, UPDATE: 0, ADDITIONAL: 1 >> >> ;; ZONE SECTION: >> >> ;10.in-addr.arpa. IN SOA >> >> >> >> ;; TSIG PSEUDOSECTION: >> >> rndc-key. 0 ANY TSIG hmac-md5.sig-alg.reg.int. 1444937382 300 16 >> bxCxScg9/PZeJyDU+9PBHA== 28156 NOERROR 0 >> >> >> >> 10.128.0.57 - - [15/Oct/2015 19:29:42] "POST /dns/ HTTP/1.1" 400 329 >> 0.0782 >> >> Again, no clues... >> >> thanks for any help >> >> On Thursday, October 15, 2015 at 9:21:43 PM UTC+2, Alessandro Vozza wrote: >>> >>> While I could deploy the DNS proxy, actual deployment of discovered >>> hosts fail (proxy.log): >>> >>> 10.128.0.57 - - [15/Oct/2015 19:16:53] "POST /dns/ HTTP/1.1" 400 50 >>> 0.0016 >>> 10.128.0.57 - - [15/Oct/2015 19:16:54] "DELETE /dhcp/ >>> 10.128.0.0/74:e6:e2:86:4e:88 HTTP/1.1" 200 - 0.2025 >>> 10.128.0.57 - - [15/Oct/2015 19:19:02] "GET /tftp/serverName HTTP/1.1" >>> 200 28 0.0024 >>> 10.128.0.57 - - [15/Oct/2015 19:19:02] "GET /dhcp/10.128.0.0/10.128.1.9 >>> HTTP/1.1" 200 186 0.1856 >>> 10.128.0.57 - - [15/Oct/2015 19:19:02] "POST /dhcp/10.128.0.0 HTTP/1.1" >>> 200 - 0.2232 >>> E, [2015-10-15T19:19:03.009106 #2902] ERROR -- : Unrecognized or missing >>> DNS provider: dns_nsupdate >>> >>> Hosts then reboots into the discovery image again. I would suggest a >>> patch if I was smart enough :( >>> >>> thanks >>> >>> >>> On Tuesday, October 13, 2015 at 8:21:36 PM UTC+2, Alessandro Vozza wrote: >>>> >>>> http://projects.theforeman.org/issues/12157 >>>> >>>> On Tuesday, October 13, 2015 at 5:47:35 PM UTC+2, stephen wrote: >>>>> >>>>> Yes please, that'd be much appreciated. >>>>> >>>>> >>>>> ----- Original Message ----- >>>>> > From: "Alessandro Vozza" >>>>> > To: "Foreman users" >>>>> > Sent: Tuesday, October 13, 2015 11:07:03 AM >>>>> > Subject: Re: [foreman-users] Re: [katello] DNS capsule >>>>> > >>>>> > Thanks, that fixed the issue. But, I haven't specified the provider >>>>> during >>>>> > installation, it got the default : >>>>> > >>>>> > --capsule-dns-provider DNS provider (default: "nsupdate") >>>>> > >>>>> > is this a regression? Worth filing a bug? >>>>> > >>>>> > thanks again, you made my day! >>>>> > >>>>> > On Tuesday, October 13, 2015 at 4:48:24 PM UTC+2, Greg Sutcliffe >>>>> wrote: >>>>> > > >>>>> > > Looking at the example config in GitHub, you've got the wrong name >>>>> for >>>>> > > the provider - it should be dns_nsupdate. >>>>> > > >>>>> > > >>>>> > > >>>>> https://github.com/theforeman/smart-proxy/blob/develop/config/settings.d/dns.yml.example#L10 >>>>> > > >>>>> > > Hope it helps, >>>>> > > Greg >>>>> > > >>>>> > >>>>> > -- >>>>> > 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 foreman-user...@googlegroups.com. >>>>> > To post to this group, send email to forema...@googlegroups.com. >>>>> > Visit this group at http://groups.google.com/group/foreman-users. >>>>> > For more options, visit https://groups.google.com/d/optout. >>>>> > >>>>> >>>>

I see proxy logs but not named logs - i assume you've already looked,
but is there anything useful in the named logs as to why it's refusing
the update?

Greg

··· On 16 October 2015 at 11:20, Alessandro Vozza wrote: > Sorry for the flood or replies :) > > I found out the problem: I have a /23 network for provisioning, but somehow > named refuses to update the second half of the CIDR (10.128.0.x updates are > working fine). Why is that? Any hint/link to where to find more information > on how to setup a /23 provisioning network? > > cheers