3 ms·
These aren't registrations; these are hostnames in use. For some reason -- perhaps just traditions -- it's especially common for bulk service providers to assi
by gojomo 16y ago
These aren't registrations; these are hostnames in use.
For some reason -- perhaps just traditions -- it's especially common for bulk service providers to assign individual machine/address subdomains from .NET rather than .COM.
Indeed: I'm using a Comcast cable modem, and you reach Comcast's web page at comcast.com -- but my dynamic IP reverse-resolves to a comcast.net subdomain, and is obviously one of many thousands from its formulaic construction (including within it the IP address and region hints).
- nwatson 16y agoIf this is 'hosts in use' then discrepancy comes from security concerns. The majority of computers in *.com concerns will be behind firewall and not have publicly exposed names. The .net orgs are more likely to let it all hang out.