Cannot assign a subdomain

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
cli, networking

Research direction

Start by reproducing ey-dns assign todo.zerotorails.com -a drnic -e todo_production against a newly created zerotorails.com zone, then compare it with the successful zone assignment shown in the issue. Done means a subdomain can be assigned as the first record and the command creates the expected DNS record instead of asking for the subdomain to be registered.

Written by the indexing model from the issue text.

Description

The zone zerotorails.com is new had had no records. I attempted to assign the subdomain todo.zerotorails.com as the first record; but it failed:

$ ey-dns assign todo.zerotorails.com -a drnic -e todo_production
Fetching AppCloud environment information...
AppCloud environment drnic/todo_production has IP 184.73.167.68

Searching for todo.zerotorails.com amongst your DNS providers...
ERROR: Please register domain todo.zerotorails.com with your DNS provider

Creating the domain matching the zone worked:

$ ey-dns assign zerotorails.com -a drnic -e todo_production
Fetching AppCloud environment information...
AppCloud environment drnic/todo_production has IP 184.73.167.68

Searching for zerotorails.com amongst your DNS providers...
Found zerotorails.com in DNSimple account

Assigning zerotorails.com --> 184.73.167.68 (drnic/todo_production)
Created A record for zerotorails.com
Assigning www.zerotorails.com --> 184.73.167.68 (drnic/todo_production)
Created A record for www.zerotorails.com
Complete!
Dominant language
Ruby
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from engineyard/engineyard-dns

All issues in engineyard/engineyard-dns

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.