hat
Enthusiast
- Joined
- Nov 20, 2006
- Messages
- 21,755 (3.22/day)
- Location
- Ohio
System Name | Starlifter :: Dragonfly |
---|---|
Processor | i7 2600k 4.4GHz :: i5 10400 |
Motherboard | ASUS P8P67 Pro :: ASUS Prime H570-Plus |
Cooling | Cryorig M9 :: Stock |
Memory | 4x4GB DDR3 2133 :: 2x8GB DDR4 2400 |
Video Card(s) | PNY GTX1070 :: Integrated UHD 630 |
Storage | Crucial MX500 1TB, 2x1TB Seagate RAID 0 :: Mushkin Enhanced 60GB SSD, 3x4TB Seagate HDD RAID5 |
Display(s) | Onn 165hz 1080p :: Acer 1080p |
Case | Antec SOHO 1030B :: Old White Full Tower |
Audio Device(s) | Creative X-Fi Titanium Fatal1ty Pro - Bose Companion 2 Series III :: None |
Power Supply | FSP Hydro GE 550w :: EVGA Supernova 550 |
Software | Windows 10 Pro - Plex Server on Dragonfly |
Benchmark Scores | >9000 |
My ISP recently upgraded me to fiber optic internet to the home, as they're moving everyone to straight fiber and moving off the old infrastructure. For whatever reason, sites like speedtest and whatismyip seem to correctly identify my public IP, while my router shows my public IP as 100.64.160.237. Unfortunately, this means if I set up my router to automatically update my DDNS, it winds up being this 100.64.160.237 which no one can connect to. I've learned this is apparently some sort of "shared address space" which is a concept I don't really understand, nor how it affects me as a server host. I run a Quake server and it would be a real shame if that became impossible. I would also very much like it if I could automatically update my DDNS without giving it a useless IP.