DNS record config with rubber 1.1.4

30 views
Skip to first unread message

Brandon Casci

unread,
Nov 3, 2009, 3:52:19 PM11/3/09
to rubbe...@googlegroups.com
I'm using Nettica as a DNS provider. What's changed between rubber now and pre 1.x rubber? There is a barf when rubber tries to speak with Nettica. I can see it's an SSL/certificate problem but it was working with older versions of rubber.

 * executing `rubber:setup_dns_aliases'
cacerts: /usr/lib/ruby/gems/1.8/gems/httpclient-2.1.4/lib/httpclient/cacert.p7s loading failed
at depth 0 - 20: unable to get local issuer certificate
/usr/lib/ruby/gems/1.8/gems/httpclient-2.1.4/lib/httpclient/session.rb:247:in `connect': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (OpenSSL::SSL::SSLError)


--
=========================================
I'm having a bout of spondylosis, so I can't hammer away at the keyboard too long. Please don't mistake short e-mails for rude e-mails..
=========================================

Matthew Conway

unread,
Nov 3, 2009, 3:54:36 PM11/3/09
to rubbe...@googlegroups.com
Try updating the httpclient gem

Brandon Casci

unread,
Nov 3, 2009, 4:08:22 PM11/3/09
to rubbe...@googlegroups.com
Yup, I updated that one and nettica. A little better now. The dns calls out to nettica on a rubber:destroy work, but on a create, the nettica call comes back with an HTTP 450 :/

Brandon Casci

unread,
Nov 3, 2009, 4:13:50 PM11/3/09
to rubbe...@googlegroups.com
From Wikipedia:

450 Blocked by Windows Parental Controls - A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.
I'm on Ubuntu though... heh heh. I'll contact nettica.

Matthew Conway

unread,
Nov 3, 2009, 4:17:52 PM11/3/09
to rubbe...@googlegroups.com
Weird, never seen that one - you can run rubber:setup_dns_aliases to
just do the dns part while testing. Was it trying to create an
entirely new record, or update an existing one? Does the domain
itself exist in nettica?

Brandon Casci

unread,
Nov 3, 2009, 4:20:03 PM11/3/09
to rubbe...@googlegroups.com
The domain does exist in nettica. I'm assuming it was trying to create an A record for new instance's alias.

Matthew Conway

unread,
Nov 3, 2009, 4:30:57 PM11/3/09
to rubbe...@googlegroups.com
Yes, if the domain doesn't exist, rubber _should_ try and create the
domain record before adding the A record for the new instance. Since
it exists for you, that isn't where the failure is happening.
You can try opening up a console and creating the record manually to
see if it is the dns lib, or the rubber use of it thats broken:

(RUBBER_CONFIG is set if you config.gem 'rubber')

./script/console
>> n = Rubber::Dns::get_provider('nettica', RUBBER_CONFIG); nil
=> nil
>> n.provider_env
=> {"user"=>"myuser, "password"=>"mypassword"}
>> n.create_host_record(:host => 'yourhost', :domain =>
'yourdomain.com', :type => 'A', :data => '1.2.3.4')


Matt

Brian Del Vecchio

unread,
Nov 3, 2009, 4:48:45 PM11/3/09
to rubbe...@googlegroups.com
I use Elastic IPs instead of dynamic DNS.  They're free while the addresses are attached to a running instance; a penny an hour to reserve them when not in use.

just set
  use_static_ip: true

and rubber:create will allocate static addresses for newly created instances.
Then copy them from the console (or /etc/hosts) to your DNS.

Brian Del Vecchio  |  b...@hybernaut.com  |  @hybernaut
Reply all
Reply to author
Forward
0 new messages