Question 1

How to set up aws-name-server on Ubuntu?

Accepted Answer

Download the binary from gobuild.io, move it to /usr/bin, set capabilities for non-root execution with setcap, and configure upstart using the provided conf file, as outlined in the installation and upstart sections of the README.

Question 2

aws-name-server vs Route 53 for internal DNS?

Accepted Answer

aws-name-server is a lightweight, self-hosted option for tag-based EC2 discovery without Route 53 costs, but it lacks Route 53's advanced features like health checks, global latency-based routing, and managed scalability.

Question 3

Can aws-name-server resolve instances across multiple AWS regions?

Accepted Answer

It uses the --aws-region parameter, defaulting to the instance's region or us-east-1, so it typically queries one region at a time; for multi-region support, you'd need separate instances or custom modifications.

Question 4

How to troubleshoot if aws-name-server isn't responding?

Accepted Answer

Check logs in /var/log/upstart/aws-name-server.log, verify security group rules for port 53, ensure IAM permissions are correct, and confirm NS records are set up, as detailed in the troubleshooting guide.

Question 5

Is aws-name-server secure for exposing to the internet?

Accepted Answer

While it uses minimal AWS permissions and can run non-root, exposing port 53 publicly without restrictions can be risky; the setup guide recommends security group configurations that might need tightening for production.

Question 6

How does aws-name-server handle auto-scaling groups?

Accepted Answer

It dynamically resolves instances by tags, so if auto-scaling groups use consistent Name or Role tags, new instances will automatically appear in DNS, but there's no built-in health checking or load balancing.

aws-name-server

What is aws-name-server?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions