County IT must advertise a shared DNS prefix into two VRFs without merging the full routing tables. What is the appropriate technique?
Select an answer to reveal the explanation.
Short Explanation
Shared DNS shouldn’t mean marrying the whole SCADA and corporate maps. Route leaking is the narrow hallway that copies just the DNS prefix between VRFs. Export only what you mean to share—leave the rest in its own cabinet.
Full Explanation
Inter-VRF route leaking selectively imports or exports prefixes so shared services such as DNS are reachable from multiple VRFs without collapsing isolation. Filters and route-targets, or carefully scoped redistribution, limit what crosses. Putting everything in the global table or freely redistributing entire VRFs defeats segmentation, and matching OSPF process IDs alone does not auto-merge VRF tables. Design least-privilege leaking and verify return paths for the shared service.