Difference between revisions of "DNS"

From Luna Node
Jump to: navigation, search
(Created page with "The [https://dynamic.lunanode.com/panel/dns.php DNS management tab] gives you various options to manage DNS records regarding your virtual machines or otherwise. rDNS, DNS ho...")
 
 
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
−
The [https://dynamic.lunanode.com/panel/dns.php DNS management tab] gives you various options to manage DNS records regarding your virtual machines or otherwise.
+
We offer [https://dynamic.lunanode.com/panel/dns high-performance DNS hosting] with load balancing, automatic failover, and geo-targeting.
  
−
rDNS, DNS hosting, and dynamic DNS services are free. The latter two are service extensions that are currently in beta.
+
The nameservers are:
  
−
== Set rDNS records ==
+
* ns1.lunanode.net
 +
* ns2.lunanode.net
 +
* ns3.lunanode.net
  
−
PTR records for the IP addresses assigned to your various virtual machines can be updated from the '''rDNS''' section. For each IP address, you can enter an updated hostname, hit enter or press Update, and then the PTR record data will be updated. Note that it may take several hours for the new DNS settings to propogate, as DNS servers cache records.
+
Each user has one million free DNS queries per calendar month, assuming at least $3 credit is used on other services in that month. Additional queries are priced at $0.1 per 250K queries. Record storage is free.
  
−
The hostname will be displayed whenever an PTR lookup is performed on your IP address, for example '''ping''', '''mtr''', and other tools perform this hostname conversion automatically.
+
== Basic Configuration ==
  
−
== DNS hosting ==
+
To get started, add a zone from the [https://dynamic.lunanode.com/panel/dns DNS manager]. The name is your domain name or subdomain that has been delegated to our nameservers. The TTL is used for the SOA record.
  
−
lndynamic offers minimal DNS hosting, which can be controlled from the '''DNS hosting''' section of the DNS management tab. Start off by adding your domain by entering it into the '''Origin''' field. It will then appear in the zones table; you can select it there and manage DNS records for the zone.
+
Once the zone is added, you can select it from the manager to add and remove records. A minimal setup might look like this:
  
−
== Dynamic DNS ==
+
* Zone: example.com
 +
* Type: A, name: @, data: 1.2.3.4
 +
* Type: CNAME, name: www, data: example.com. (here, the dot at the end is important as it signifies that this is an FQDN)
 +
* Type: MX, name: @, data: example.com., priority: 0
  
−
The panel also lets you control dynamic DNS records, which are simply DNS records with a low TTL and which can be automatically adjusted from your computer via the lndynamic API (you must have API enabled for this to work). See the panel for more details.
+
== Monitoring ==
 +
 
 +
You can [https://wiki.lunanode.com/index.php/Server_monitoring create a server monitoring check], and then associate that with a DNS record so that the record is disabled if the check goes offline. To set this, select the Advanced tab when you add or edit a record.
 +
 
 +
Disabling a check is useful primarily in two scenarios.
 +
 
 +
'''Scenario 1:''' you want to distribute traffic between several servers, and have set up round-robin DNS:
 +
 
 +
* Type: A, name: @, data: 1.1.1.2
 +
* Type: A, name: @, data: 1.1.1.3
 +
* Type: A, name: @, data: 1.1.1.4
 +
 
 +
If a server goes offline, you don't want that server to be returned by the DNS server. Otherwise, you want all the records to be returned. In this case, set the weight to 0 for all records.
 +
 
 +
'''Scenario 2:''' you have a primary server and a backup server. The primary server should receive traffic, but if it fails, then traffic should failover to the backup server. Again, you have DNS records like this:
 +
 
 +
* Type: A, name: @, data: 1.1.1.2
 +
* Type: A, name: @, data: 1.1.1.3
 +
 
 +
Set the weight to 1000 for the primary server, and 1 for the backup server. Since the primary record's weight is more than 100 times the weight of the other record, the other record will not be used at all.
 +
 
 +
== Geo-targeting ==
 +
 
 +
The DNS server can be configured to select records based on the user's location. The user's location is determined based on IP geo-location data from MaxMind.
 +
 
 +
There are two ways to configure.
 +
 
 +
* Latitude/Longitude: enter the latitude/longitude of the server. The two records closest to the user will be returned.
 +
* Region-based: enter settings for the hierarchical structure. Note that you only need to configure one grouping, any less specific groupings can be determined automatically (e.g. if country is ca and continent is auto, then continent will be automatically set to north-america). The record(s) in the most specific grouping matching the client's location will be returned; by most specific, we mean the most specific one that has a non-zero number of records.

Latest revision as of 07:25, 6 July 2016

We offer high-performance DNS hosting with load balancing, automatic failover, and geo-targeting.

The nameservers are:

  • ns1.lunanode.net
  • ns2.lunanode.net
  • ns3.lunanode.net

Each user has one million free DNS queries per calendar month, assuming at least $3 credit is used on other services in that month. Additional queries are priced at $0.1 per 250K queries. Record storage is free.

Basic Configuration

To get started, add a zone from the DNS manager. The name is your domain name or subdomain that has been delegated to our nameservers. The TTL is used for the SOA record.

Once the zone is added, you can select it from the manager to add and remove records. A minimal setup might look like this:

  • Zone: example.com
  • Type: A, name: @, data: 1.2.3.4
  • Type: CNAME, name: www, data: example.com. (here, the dot at the end is important as it signifies that this is an FQDN)
  • Type: MX, name: @, data: example.com., priority: 0

Monitoring

You can create a server monitoring check, and then associate that with a DNS record so that the record is disabled if the check goes offline. To set this, select the Advanced tab when you add or edit a record.

Disabling a check is useful primarily in two scenarios.

Scenario 1: you want to distribute traffic between several servers, and have set up round-robin DNS:

  • Type: A, name: @, data: 1.1.1.2
  • Type: A, name: @, data: 1.1.1.3
  • Type: A, name: @, data: 1.1.1.4

If a server goes offline, you don't want that server to be returned by the DNS server. Otherwise, you want all the records to be returned. In this case, set the weight to 0 for all records.

Scenario 2: you have a primary server and a backup server. The primary server should receive traffic, but if it fails, then traffic should failover to the backup server. Again, you have DNS records like this:

  • Type: A, name: @, data: 1.1.1.2
  • Type: A, name: @, data: 1.1.1.3

Set the weight to 1000 for the primary server, and 1 for the backup server. Since the primary record's weight is more than 100 times the weight of the other record, the other record will not be used at all.

Geo-targeting

The DNS server can be configured to select records based on the user's location. The user's location is determined based on IP geo-location data from MaxMind.

There are two ways to configure.

  • Latitude/Longitude: enter the latitude/longitude of the server. The two records closest to the user will be returned.
  • Region-based: enter settings for the hierarchical structure. Note that you only need to configure one grouping, any less specific groupings can be determined automatically (e.g. if country is ca and continent is auto, then continent will be automatically set to north-america). The record(s) in the most specific grouping matching the client's location will be returned; by most specific, we mean the most specific one that has a non-zero number of records.
Retrieved from "https://wiki.lunanode.com/index.php?title=DNS&oldid=344"