mirror of
https://github.com/netbirdio/docs.git
synced 2026-04-30 06:16:35 +00:00
Restructuring Phase 3 (#492)
This commit is contained in:
@@ -817,7 +817,7 @@ misconfiguration and resulting lack of connectivity establishment.
|
||||
This section will provide general directions for verifying connectivity on every step involved in handling
|
||||
the Domain Resources, to better understand where issue might lie.
|
||||
|
||||
For in-depth overview of the mechanism please read [Domain Resources](/how-to/networks#domain-resources) section.
|
||||
For in-depth overview of the mechanism please read [Domain Resources](/manage/networks#domain-resources) section.
|
||||
|
||||
Analyzing those issues will take a "backwards" approach (based on the most common issues), where we will first confirm
|
||||
that Routing Peer itself is working as expected and will check the client's operating system configuration as one of the
|
||||
@@ -905,7 +905,7 @@ Address: 100.83.136.209#22054
|
||||
### Trigger the Domain Resource
|
||||
|
||||
I have yet to see a local DNS forwarder fail, but using it is a good way of forcing the NetBird client to set up
|
||||
routing for the domain (see the [Domain Resources](/how-to/networks#domain-resources) for explanation).
|
||||
routing for the domain (see the [Domain Resources](/manage/networks#domain-resources) for explanation).
|
||||
|
||||
<Note>
|
||||
On MacOS & Windows the IP address would always be `100.83.255.254` instead of `100.83.73.97`.
|
||||
|
||||
Reference in New Issue
Block a user