3 ms·
If it’s behind NAT, anything can be used but best practice is to just the 10s
by m3kw9 6y ago
If it’s behind NAT, anything can be used but best practice is to just the 10s
- jrockway 6y agoDoes that actually work? If ISPs assign, say, 8.8.8.0/24, then you're going to have trouble determining whether that DNS lookup bound for 8.8.8.8 is 8.8.8.8 on the Internet or 8.8.8.8 on some link-local host. Because people typically use IPs designated as private behind a NAT, this isn't a problem in practice. But if you start using publicly-routable IP addresses internally, then you can create some fun problems. Actually, not even that fun. Just annoying.
- m3kw9 6y agoNAT usually translates a private ip to global ip, in your case there should be an internal DNS to resolve internal names
- p1mrx 6y agoYou're missing the point; 8.8.8.8 was just an example. For any public IP assigned inside your network, clients trying to reach to the real address won't be able to get there, because they'll hit the internal one instead.
- deleted 6y ago[deleted]
- rswail 6y agoBest practice for an ISP that is implementing CGNAT is to use 100.64.0.0/10 as per RFC 6598. That way, your customers can use private IPv4 (10/8, 172.16/12, 192.168/16) and you can manage your ISP network in the 100.64.0.0/10 space. Your CGNAT looks after translating your customer's ISP address (ie, the 100.64.0.0/10 side of their CPE). Of course, the best solution is to move to IPv6 and allocate each customer: * a /64 address out of the ISP's network space * a /48 (or /56) delegation for their own network See https://www.ripe.net/publications/docs/ripe-690 https://www.ripe.net/publications/docs/ripe-690