enom-api's Introduction

eNom API Client

Provides a Ruby client for the eNom Reseller API.

Installation

Add this line to your application's Gemfile:

gem 'enom-api'

And then execute:

$ bundle

Or install it yourself as:

$ gem install enom-api

Usage

require 'enom-api'
client = EnomAPI::Client.new('username', 'password')
testclient = EnomAPI::Client.new('username', 'password', 'resellertest.enom.com')

Contributing

Fork it
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Add some feature')
Push to the branch (git push origin my-new-feature)
Create new Pull Request

Copyright

enom-api's People

Contributors

Watchers

enom-api's Issues

Implement Contacts method for changing domain contact info

The eNom API "Contacts" method provides the ability to make domain registrant changes. The whole contact needs to be sent, doesn't look like it will merge new attributes with old.

XML Parsing issues

Issues parsing XML responses from eNom API are causing problems using the gem. Demolisher should be re-written to use Nokogiri

CheckNSStatus can return more than one IP address

If a nameserver has one more than one IP address, say an IPv4 and IPv6, then the XML which is returned isn't parsed correctly.

The documentation shows

<CheckNsStatus>
  <name>ns2.budip.com</name>
  <ipaddress>198.51.100.53</ipaddress>
</CheckNsStatus>

when more than one IP address is returned the format is as follows

<CheckNsStatus>
  <name>ns2.budip.com</name>
  <ipaddress>
    <ipaddress>198.51.100.53</ipaddress>
    <ipaddress>2001:db8::53</ipaddress>
  </ipaddress>
</CheckNsStatus>

in this case a call to EnomAPI::Client#check_ns_status will return a Demolisher::Node in the :ipaddress key instead of the IP address which it would in the first case.

Recommend Projects