How to Verify the DNS record under our nameservers

If you receive a case that customer want to point the DNS record to an IP and then you already added the DNS record, you would need to verify it first before you update to customer. By follow these steps :

1. Using nsloookup

# nslookup
> server ns1.idcloudhosting.com
Default server: ns1.idcloudhosting.com
Address: 103.82.240.100#53
> fascia.co.id
Server:		ns1.idcloudhosting.com
Address:	103.82.240.100#53

Name:	fascia.co.id
Address: 202.179.136.172

This mean that fascia.co.id are correctly pointing and it will be resolved to that IP once the nameservers has been changed

2. Using dig

 # dig IN A fascia.co.id @ns1.idcloudhosting.com

; <<>> DiG 9.10.6 <<>> IN A fascia.co.id @ns1.idcloudhosting.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52648
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;fascia.co.id.			IN	A

;; ANSWER SECTION:
fascia.co.id.		3600	IN	A	202.179.136.172

;; AUTHORITY SECTION:
fascia.co.id.		3600	IN	NS	ns2.idcloudhosting.com.
fascia.co.id.		3600	IN	NS	ns1.idcloudhosting.com.

;; ADDITIONAL SECTION:
ns1.idcloudhosting.com.	14400	IN	A	103.82.240.100
ns2.idcloudhosting.com.	14400	IN	A	42.1.61.102

;; Query time: 43 msec
;; SERVER: 103.82.240.100#53(103.82.240.100)
;; WHEN: Wed Oct 03 13:34:20 WIB 2018
;; MSG SIZE  rcvd: 143