You have imported or manually configured a DNS zone and set up a bunch of records. Before you transition your production traffic to NS1's nameservers, you want to do some DNS lookups to confirm everything is working as expected. Here's how:
If you are using a Linux or Unix OS, you can do DNS lookups directly against the NS1 nameservers using
dig (on Windows, you can use
To test a record like somerecord.example.org of a given type (say an A record), do: dig @dnsX.pYY.nsone.net somerecord.example.org A -- replace "dnsX.pYY.nsone.net" with one of the nameservers under the Nameservers tab in your zone. You can repeat this for other records you need to test.
$ dig @dns1.p04.nsone.net example.org any ; <<>> DiG 9.8.1-P1 <<>> @dns1.p04.nsone.net example.org any ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17103 ;; flags: qr aa rd; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 5 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;example.org. IN ANY ;; ANSWER SECTION: example.org. 60 IN NS dns1.p04.nsone.net. example.org. 60 IN NS dns2.p04.nsone.net. example.org. 60 IN NS dns3.p04.nsone.net. example.org. 60 IN NS dns4.p04.nsone.net. example.org. 60 IN MX 10 mail.example.org. example.org. 60 IN SOA dns1.p04.nsone.net. hostmaster.example.org. 1380566489 43200 7200 1209600 60 ;; ADDITIONAL SECTION: dns1.p04.nsone.net. 86400 IN A 220.127.116.11 dns2.p04.nsone.net. 86400 IN A 18.104.22.168 dns3.p04.nsone.net. 86400 IN A 22.214.171.124 dns4.p04.nsone.net. 86400 IN A 126.96.36.199 mail.example.org. 60 IN A 188.8.131.52 ;; Query time: 8 msec ;; SERVER: 184.108.40.206#53(220.127.116.11) ;; WHEN: Fri Oct 25 16:13:22 2013 ;; MSG SIZE rcvd: 275
You can also make use of third party tools like What's My DNS to do more extensive tests, however please note that this service can falsely represent testing locations on occasion.
Need to do more extensive validation or load testing? Contact [email protected] and we can make recommendations.