...

• Case-insensitive searches for IPv6 objects do not work.
• Search will yield results in the format IPv6  is entered in the Cloud Services Portal (UI or API). For example, if you create or update an IPv6 address in a normalized format (fc99:2222:3333::1) and search in the same way, the result will yield the object. The same is true for the non-normalized format (fc99:2222:3333:0:0:0:0:1).
• IPv6 Range search will work in the same format it is created. For example, if the range is created as ( 2001:db8:1:1:1::1:0001 - 2001:db8:1:1:1::1:1fff), the search will yield result if you search with 2001:db8:1:1:1::1:0001 or 2001:db8:1:1:1::1:1fff. If you search with 2001:db8:1:1:1::1:1, it will not yield any result.

Examples of wildcard search

Wildcard search provides three types of search:

• prefix - wildcard placed before the search string. If you do not add any wildcard, the search type will be prefix search by default.
• infix - wildcard placed within the search string.
• suffix - wildcard placed at the end of the search string.

Here is an example of how the wildcard search works. Let's say we want to search within the following text:

eu.network.com
networking.com
ams.network.com
fiber_network_details

Prefix search: When searching with the query network, search will generate a match only for networking.com. Without specifying the wildcard, the type of search is a prefix by default. 

Prefix, suffix and infix search: a query *network*  will generate  a hit for all texts with the word network. All the entries specified above will be listed. By using all the three types of search, we can get a more accurate result for the search string.