DNS Lookup   «Prev 

Changing Servers and Listing Domains

If you have use of a UNIX system, you should experiment with directing nslookup at different servers.
  1. Set the default server for nslookup to be your favorite authoritative server (we assume you are running nslookup already): 

> server your_favorite_dns_server
  1. Verify that you can query the server for SOA, NS, and A records.
  2. Try to list the domain at your favorite server. For example, suppose it is corporation.com; try:
> ls corporation.com
Did it work?
  1. If you have time, consider experimenting with tcpdump and nslookup. Use nslookup to generate DNS queries and use tcpdump to watch the resulting network traffic.

Create Private DNS Namespace

Service: Amazon Route 53 Auto Naming
Creates a private namespace based on DNS, which will be visible only inside a specified Amazon VPC. The namespace defines your service naming scheme. For example, if you name your namespace example.com and name your service backend, the resulting DNS name for the service will be backend.example.com. For the current limit on the number of namespaces that you can create using the same AWS account, see Limits on Auto Naming in the Route 53 Developer Guide.

Request Syntax

{
"CreatorRequestId": "string",
"Description": "string",
"Name": "string",
"Vpc": "string"
}