You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
since the route entries are done via network range, i was wondering if it is possible to add also via FQDN.
for example i need to route cloudflare ip via netbird (since we have sites that allow only access from our Office IP).
so either add all the ip of cloudflare + WARP (which is a very very long list),
or maybe can use the internal DNS of netbird and have it populate to the clients that
if "netbird client" (AKA laptop) accesses cloudflare FQDN -> resolves to a site that is hosted on cloudflare -> route via netbird
its a long shot since no one can do that on traditional firewalls or SSL VPN but though i would ask
The text was updated successfully, but these errors were encountered:
Hi
thanks for your reply.
what i mean is that we have websites that are using amazon edge via
cloudfront.
according to these , they have about 9280 different IP and ranges.
if i could just add our website FQDN and then netbird will be able to route
that website via netbird instead of adding 9200 routes to netbird.
thanks
https://ip-ranges.amazonaws.com/ip-ranges.json
Hello.
since the route entries are done via network range, i was wondering if it is possible to add also via FQDN.
for example i need to route cloudflare ip via netbird (since we have sites that allow only access from our Office IP).
so either add all the ip of cloudflare + WARP (which is a very very long list),
or maybe can use the internal DNS of netbird and have it populate to the clients that
if "netbird client" (AKA laptop) accesses cloudflare FQDN -> resolves to a site that is hosted on cloudflare -> route via netbird
its a long shot since no one can do that on traditional firewalls or SSL VPN but though i would ask
The text was updated successfully, but these errors were encountered: