Testing your records

Before updating the nameserver delegation at the domain registrar to point to IBM® NS1 Connect® nameservers, we recommend testing your DNS zone and record configuration using a dig command to perform a DNS lookup. If you are using a Linux or UNIX OS, you can perform DNS lookups directly against the NS1 Connect nameservers or, if using Windows, you can use nslookup.

To test a record (for example, somerecord.example.org) of a given type (for example, A), execute the following command:

The following example shows a dig command to test the A record, example.org.

dig @dns1.p04.nsone.net example.org A

Replace dns1.p04.nsone.net with an assigned nameserver for the zone.

Example response:

$ dig @dns1.p08.nsone.net example.org A

; <<>> DiG 9.11.6 <<>> @dns1.p08.nsone.net somerecord.example.org A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34333
;; flags: qr aa rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;somerecord.example.org. IN A

;; ANSWER SECTION:
somerecord.example.org. 3600 IN A 42.118.178.182
somerecord.example.org. 3600 IN A 148.92.244.181
somerecord.example.org. 3600 IN A 93.230.244.187
somerecord.example.org. 3600 IN A 125.221.7.255
somerecord.example.org. 3600 IN A 111.124.237.165

;; Query time: 2 msec
;; SERVER: 198.51.44.8#53(198.51.44.8)
;; WHEN: Mon Apr 22 15:47:00 UTC 2019
;; MSG SIZE rcvd: 119

You can also make use of third-party tools like What's My DNS.net to do more extensive tests; however, this service can occasionally represent testing locations falsely.

For extensive validation or load testing, contact IBM support for recommendations.