cluster.ngcomms.net - robtex.com
cluster.ngcomms.net
| DNSSEC | ⚠️ Not signed | ||||||
| A | 59.100.174.105🇦🇺 ASN-CONNECT-NET59.100.0.0/15 AAPT Ltd | ||||||
| PTR | node1a.ngcomms.net | ||||||
| A | 125.254.4.169🇦🇺 COMINDICO-AP125.254.0.0/19 (7326) | ||||||
| NS | ns1.ngcomms.net ⭐ | ||||||
| A | 59.100.174.105🇦🇺 ASN-CONNECT-NET59.100.0.0/15 AAPT Ltd | ||||||
| PTR | node1a.ngcomms.net | ||||||
| A | 203.221.90.201🇦🇺 COMINDICO-AP203.220.0.0/15 Proxy route object registered by AS2764 | ||||||
| PTR | node1b.ngcomms.net | ||||||
| NS | ns2.ngcomms.net | ||||||
| A | 125.254.4.169🇦🇺 COMINDICO-AP125.254.0.0/19 (7326) | ||||||
| PTR | node2a.ngcomms.net | ||||||
| A | 203.174.171.249🇦🇺 TPG-AU203.174.171.240/28 | ||||||
| PTR | node2b.ngcomms.net | ||||||
| SOA | ns1.ngcomms.nethostmaster@noggin.com.au serial=2008177096 | ||||||
ngcomms.net
| DNSSEC | ⚠️ Not signed | ||||||
| NS | dns31.cloudns.net ⭐ | ||||||
| NS | dns32.cloudns.net | ||||||
| NS | dns33.cloudns.net | ||||||
| NS | dns34.cloudns.net | ||||||
| MX | cluster.ngcomms.net ⭐ | ||||||
| MX | node2a.ngcomms.net(20) | ||||||
| MX | node1a.ngcomms.net(30) | ||||||
| MX | node2b.ngcomms.net(40) | ||||||
| MX | node1b.ngcomms.net(50) | ||||||
| TXT | _jibyfbw6yhqism7x2vcv65ovl2s1r97 | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | dns31.cloudns.nethostmaster@noggin.com.au 2025-09-08 #5 | ||||||
MX for
oca21-basemx.syd1.sec2-soa.nogginoca.com |
oca21-syd1-sec2-mx.xdns.nogginoca.com |
ngcomms.net |
id.ngcomms.net |
Previously MX for
Same first word
Similar names
DNS History
5 records (4 active, 1 former)
●NSns1.ngcomms.net2015-05-14 → 2026-04-24 · 2 obs
● 2026-04-24 11:41:54
●NSns2.ngcomms.net2015-05-14 → 2026-04-24 · 2 obs
● 2026-04-24 11:41:54
●A125.254.4.1692015-05-14 → 2026-04-24 · 2 obs
● 2026-04-24 11:41:54
○A220.233.197.1692015-05-14 → 2016-12-16 · 4 obs
● 2016-12-16 01:14:04
○ 2026-02-15 17:31:32
○ 2026-04-24 11:41:54
●A59.100.174.1052026-02-15 → 2026-04-24 · 3 obs
● 2026-02-15 17:31:32
● 2026-04-24 11:41:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | d.gtld-servers.net, k.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net... | - |
| ngcomms.net | dns31.cloudns.net, dns32.cloudns.net, dns33.cloudns.net, dns34.cloudns.net | 8 records |
| cluster.ngcomms.net | ns1.ngcomms.net, ns2.ngcomms.net | 4 records |
✅ Authoritative Response
Server:203.174.171.249
NS records: ns1.ngcomms.net, ns2.ngcomms.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ngcomms.net (unsigned zone)
⏱️ Timing
Total: 625ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 59.100.174.105, 125.254.4.169 |
| NS | 2 | ns1.ngcomms.net, ns2.ngcomms.net |
| SOA | 1 | ns1.ngcomms.net hostmaster.noggin.com.au |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (dns31.cloudns.net, dns31.cloudns.net, dns32.cloudns.net...)
Analysis
Mail Server Role
cluster.ngcomms.net serves as the mail server for oca21-basemx.syd1.sec2-soa.nogginoca.com, oca21-syd1-sec2-mx.xdns.nogginoca.com, ngcomms.net and id.ngcomms.net.
Commonly, node1a.ngcomms.net, node1b.ngcomms.net and node2a.ngcomms.net serve as mail servers together with cluster.ngcomms.net.
IP Addresses
cluster.ngcomms.net resolves to two IP numbers: 59.100.174.105 and 125.254.4.169.
Other host names, for instance node2-1.ngcomms.net, node1-1.ngcomms.net, node2a.ngcomms.net, node1a.ngcomms.net and ns1.ngcomms.net share IP numbers with cluster.ngcomms.net.
Name Servers
Two name servers ns1.ngcomms.net and ns2.ngcomms.net handle delegation for cluster.ngcomms.net.
Host names with two IP numbers:
ns1.ngcomms.net points to: 59.100.174.105 and 203.221.90.201
ns2.ngcomms.net points to: 125.254.4.169 and 203.174.171.249