When we configure name server in the mgmt-junos vrf - it doesn't work . Router doses not event try to connect to the the dns servers.

The name-servers should suprot work in mgmt-vrf - can you explains why it is not working.

labroot@jtac-acx7100-48l-ao-r2036> show route table mgmt_junos.inet.0 

mgmt_junos.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

0.0.0.0/0     *[Static/5] 00:47:33

          > to 10.219.37.193 via re0:mgmt-0.0

10.219.37.192/26 *[Direct/0] 00:47:34

          > via re0:mgmt-0.0

10.219.37.239/32 *[Local/0] 00:47:34

            Local via re0:mgmt-0.0

labroot@jtac-acx7100-48l-ao-r2036> show configuration interfaces re0:mgmt-0 | display set | display inheritance 

set interfaces re0:mgmt-0 unit 0 family inet address 10.219.37.239/26

labroot@jtac-acx7100-48l-ao-r2036> show configuration system management-instance | display set 

set system management-instance

labroot@jtac-acx7100-48l-ao-r2036> show configuration system name-server | display set 

set system name-server 10.219.2.101 routing-instance mgmt_junos

set system name-server 10.219.2.102 routing-instance mgmt_junos

set system name-server 10.215.194.50 routing-instance mgmt_junos

labroot@jtac-acx7100-48l-ao-r2036> show system connections | match "10.219.2|10.215" | refresh 1 

---(refreshed at 2026-02-26 16:34:10 IST)---

---(refreshed at 2026-02-26 16:34:11 IST)---

---(refreshed at 2026-02-26 16:34:12 IST)---

---(refreshed at 2026-02-26 16:34:13 IST)---

We have documented the process for Junos & Evo in below page.

https://www.juniper.net/documentation/us/en/software/junos/junos-getting-started-evo/junos-getting-started/topics/topic-map/dns-system-management.html

The verification step provided in the document is for global config (step 7). We can see the use of mgmt_junos vrf is optional in those steps.

So when you try reaching to hosts, you will need to use the mgmt_junos instance.

If customer is concerned only about not seeing any transactions in system connections, its because lookup will use udp port 53 normally (these transient udp transactions will not show up there).

We can verify with below output if DNS is fine.

labroot@jtac-acx7100-48l-ao-r2036> show host server 10.219.2.101 routing-instance mgmt_junos jtac-acx7100-48l-ao-r2033  

Using domain server:

Name: 10.219.2.101

Address: 10.219.2.101#53

Aliases:

jtac-acx7100-48l-ao-r2033.ultralab.juniper.net has address 10.219.37.246

labroot@jtac-acx7100-48l-ao-r2036> monitor traffic interface re0:mgmt-0 matching "host 10.219.2.101" no-resolve  

tcpdump: verbose output suppressed, use -v[v]... for full protocol decode

listening on vmb0, link-type EN10MB (Ethernet), snapshot length 262144 bytes

17:30:59.775655 IP 10.219.37.239.34688 > 10.219.2.101.53: 37275+ A? jtac-acx7100-48l-ao-r2033.juniper.net. (55)

17:30:59.777284 IP 10.219.2.101.53 > 10.219.37.239.34688: 37275 NXDomain 0/1/0 (125)

17:30:59.777457 IP 10.219.37.239.53210 > 10.219.2.101.53: 43083+ A? jtac-acx7100-48l-ao-r2033.ultralab.juniper.net. (64)

17:30:59.779525 IP 10.219.2.101.53 > 10.219.37.239.53210: 43083 1/0/0 A 10.219.37.246 (80)

17:30:59.779760 IP 10.219.37.239.53398 > 10.219.2.101.53: 36030+ AAAA? jtac-acx7100-48l-ao-r2033.ultralab.juniper.net. (64)

17:30:59.781741 IP 10.219.2.101.53 > 10.219.37.239.53398: 36030 0/1/0 (143)

17:30:59.781915 IP 10.219.37.239.37597 > 10.219.2.101.53: 51979+ MX? jtac-acx7100-48l-ao-r2033.ultralab.juniper.net. (64)

17:30:59.783857 IP 10.219.2.101.53 > 10.219.37.239.37597: 51979 0/1/0 (143)

labroot@jtac-acx7100-48l-ao-r2036> file show /etc/resolv.conf 

<snip>

nameserver 10.219.2.101 #vrf@mgmt_junos

nameserver 10.219.2.102 #vrf@mgmt_junos

nameserver 10.215.194.50 #vrf@mgmt_junos