Zipy
  • Welcome to Zipy ai
  • Getting Started
    • Install Zipy
    • Installing with Google Tag Manager
    • Supported frameworks
    • Security Overview
    • Sensitive User Data
    • SOC2 Type II
  • Zipy For Mobile
    • React Native Setup
      • Install React Native
      • Input Masking
      • Session Replay
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Fetch and XHR Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
    • Flutter Setup
      • Install Flutter
      • Session Replay
      • Input Masking & Custom Masking
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Http Network Calls
      • Dio Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
      • Session Recording Control
      • Data Sanitization
  • iOS Setup
    • Install in an iOS app
    • Identify Users
    • Screen Tracking & Tagging
    • Custom Logging
    • Session URL Retrieval
    • Session Recording Control
    • Input Masking & Custom Masking
  • Chrome Extension
    • Zipy Plug and Play Support
  • Configure
    • Zipy Recording Control
    • Release Version
    • Identifying Users
    • Adding Custom Identifiers
    • Anonymize Users
    • Source Maps
    • Blocking PII data
    • Ignoring Errors/Noise
    • npm Update
    • Support Integration
    • Session Stitching (rootDomain)
  • Product Features
    • Custom Events
    • Session Replay
    • Errors
    • Analytics
    • Time Filters
    • Multiple Filters
    • Clicked Element Filters
    • Manage Teams
    • Stack Trace
    • Console Logs
    • Network Requests
    • Network Headers and Payload
    • Custom Logs
    • Live Users
    • Alerts
      • Slack Alerts
      • Email Alerts
      • Live Alerts
      • Custom Alerts
    • Auto Resolve Errors
    • Zipy Labels Plugin
    • iFrame Support
    • API Performance
    • Heatmaps
    • Page Performance
    • Seen/Unseen Sessions
    • Public Session URL
  • FAQs
    • Install Zipy
    • Session Replay Definition
    • Error Tracking
    • Error Classification
    • Environment Support
    • Impact on your App
    • Performance Impact
    • Mobile Support
    • Network Data Capture
    • API Performance Diagnostic Help
      • High DNS Time
      • High SSL Connection Time
      • High Connection Setup Time
      • Large API Response Size
      • High Response Time
      • Compression Not Enabled
      • Server side API Failures
      • Client side API Failures
      • Insecure Connections
  • Troubleshooting
    • Errors in npm
    • Network header missing in Zipy
    • Can't see user data in sessions
    • No recordings or errors visible
    • No network timing split available
  • Product Videos
    • Ask AI
    • Getting Started
    • Session Replay
    • Multiple Project Creation
    • Team Management
    • Alerting on Slack
    • Time Filters and Daily Alerts
    • Custom Identifiers
    • Ignore Errors
    • Identify Users
    • Dashboard
    • Resolve Errors
    • New Error Digest
    • Jira and Slack
    • Online/Offline Network Status
    • Zipy on Zipy
      • Zipy Product Roadmap
  • Whats new
    • Product Updates
  • Legal & Policy
    • Terms of Service
    • Privacy Policy
    • Fulfillment Policy
    • Cookie Policy
    • Acceptable Usage Policy
    • Zipy Sub Processor List
  • Integration
    • Azure DevOps
    • Factors
    • RB2B
    • Webflow
    • WordPress
    • Amplitude
    • Coralogix
    • DevRev
    • Drift
    • Errorception
    • Freshchat
    • Google Analytics
    • Heap
    • HelpScout
    • Honeybadger
    • Hubspot
    • Intercom
    • Mixpanel
    • New Relic
    • Pendo
    • Raygun
    • Rollbar
    • Segment
    • Sentry
    • Shopify
    • Sumo Logic
    • TrackJS
    • Zendesk
Powered by GitBook
On this page
  • Why am I seeing this diagnostic?
  • How do I fix this?
  1. FAQs
  2. API Performance Diagnostic Help

High DNS Time

Why am I seeing this diagnostic?

As a webapp developer, you're likely familiar with the concept of DNS (Domain Name System). DNS is essentially a system that translates human-readable domain names (like zipy.ai) into IP addresses that computers understand. When your webapp connects to an API, it needs to resolve the API's domain name to an IP address using DNS.

DNS resolution time refers to the time it takes for the DNS lookup process to complete and return the IP address associated with a domain name.

High DNS resolution times in your app's API calls can be caused by various factors, such as misconfigured DNS settings, DNS server latency or overload, network connectivity issues, DNS caching problems, or a large number of DNS lookups being performed.

When you experience high DNS resolution times, it can have several implications for your webapp:

  1. Increased latency: Longer DNS resolution times directly contribute to the overall latency of your API connections. If DNS resolution is slow, it delays the start of the actual data transfer, resulting in slower response times from the API server.

  2. Performance impact: If your webapp relies on multiple API connections, each with its own DNS resolution process, the cumulative delay can significantly impact the overall performance and responsiveness of your application.

  3. User experience: Slow DNS resolution times can frustrate users who expect quick responses from your webapp. It may give the impression that your application is slow, even if the API response itself is fast.

How do I fix this?

To optimize DNS resolution times and mitigate these issues, consider the following:

  1. DNS caching: Implement caching mechanisms in your webapp to store resolved IP addresses locally. This reduces the reliance on DNS resolution for subsequent requests to the same domain, improving performance.

  2. DNS resolver selection: Evaluate the DNS resolver being used by your webapp. Sometimes, switching to a faster or more reliable resolver can significantly improve resolution times.

  3. Reduce DNS lookups: Minimize the number of DNS lookups your webapp performs. If possible, reuse existing connections or implement connection pooling to reduce the need for frequent DNS resolutions.

  4. Monitor and optimize: Continuously monitor and analyze the DNS resolution times of your webapp. Identify patterns, bottlenecks, or issues with specific domains and take appropriate actions to optimize performance.

PreviousAPI Performance Diagnostic HelpNextHigh SSL Connection Time

Last updated 1 year ago