Autoconfiguration considerations

During autoconfiguration, make the following considerations:

A manually configured address or prefix on an interface disables stateless autoconfiguration for the interface.
INTERFACE name DELADDR addr/prefix and INTERFACE name DEPRADDR addr/prefix profile statements that are activated with the VARY TCPIP,,OBEYFILE command are not valid for autoconfigured addresses.
A VARY TCPIP,,OBEYFILE command whose profile contains ADDADDR INTERFACE or DELADDR INTERFACE statements can affect stateless autoconfiguration:
- An INTERFACE name ADDADDR addr/prefix profile statement that is activated with the VARY TCPIP,,OBEYFILE command results in the deletion of stateless autoconfigured addresses on the interface. Stateless autoconfiguration capability is disabled.
- If the DELADDR profile statement removes the last manually configured address or prefix, stateless autoconfiguration is enabled and subsequent router advertisements can generate autoconfigured addresses.

Guidelines:

Consider using VIPA addresses in conjunction with autoconfigured addresses because public autoconfigured addresses are not automatically added to the Domain Name System (DNS).
Do not add temporary autoconfigured address to the DNS. Temporary autoconfigured addresses are regenerated periodically to prevent client activity from being correlated. If a DNS name is associated with the addresses, the DNS name might be used for correlation.