Forum Discussion
DNS and NTP reachability from non-0 route domain
Hello,
I'm currently deploying a bunch of F5 but I'm facing an issue with the normal behavior of the device regarding route-domain 0.
In fact, I don't have any interface on the route domain 0 and my management traffic is located on the route-domain 1 ... However I still need to access remote NTP/DNS/Syslog servers for the normal activities of my F5.
From my experience, it seems that this type of traffic cannot be originated from another route-domain self-IPs.
Did you already face this type of design and if yes how did you solve it ?
In advance, thank you.
Guillaume
I found the way to enable communication between both RD. Only thing is create a route from 0.0.0.0%0 (based on which traffic you want to route) and route it to default gateway within other route domain where your external routing sit.
1 Reply
- guidem15_338787
Altostratus
I found the way to enable communication between both RD. Only thing is create a route from 0.0.0.0%0 (based on which traffic you want to route) and route it to default gateway within other route domain where your external routing sit.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
