mirror of
https://github.com/netbirdio/docs.git
synced 2026-04-19 17:06:36 +00:00
add missing word to routing-traffic-to-multiple-resources.mdx (#312)
This commit is contained in:
@@ -4,7 +4,7 @@ Adding routes to resources within on-premises or cloud is a common scenario for
|
||||
## Example
|
||||
In the following scenario, we will cover the case where all users have restricted access to internal DNS servers in the internal network, and the DevOps team has full access to the entire network.
|
||||
The network address is `172.16.0.0/15` and DNS servers has the IPs `172.16.30.2` and `172.17.100.2`.
|
||||
These IP ranges will routed using [Routing peers](/how-to/networks-concept#routing-peers) running in the network.
|
||||
These IP ranges will be routed using [Routing peers](/how-to/networks-concept#routing-peers) running in the network.
|
||||
|
||||
### Create a Network
|
||||
To create a Network, navigate to the `Networks` > `Networks` section in the NetBird dashboard:
|
||||
@@ -108,4 +108,4 @@ With the steps above, we created resources that allow different levels of access
|
||||
- Make sure to [star us on GitHub](https://github.com/netbirdio/netbird)
|
||||
- Follow us [on Twitter](https://twitter.com/netbird)
|
||||
- Join our [Slack Channel](https://join.slack.com/t/netbirdio/shared_invite/zt-31rofwmxc-27akKd0Le0vyRpBcwXkP0g)
|
||||
- NetBird [latest release](https://github.com/netbirdio/netbird/releases) on GitHub
|
||||
- NetBird [latest release](https://github.com/netbirdio/netbird/releases) on GitHub
|
||||
|
||||
Reference in New Issue
Block a user