The SOA record for the zone is required to be present in the primary Name Server and is not found. This usually means that the zone file is not setup properly in the primary Name Server host. It may also be due to any of the following reasons.
The Name Server domain is actually not running at all. Start your Name Server domain before running this test again.
The Name Server domain is not reachable from the Internet because there is a firewall or filtering router that is blocking connections to port 53 on this host for both UDP and TCP connections. The firewall configuration must permit connections on this port from any host on the Internet for the DNS to function properly.
MX Record(s)
Target
IP
Priority
TTL
No Record(s) Found
Reverse Lookup
IP Address
Reverse Lookup Name
Reverse IP Address
Status
103.251.186.40
OK
Name Server Performance
Server
Resolved IP
TTL
Response Time (ms)
Status
dems03.imd.gov.in.[14.139.247.8]
103.251.186.40
86400
286
NOTICE
Namespace Server delegation
Root Server Glue IP mapping
Name Server mapping
Status
Root Server Glue IP
dems03.imd.gov.in.
14.139.247.8
OK
14.139.247.8[dems03.imd.gov.in.]
-
Possible DNS forwarding issue.
DNS Traversal- performed using
i.root-servers.net.
Server
Name Servers
Response Time (ms)
Status
ns1.registry.in.[37.209.192.12]
dems04.imd.gov.in.
6
NOTICE
dems03.imd.gov.in.
ns6.registry.in.[156.154.101.20]
dems04.imd.gov.in.
6
NOTICE
dems03.imd.gov.in.
ns3.registry.in.[37.209.196.12]
dems04.imd.gov.in.
23
NOTICE
dems03.imd.gov.in.
ns4.registry.in.[37.209.198.12]
dems03.imd.gov.in.
6
NOTICE
dems04.imd.gov.in.
ns5.registry.in.[156.154.100.20]
dems03.imd.gov.in.
30
NOTICE
dems04.imd.gov.in.
ns2.registry.in.[37.209.194.12]
dems03.imd.gov.in.
6
NOTICE
dems04.imd.gov.in.
Find IP Address - Results: 19 Apr 2024 09:23:51 PM
