DNS

Monogoto now provides an optional DNS feature that lets you choose where and how your device resolves domain names. This capability gives you better performance, greater visibility into traffic, and enhanced security controls - all natively from your Monogoto connectivity.

You can configure DNS under Device Configuration, right after selecting or defining your APN. Devices can either inherit DNS settings from the APN or override them manually with Monogoto’s DNS addresses.

Why DNS Matters in IoT

Every time your device connects to a cloud service, API endpoint, or update server, it first performs a DNS lookup. DNS resolution directly affects:

• Latency

• Reliability

• Security

• Traffic routing behavior

• Visibility into application patterns

Optimizing DNS is often one of the simplest ways to improve performance and gain deeper operational insight into your IoT deployment.

DNS Configuration Options

You can choose between two methods:

Use DNS from the APN (Default)

The device automatically receives DNS via the APN it uses. This is the standard approach for most deployments and requires no additional configuration.

Manually Configure DNS

You may override the default DNS and configure the device to use Monogoto’s DNS resolvers. Two DNS options will be available:

• EU DNS resolver - optimal for devices operating in or near Europe

• US DNS resolver - optimal for devices operating in or near North America

Using a geographically closer resolver reduces lookup latency and improves performance when connecting to cloud platforms like Google Cloud, AWS, Azure, etc.

(DNS IP addresses will be added here once finalized.)

Key Benefits of Monogoto DNS

Lower Latency and Faster DNS Resolution

Choosing the right DNS region (EU or US) helps shorten the network path to the DNS servers. This results in:

• Quicker name resolution

• Faster transaction setup

• Reduced round-trip time when accessing services like Google DNS

• More predictable performance for latency-sensitive IoT applications

Reduced Risk of Unintended DNS Blocking

Public DNS providers may occasionally throttle or block requests coming from networks where certain devices behave badly or produce noisy traffic.

By using Monogoto’s DNS:

• You avoid being grouped with unrelated “bad actors”

• Your DNS traffic is isolated and trusted

• Devices experience fewer unexpected DNS errors

This is especially important for large fleets where even small DNS disruptions can impact thousands of devices.

Full Visibility Into URL-Level Traffic

When using Monogoto DNS, you gain powerful application-layer insights:

• What URLs your devices are accessing

• How much traffic is being sent to each destination

• Frequency and patterns of DNS queries

• Failures or anomalies in resolution

This helps with:

• Debugging

• Cloud API monitoring

• Detecting misconfigured devices

• Observing application behavior over time

For example, if your load balancer or CDN edge begins returning an incorrect IP address, you will see the failure immediately through DNS logs.

URL Filtering (DNS Firewall)

Monogoto DNS includes built-in URL filtering capabilities, enabling you to define:

• Allow lists - only approved domains are reachable

• Block lists - prevent access to unwanted or risky domains

This acts as a simple but effective firewall layer and helps enforce:

• Device compliance

• Security policies

• Tenant segmentation

• Protection from malware or unintended domains

For many IoT devices, DNS filtering is a lightweight and highly effective way to control outbound communication behavior.

When Should You Use Monogoto DNS?

Monogoto DNS is recommended when:

• You want lower latency for DNS lookups

• You need URL-level visibility for debugging or analytics

• You want enforceable security controls for outbound traffic

• You operate globally and want consistent performance

• You want to avoid unpredictable blocking from public DNS services

This feature is especially useful for:

• Telematics & fleet devices

• Smart meters & sensors

• Security & surveillance systems

• Industrial and automotive deployments

• Any IoT device relying on stable cloud endpoints

How to Configure DNS in the IoT Device

1. Go to Device Configuration

2. Select or create your APN

3. Choose DNS Source:

4. From APN

5. Manual Configuration

6. If selecting manual configuration, enter the DNS addresses:

7. EU DNS (IPv4)

8. US DNS (IPv4) (DNS IP addresses will be added here once finalized.)

9. Save the configuration and allow the device to reconnect.

Once active, DNS logs and URL analytics will appear in your monitoring tools.