---
title: "set subscriber_secure_data bypass"
canonical: "https://docs.infoblox.com/space/nios86/35757167/set%20subscriber_secure_data%20bypass"
format: markdown
---
<span style="color: #000000">You can use the </span>`set subscriber_secure_data bypass `<span style="color: #000000">command to configure bypass subscriber service policies </span><span style="color: #000000">on all members of each site on the entire Grid, all members of the site or on a local member</span>**<span style="color: #000000">.</span>**<span style="color: #000000"> </span><span style="color: #000000">To view information about the status of the command, see </span>[*show subscriber_secure_data bypass*](https://infoblox-docs.atlassian.net/wiki/display/nios86draft/show+subscriber_secure_data+bypass)<span style="color: #000000">.</span>

## Syntax

`set subscriber_secure_data bypass <on | off > ``[grid | site][ "site_name" ]`

| **Argument** | **Description** |
| --- | --- |
| `on` | Enables subscriber service policies bypass. |
| `off` | Disables subscriber service policies bypass. |
| `grid` | <span style="color: #000000">Enable or disable the subscriber service policies bypass for all members of each site on the entire Grid.</span> |
| `site` | <span style="color: #000000">Enable or disable the subscriber service policies bypass for all members of the site.</span> |


> ⚠️ **Note**
> ⚠️ 
> ⚠️ - The newly added member do not inherit the bypass settings configured for the site. You must re-execute the bypass on/off CLI command.
> ⚠️ - For a member of the group, that is not upgraded, the bypass subscriber service policies are not configured, and the message "Failed to set Subscriber Secure Bypass state for the member <span style="color: #000000">dns.com</span><span style="color: #3e3f40">:</span> upgrade is in progress." is displayed.
> ⚠️ - The member must be part of a site even if the Subscriber Services are not running in order to configure Bypass Subscriber Service Policies.
> ⚠️ - When there is a DNS service restart, if a member is restarting and the `set subscriber_secure_data bypass` command is executed, then the Subscriber Secure Bypass state is not enabled for the member.
> ⚠️ - You can execute the `set subscriber_secure_data bypass` command with grid and site arguments only on the Grid Master and not on members.

# Examples

`Infoblox` > `set subscriber_secure_data bypass on`` ``site mobile1`

`Site: mobile1`  
`             Member:`` ``dns1.com`  
`                            Subscriber Secure Bypass enabled for the member dns1.com.`

`             Member:``dns2.com`  
`                            Subscriber Secure Bypass enabled for the member ``dns2.com``.`  
`             Member:``dns3.com`  
`                            Subscriber Secure Bypass enabled for the member ``dns3.com``.`

`Infoblox>`` ``set subscriber_secure_data bypass off site mobile1`

`Site: mobile1`

`             Member:``dns1.com`  
`                            Subscriber Secure Bypass enabled for the member dns1.com.`  
`             Member: ``dns2.com`  
`                            Subscriber Secure Bypass disabled for the member ``dns2.com``.`  
`             Member: ``dns3.com`  
`                            Subscriber Secure Bypass disabled for the member ``dns3.com``.`

`Infoblox > ``set subscriber_secure_data bypass off`

`Member: ``dns1.com`  
`             Subscriber Secure Bypass disabled on the member ``dns1.com``.`