The parent servers are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records.
That may cause some extra milliseconds in DNS. This will usually occur if your DNS servers are not in the same TLD as your domain
All of your NS records appear to use public IPs.
SOA record is:
Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
There is serial 1610592151 at nameserver(s) (18.104.22.168)
There is serial 1610592155 at nameserver(s) (22.214.171.124)
SOA (Start of Authority) record states that your master (primary) name server is: 126.96.36.199, but that server is not listed at the parent servers.
SOA serial number is: 1610592151 This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. This number must be incremented every time you make a DNS change.
SOA Retry interval is : 10800 seconds. This seems OK. (Values about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates.
SOA Retry interval is : 3600 seconds. This seems OK. (Values about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
SOA Expire time is : 604800 seconds. This seems OK. (Values 604800 to 2419200 seconds (1-4 weeks) is good). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
SOA Expire time is : 60 seconds. This seems too small. (about 300 to 86400 seconds or 5 min - 24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
Trace to cybersuraksha.co.in
lookup cybersuraksha.co.in at A.ROOT-SERVERS.NET(188.8.131.52) 5 ms
A.ROOT-SERVERS.NET(184.108.40.206) refer to ns1.registry.in(220.127.116.11)
lookup cybersuraksha.co.in at ns1.registry.in(18.104.22.168) 3 ms
ns1.registry.in(22.214.171.124) refer to curaksha.mars.orderbox-dns.com(unknow IP)
extra IP lookup for curaksha.mars.orderbox-dns.com at root server A.ROOT-SERVERS.NET(126.96.36.199)
lookup curaksha.mars.orderbox-dns.com at A.ROOT-SERVERS.NET(188.8.131.52) 14 ms
A.ROOT-SERVERS.NET(184.108.40.206) refer to a.gtld-servers.net(220.127.116.11)
lookup curaksha.mars.orderbox-dns.com at a.gtld-servers.net(18.104.22.168) 5 ms
a.gtld-servers.net(22.214.171.124) refer to andy.ns.cloudflare.com(126.96.36.199)
lookup curaksha.mars.orderbox-dns.com at andy.ns.cloudflare.com(188.8.131.52) 6 ms
got A record 'curaksha.mars.orderbox-dns.com IN A 184.108.40.206' from curaksha.mars.orderbox-dns.com(220.127.116.11)
lookup cybersuraksha.co.in at curaksha.mars.orderbox-dns.com(18.104.22.168) 115 ms
got A record 'cybersuraksha.co.in IN A 22.214.171.124' from cybersuraksha.co.in(126.96.36.199)