IP address: 89.16.0.xxx is not a valid private address (RFC 1918/4193)

[Cioci89]

Good morning, my company, born in the 90's IPs 89.16.0.xxx were not yet assigned to France and were used “improperly” even now, and I have servers in local network with these addresses here.

The firewall has so-called “BlackHole” settings that prevent the 89.16.0.xxx network from being seen as a public network, but as a local network.

So my problem is to be able to bypass this constraint because lancache-dns blocks me with this message

IP address: 89.16.0.192 is not a valid private address (RFC 1918/4193).

But my 89.16.0.192 is private for my company....

If I can no longer use these public IPs as if they were local--then I can no longer use lancachenet.

Please let me know what I can do

Thank you

[VibroAxe]

@Cioci89 I'm afraid the RFC limitation doesn't come from LanCache but from the providers themselves. Any CDN with a handshake/trigger domain will not accept a lancache which isn't running on an offiical local node. This prevents a misconfigured route "caching" across the internet

Apologies but this is something we cannot fix

[Cioci89]

I thank you first of all for your reply, I actually use lancache for the Windows update part ...is there any “Environment” I can use to still allow the use of IPs that are considered non-private?