|
|
(24 intermediate revisions by one user not shown) |
Line 1: |
Line 1: |
− | {{Sidebar}}
| + | #REDIRECT [[DNS_API]] |
− | <div style="font-size: 150%;">'''Premium DNS'''</div><br/>
| + | |
− | <p>
| + | |
− | | + | |
− | HEXONET's Premium DNS is a powerful, yet simple DNS solution that is built on our brand new, globally connected Anycast DNS network. Our highly-reliable Premium DNS service can optimize your DNS resolution, leading to faster response rates for your website and ensuring that your website is always responsive with our globally accessible DNS network. On top of that, Premium DNS adds multiple layers of security and protection against cybersecurity threats such as DDoS attacks. With today's standard on faster speed, tighter security and websites that are always accessible, Premium DNS is a must-have for anyone with a personal website, business, e-commerce and more!
| + | |
− | | + | |
− | Read below to learn more about Premium DNS.
| + | |
− | | + | |
− | = Upgrade Policy =
| + | |
− | === Upgrade from Basic DNS to Premium DNS ===
| + | |
− | Credit refund is not applicable. DNS zone will be upgraded to Premium DNS with a new plan, which will be registered for 1 year starting on the day of upgrade.
| + | |
− | | + | |
− | === Upgrade Premium DNS zone to a higher tiered plan ===
| + | |
− | Credit refund will be calculated based on the number of months left for existing Premium DNS plan. DNS zone will then be upgraded to a higher tiered plan, which will be registered for 1 year starting on the day of upgrade.
| + | |
− | | + | |
− | {{Warnbox|Note, it is not possible to change Premium DNS zone to a lower tiered plan while the current plan is still ongoing such as changing from a Premium 15M plan to a Premium 5M plan. Instead, you must wait for the current plan to expire and create a new DNS zone with the lower tiered Premium DNS plan.}}
| + | |
− | | + | |
− | = Over Limit and Suspension Policy =
| + | |
− | The monthly query usage of DNS zone is calculated based on the calendar month, not by the created date of the zone. A DNS zone query counter will reset to zero on the 1st of every calendar month. For example, if a DNS zone was created on March 15th, 2018 with a Premium 2M plan,
| + | |
− | | + | |
− | {| class="wikitable" style="width:100% !important"
| + | |
− | |-
| + | |
− | ! scope="col" style="text-align:left; border:1px solid darkgray" | Monthly cycle
| + | |
− | ! scope="col" style="text-align:left; border:1px solid darkgray" | Description
| + | |
− | |-
| + | |
− | | style="text-align:left" | March 2018 || The zone is allowed to make 2 million queries in total starting from March 15th, 2018 (created date) to March 31st, 2018.
| + | |
− | |-
| + | |
− | | style="text-align:left" | April 2018 to February 2019 || The zone is allowed to make 2 million queries in total starting from the 1st to the end of the current month
| + | |
− | |-
| + | |
− | | style="text-align:left" | March 2019 || The zone is allowed to make 2 million queries in total starting from March 1st, 2019 to March 14th, 2019 (expiration date)
| + | |
− | |}
| + | |
− | | + | |
− | If a DNS zone exceeds the query limit before the end of the calendar month, the following over limit and suspension policy will apply:
| + | |
− | | + | |
− | {| class="wikitable" style="width:100% !important"
| + | |
− | |-
| + | |
− | ! style="width:150px; border:1px solid darkgray" | Over limit
| + | |
− | | style="padding: 5px" | Once the DNS zone exceeds the monthly query limit, the user must upgrade to a higher tiered plan within 72 hours. Failing to do so will result in an immediate suspension of the DNS zone.
| + | |
− | <br>
| + | |
− | An email notice will be sent to the user regarding this event.
| + | |
− | |-
| + | |
− | ! style="border:1px solid darkgray" | Suspension
| + | |
− | | style="padding: 5px" | If the DNS zone is not upgraded within 72 hours after exceeding the monthly query limit, the DNS zone will be suspended and will not resolve any further queries.
| + | |
− | <br>
| + | |
− | An email notice will be sent to the user regarding this event.
| + | |
− | |}
| + | |
− | | + | |
− | === How to restore suspended Premium DNS zone ===
| + | |
− | Once a Premium DNS zone is suspended, a user can do one of the following to restore the zone:
| + | |
− | | + | |
− | * Upgrade to a higher tiered plan to immediately restore the zone, or
| + | |
− | * Wait for an automated restore at the start of the following month. Note, query counter is always reset at the beginning of each month so all DNS zones that were suspended in the previous month will be automatically restored due to the counter reset.
| + | |
− | | + | |
− | You can upgrade suspended Premium DNS zone with the following command
| + | |
− | | + | |
− | <pre>
| + | |
− | COMMAND = UpgradePremiumDNS
| + | |
− | CLASS = (Higher tiered Premium DNS plan)
| + | |
− | OBJECTID = (Premium DNS object ID)
| + | |
− | </pre>
| + | |
− | | + | |
− | To get the OBJECTID for your Premium DNS zone, use the following command
| + | |
− | | + | |
− | <pre>
| + | |
− | COMMAND = StatusDNSZone
| + | |
− | DNSZONE = (DNS zone name)
| + | |
− | </pre>
| + | |
− | | + | |
− | === Warning status using Control Panel ===
| + | |
− | There are 4 warning types for Premium DNS zone in the Control Panel
| + | |
− | | + | |
− | {| class="wikitable" style="width:100% !important"
| + | |
− | |-
| + | |
− | ! scope="col" style="width:120px; text-align:left; border:1px solid darkgray" | Warning type
| + | |
− | ! scope="col" style="text-align:left; border:1px solid darkgray" | Description
| + | |
− | |-
| + | |
− | | style="text-align:left" | High usage rate warning || Triggered when the Premium DNS zone is expected to exceed the monthly query limit, which is determined based on the current query usage rate.
| + | |
− | |-
| + | |
− | | style="text-align:left" | 80% usage warning || Triggered when the Premium DNS zone uses 80% of the monthly query limit before the end of the calendar month.
| + | |
− | |-
| + | |
− | | style="text-align:left" | 100% usage warning || Triggered when the Premium DNS zone uses 100% of the monthly query limit before the end of the calendar month. Following the over limit policy, the user must upgrade to a higher tiered plan within 72 hours. Otherwise, the DNS zone will be immediately suspended.
| + | |
− | <br>
| + | |
− | The user will also receive an email notice for this event.
| + | |
− | |-
| + | |
− | | style="text-align:left" | Suspension warning || Triggered when the Premium DNS zone is not upgraded within 72 hours after exceeding query quota, leading to a subsequent suspension of the DNS zone. Any queries to the DNS zone will stop resolving.
| + | |
− | <br>
| + | |
− | The user will also receive an email notice for this event.
| + | |
− | |}
| + | |
− | | + | |
− | === Warning status using API ===
| + | |
− | You can determine the warning status of Premium DNS zone with the following command:
| + | |
− | | + | |
− | <pre>
| + | |
− | COMMAND = StatusDNSZone
| + | |
− | DNSZONE = (DNS zone name)
| + | |
− | </pre>
| + | |
− | | + | |
− | The command will return QUERY-QUOTA-STATUS to represent the warning status of DNS zone:
| + | |
− | | + | |
− | {| class="wikitable" style="width:100% !important"
| + | |
− | |-
| + | |
− | ! scope="col" style="width:120px; text-align:left; border:1px solid darkgray" | QUERY-QUOTA-STATUS
| + | |
− | ! scope="col" style="text-align:left; border:1px solid darkgray" | Warning status of DNS zone
| + | |
− | |-
| + | |
− | | style="text-align:left" | OK || No warning issued for DNS zone
| + | |
− | |-
| + | |
− | | style="text-align:left" | WARNING || The DNS zone has used 80% of its monthly query limit and is at risk of exceeding the monthly query limit.
| + | |
− | |-
| + | |
− | | style="text-align:left" | EXCEEDED || The DNS zone has used 100% of its monthly query limit. User has 72 hours to upgrade to a higher tiered plan. Otherwise, the DNS zone will be suspended.
| + | |
− | |-
| + | |
− | | style="text-align:left" | SUSPENDED || The DNS zone is suspended and will stop resolving to any queries
| + | |
− | |}
| + | |
− | | + | |
− | The command will also return 3 other properties that will allow you to keep track of the DNS zone's query count:
| + | |
− | | + | |
− | {| class="wikitable" style="width:100% !important"
| + | |
− | |-
| + | |
− | ! scope="col" style="width:120px; text-align:left; border:1px solid darkgray" | Properties
| + | |
− | ! scope="col" style="text-align:left; border:1px solid darkgray" | Description
| + | |
− | |-
| + | |
− | | style="text-align:left" | QUERY-QUOTA-COUNT || Query count for the current month
| + | |
− | |-
| + | |
− | | style="text-align:left" | QUERY-QUOTA-PREDICTION || Expected query count for the whole month, which is dynamically calculated based on current quota count
| + | |
− | |-
| + | |
− | | style="text-align:left" | QUERY-QUOTA-LIMIT || Monthly query limit of the DNS zone
| + | |
− | |}
| + | |
− | | + | |
− | = Manage Legacy DNS Zones =
| + | |
− | All DNS zones created prior to October 1st, 2018 will be assumed as legacy zones for 1 year and will be eligible for one of the following retention plans:
| + | |
− | | + | |
− | {| class="wikitable" style="width:100% !important"
| + | |
− | |-
| + | |
− | ! scope="col" style="width:120px; text-align:left; border:1px solid darkgray" | Type of zone
| + | |
− | ! scope="col" style="text-align:left; border:1px solid darkgray" | Description
| + | |
− | |-
| + | |
− | | style="text-align:left" | Internal DNS zone || HEXONET will continue to support internal DNS zone under the same terms and conditions that was agreed upon creation until October 1st, 2019. This means internal DNS zone will <b>remain free of charge and has no monthly query limit</b> until October 1st, 2019.
| + | |
− | |-
| + | |
− | | style="text-align:left" | External DNS zone || HEXONET will continue to support external DNS zone under the same terms and conditions that was agreed upon creation until October 1st, 2019 (1 year duration after the launch of Premium DNS). This means external DNS zone will continue to be <b>charged in the customer's monthly invoice and has no monthly query limitation</b> until October 1st, 2019.
| + | |
− | |}
| + | |
− | | + | |
− | {{Warnbox|Customers can upgrade Legacy DNS zones to Premium DNS via the Control Panel or API any time until October 1st, 2019. Once upgraded to Premium DNS, the DNS zone will no longer be considered as a Legacy DNS zone and the new Premium DNS zone cannot be reverted back to Legacy DNS zone.}}
| + | |
− | | + | |
− | === Phasing out Legacy DNS zones ===
| + | |
− | On October 1st, 2019, HEXONET will start phasing out support for Legacy DNS zones.
| + | |
− | | + | |
− | * All internal Legacy DNS zones that were not upgraded to Premium DNS by October 1st, 2019 will be transferred over to Basic DNS, with all the restrictions of Basic DNS in place
| + | |
− | * All external Legacy DNS zones that were not upgraded to Premium DNS by October 1st, 2019 will be deleted
| + | |
− | | + | |
− | === Using Control Panel ===
| + | |
− | Legacy DNS zones will be listed under DNS Service > Legacy DNS zones
| + | |
− | | + | |
− | === Using API ===
| + | |
− | You can see all of your Legacy DNS zones with the following command:
| + | |
− | | + | |
− | <pre>
| + | |
− | COMMAND = QueryDNSZoneList
| + | |
− | MAXCREATEDDATE = 2018-10-01
| + | |
− | WIDE = 1
| + | |
− | USERDEPTH = Self
| + | |
− | </pre>
| + | |
− | | + | |
− | You can upgrade your Legacy DNS zone to Premium DNS with the following command:
| + | |
− | | + | |
− | <pre>
| + | |
− | COMMAND = CreatePremiumDNS
| + | |
− | DNSZONE = (DNS zone name)
| + | |
− | CLASS = (Premium DNS plan)
| + | |
− | </pre>
| + | |
− | | + | |
− | = How to Use and Monitor DNS Analytics =
| + | |
− | === Using Control Panel ===
| + | |
− | ....
| + | |
− | | + | |
− | === Using API ===
| + | |
− | You can get the query log for a Premium DNS zone with the following command
| + | |
− | | + | |
− | <pre>
| + | |
− | COMMAND = QueryDNSZoneStats
| + | |
− | DNSZONE = (DNS zone name)
| + | |
− | PERIODICITY = HOURLY | DAILY | MONTHLY
| + | |
− | </pre>
| + | |
− | | + | |
− | The command will return the date, error count and response count for each query, given the selected time frame.
| + | |