serviceLookupsAndConfiguration

Create DNS config

<Info icon="fa-light fa-lock" className="permission-callout"> <div className="permission-callout__header"><span className="permission-callout__title"><span className="permission-callout__label">Required permissions</span> <span className="fern-docs-badge small blue subtle rounded-full permission-callout__beta">Beta</span></span> <span className="permission-callout__learn-more">[Learn more](/developers/api-guidelines/permissions#how-permissions-work)</span></div>

Dns + Create

<div className="permission-callout__roles"><span className="permission-callout__roles-label">Roles:</span> <Badge intent="info">Administrator</Badge> <Badge intent="info">User</Badge></div> </Info>

Creates a DNS configuration object. The DNS config can be applied to a service profile and all endpoints which use that service profile will have the associated DNS settings applied. DNS changes are instantly applied to any new PDP context. Connected devices with previously established PDPs will continue to use the previous nameserver config until the next time they reconnect.

Primary and secondary nameservers and IP version (4 for IPV4 or 6 for IPV6) must be specified with this request.

<Info> The system currently falls back to IPV4 for the actually-enforced networking settings of endpoints, therefore **the IPV6 parameter will be ignored** when provided. </Info>
post/api/v1/dns

Request

  • Base URL: https://cdn.emnify.net
  • URL: https://cdn.emnify.net/api/v1/dns
  • Auth: HTTP bearer

Request body

primarystring required
secondarystring required
ip_address_versioninteger required

Response

Resource Created

ServiceLookupsAndConfigurationDnsPostResponse201 required

Empty response body

Changes

No recorded changes to this operation across all 1 revision of this API.