TheLostSwede
News Editor
- Joined
- Nov 11, 2004
- Messages
- 18,013 (2.44/day)
- Location
- Sweden
| System Name | Overlord Mk MLI |
|---|---|
| Processor | AMD Ryzen 7 7800X3D |
| Motherboard | Gigabyte X670E Aorus Master |
| Cooling | Noctua NH-D15 SE with offsets |
| Memory | 32GB Team T-Create Expert DDR5 6000 MHz @ CL30-34-34-68 |
| Video Card(s) | Gainward GeForce RTX 4080 Phantom GS |
| Storage | 1TB Solidigm P44 Pro, 2 TB Corsair MP600 Pro, 2TB Kingston KC3000 |
| Display(s) | Acer XV272K LVbmiipruzx 4K@160Hz |
| Case | Fractal Design Torrent Compact |
| Audio Device(s) | Corsair Virtuoso SE |
| Power Supply | be quiet! Pure Power 12 M 850 W |
| Mouse | Logitech G502 Lightspeed |
| Keyboard | Corsair K70 Max |
| Software | Windows 10 Pro |
| Benchmark Scores | https://valid.x86.fr/yfsd9w |
The nonprofit organisation that is in charge of coordinating and managing the namespaces and numerical spaces on the internet—ICANN or Internet Corporation for Assigned Names and Number—has proposed a rather big change on how consumers and businesses could be accessing networked devices on their private networks in the future. ICANN has put forward a new top-level domain for private use, much like the 192.168.x.x IP address range is allocated to private networks (alongside two other ranges), we might end up with a similar top-level domain. The proposed domain will be .internal, although we already have .localhost and .local today, but neither is really usable in a private network.
As such .internal has been suggested—in favour of.private due to concerns about it sounding like something privacy related—as a means for less computer savvy users to connect to devices on a private network. We've already seen solutions from several router manufacturers that use various domain names or subdomains to enable easier connectivity to routers. However, the goal here is to avoid clashes with top-level domains on the internet and.internal is said to resolve this problem. That said, it's not clear how this will be implemented as yet, but the ICANN is set to release more details in the near future. Even though it might not be the perfect solution, it should hopefully allow people to remember what they called their devices when they need to access them, rather than trying to remember the correct IP address.
View at TechPowerUp Main Site | Source
As such .internal has been suggested—in favour of.private due to concerns about it sounding like something privacy related—as a means for less computer savvy users to connect to devices on a private network. We've already seen solutions from several router manufacturers that use various domain names or subdomains to enable easier connectivity to routers. However, the goal here is to avoid clashes with top-level domains on the internet and.internal is said to resolve this problem. That said, it's not clear how this will be implemented as yet, but the ICANN is set to release more details in the near future. Even though it might not be the perfect solution, it should hopefully allow people to remember what they called their devices when they need to access them, rather than trying to remember the correct IP address.
View at TechPowerUp Main Site | Source
..
..
