If you've just made any changes to the nameservers, you can verify if this has propagated at the root level.
Check root servers for the corresponding tld first. So for .com domains:
dig ns comThe output is as below:
;; ANSWER SECTION:
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS a.gtld-servers.net.Now query the root servers for the corresponding domain:
dig ns edices.com @g.gtld-servers.netThe additional section from the result with the IP address show the glue records.
;; AUTHORITY SECTION:
edices.com. 172800 IN NS ns1.edices.com.
edices.com. 172800 IN NS ns2.edices.com.
edices.com. 172800 IN NS ns3.edices.com.
;; ADDITIONAL SECTION:
ns1.edices.com. 172800 IN A 207.44.207.121
ns2.edices.com. 172800 IN A 207.44.206.16
ns3.edices.com. 172800 IN A 67.228.161.76