An enterprise network engineering team is deploying IPv6 across a new corporate VLAN. The design requirements mandate that client endpoints dynamically auto-configure their Global Unicast Address (GUA) interface identifiers using SLAAC and EUI-64 from the prefix advertised by the local default gateway. Additionally, clients must receive additional network settings—specifically IPv6 DNS server addresses and domain search lists—from a central DHCPv6 server without creating or tracking stateful IPv6 address leases on the DHCPv6 server. During initial deployment verification, client workstations correctly construct their GUA and link-local addresses but fail to receive any DNS configuration from the network. Which Router Advertisement (RA) flag configuration on the local default gateway router interface must be applied to resolve this issue?
- Set the Managed Address Configuration flag (M flag) to 0 and the Other Stateful Configuration flag (O flag) to 1 on the router interface.Answer
- BSet the Managed Address Configuration flag (M flag) to 1 and the Other Stateful Configuration flag (O flag) to 1, while defining the server's DHCPv6 pool range using multiple double-colon zero compressions such as 2001:db8::1::50.
- CDeploy an IPv6 DNS server and configure a standard DNS A record on the DNS server to map host IPv6 GUAs to hostnames.
- DSet the Managed Address Configuration flag (M flag) to 1 and the Other Stateful Configuration flag (O flag) to 0, while assigning the host default gateway address to a non-local IPv4 subnet address.