app/models/orchestration/dns.rb
*- !domain.nil? and !domain.proxy.nil? and managed?
name.present? and ip.present? and !domain.nil? and !domain.proxy.nil? and
managed?*
Once applied DNS worked perfectly when booting a new ec2 instance:
*Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329: signer
"rndc-key" approved
Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329: updating
zone 'XXX.eu/IN': adding an RR at 'appserver2.XXX.eu' *
But i cant get the reverse DNS to work. In a effort to fixing it, thinking
the problem might be similar to the above, so i also reverted the following
lines, with no success
def reverse_dns?
!subnet.nil? and !subnet.dns_proxy.nil? and managed? and
capabilities.include?(:build)
name.present? and ip.present? and !subnet.nil? and subnet.dns? and
managed?*
in /var/log/messages one can see the DNS entry been created but not the
reverse dns
[root@ log]# tail -f /var/log/messages Jun 3 15:19:54 puppetmaster named[29677]: zone XXX.eu/IN: loaded serial
152
Jun 3 15:19:54 puppetmaster named[29677]: zone localhost.localdomain/IN:
loaded serial 0
Jun 3 15:19:54 puppetmaster named[29677]: zone localhost/IN: loaded serial
0
Jun 3 15:19:54 puppetmaster named[29677]: managed-keys-zone ./IN: loaded
serial 0
Jun 3 15:19:54 puppetmaster named[29677]: running
Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329: signer
"rndc-key" approved
Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329: updating
zone 'XXX.eu/IN': adding an RR at 'appserver6.XXX.eu' A
I can also create a reverse dns entry manually with no problem
root@ dynamic]# nsupdate -k /etc/rndc.key
*> server 127.0.0.1
Reverse DNS in Foreman is configured in a different place to forward
DNS, it's worth double checking this: under More, Provisioning, Subnets,
select your subnet and verify it has a DNS proxy set at the bottom of
the page.
···
On 03/06/13 17:00, Edgard Zelaya wrote:
> Hello,
>
> I have reverted the following changes according to this ticket:
>
> http://projects.theforeman.org/issues/2325
>
> app/models/orchestration/dns.rb
> *- !domain.nil? and !domain.proxy.nil? and managed?
> + name.present? and ip.present? and !domain.nil? and !domain.proxy.nil?
> and managed?*
>
>
> Once applied DNS worked perfectly when booting a new ec2 instance:
>
> *Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329:
> signer "rndc-key" approved
> Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329:
> updating zone 'XXX.eu/IN': adding an RR at 'appserver2.XXX.eu' *
>
> But i cant get the reverse DNS to work. In a effort to fixing it,
> thinking the problem might be similar to the above, so i also reverted
> the following lines, with no success
Thanks for responding so fast.
I had previously created a subnet in foreman using the same subnet, in
which i'm launching new ec2 instances(VPC), but unfortunately did not make
any change.
i has also applied the following changes in foreman that enable VPC support
for EC2. I not sure if that might be related to the problem?
···
On Monday, June 3, 2013 6:11:05 PM UTC+2, Dominic Cleal wrote:
>
> On 03/06/13 17:00, Edgard Zelaya wrote:
> > Hello,
> >
> > I have reverted the following changes according to this ticket:
> >
> > http://projects.theforeman.org/issues/2325
> >
> > app/models/orchestration/dns.rb
> > *- !domain.nil? and !domain.proxy.nil? and managed?
> > + name.present? and ip.present? and !domain.nil? and !domain.proxy.nil?
> > and managed?*
> >
> >
> > Once applied DNS worked perfectly when booting a new ec2 instance:
> >
> > *Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329:
> > signer "rndc-key" approved
> > Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329:
> > updating zone 'XXX.eu/IN': adding an RR at 'appserver2.XXX.eu' *
> >
> > But i cant get the reverse DNS to work. In a effort to fixing it,
> > thinking the problem might be similar to the above, so i also reverted
> > the following lines, with no success
>
> Reverse DNS in Foreman is configured in a different place to forward
> DNS, it's worth double checking this: under More, Provisioning, Subnets,
> select your subnet and verify it has a DNS proxy set at the bottom of
> the page.
>
> --
> Dominic Cleal
> Red Hat Engineering
>
It could also be related to your bind configurations. Do you see any errors
when you restart bind (such as "unable to write to 0.1.168.192.arpa blady
blah" etc?
···
On Mon, Jun 3, 2013 at 9:40 AM, Edgard Zelaya wrote:
Thanks for responding so fast.
I had previously created a subnet in foreman using the same subnet, in
which i’m launching new ec2 instances(VPC), but unfortunately did not make
any change.
i has also applied the following changes in foreman that enable VPC
support for EC2. I not sure if that might be related to the problem?
app/models/orchestration/dns.**rb
*- !domain.nil? and !domain.proxy.nil? and managed?
name.present? and ip.present? and !domain.nil? and !domain.proxy.nil?
and managed?*
Once applied DNS worked perfectly when booting a new ec2 instance:
*Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329:
signer “rndc-key” approved
Jun 3 15:21:19 puppetmaster named[29677]: client 127.0.0.1#35329:
updating zone ‘XXX.eu/IN’: adding an RR at ‘appserver2.XXX.eu’ *
But i cant get the reverse DNS to work. In a effort to fixing it,
thinking the problem might be similar to the above, so i also reverted
the following lines, with no success
Reverse DNS in Foreman is configured in a different place to forward
DNS, it’s worth double checking this: under More, Provisioning, Subnets,
select your subnet and verify it has a DNS proxy set at the bottom of
the page.
