- 中文版
- Release Notes
- 产品介绍
- 使用指南
- 指标说明
- 脚本录制器
- 常见问题
- 功能分析
- 错误分析
- 打开流媒体失败
- 打开流媒体失败
- 打开流媒体失败
- 页面任务元素出现阻塞时间的分析思路
- 无法解析域名和服务器地址
- 无法解析服务器名称或地址
- 无法解析服务器名称或地址
- 无法解析服务器名称或地址
- 无法解析服务器名称或地址
- 无法与服务器建立连接
- 无法与服务器建立连接
- 无法与服务器建立连接
- 无法与服务器建联连接
- 与服务器建立连接失败
- 操作超时
- 操作超时之Chrome90
- 任务超时
- 任务超时
- 服务器连接被重置
- 与服务器连接被重置
- 与服务器连接被重置
- 应用的证书无效
- 应用证书无效
- 应用证书无效
- 安全频道支持出错
- 安全频道支持出错
- 安全频道支持出错
- 证书错误
- 私有化平台页面访问报-100错误
- 404 - Not Found错误
- HTTP/1.1 403 Forbidden
- HTTP412错误
- 元素报表数值对不上
- 数据分析
- 如何区分HLS格式是直播还是点播
- 报表数据与客户服务器端统计不一致
- DNS时间过长的分析思路
- 绑定对比任务的消耗点数不同
- 4G真机监测下客户反馈http via不正确
- 节点IP定位不准确
- 私有化平台任务无数据
- CDN厂商CNAME无响应问题
- 单文件下载任务， 创建后无数据
- SSL握手时间长
- 监控数据量少，和节点组频率对应不上
- 跨省跨运营商现象分析
- 流媒体任务，三个任务数据量相差较大
- 相同文件下载，不同厂商字节数下载不同
- 单文件下载，配置MD5，下载不全未报错。
- DNS时间较长问题分析
- PING任务警告，Request timed out
- PING任务丢包百分之百
- 元素瀑布图中有重复元素加载
- 散点数据和抓包数据对不上
- 抓包中如何查看传输的内容
- 任务无数据/数据少
- 相同URL，额外等待时间影响onload时间
- 听云监测数据和浏览器访问数据总下载字节数相差较大
- DNS时间较长
- 跨运营商访问
- 页面任务元素出现阻塞时间
- 抓包中出现TCP ZERO window
- 报表权限
- 节点分析
- 告警分析
- 问题百问
- English
- Release Notes
- Product Introduction
- Product Overview
- How It Works
- Product Architecture
- Typical Scenarios
- CDN Acceleration Evaluation and Selection
- Website Benchmarking Analysis
- Website Application Stress Test Analysis
- Website Performance Evaluation and Optimization
- Observable Hybrid Load Testing Scenario
- DNS Hijacking Monitoring - CNAME Monitoring
- VPN Quality Monitoring
- WIFI Quality Monitoring
- SMS Service Quality Monitoring
- API Active Monitoring
- Certificate Monitoring
- MTR Network Link Monitoring
- Enterprise Business Quality Monitoring
- End-to-End Scenario Monitoring
- Whois Domain Monitoring Scenario
- IPv6 Support Rate Monitoring
- Core Advantages
- Feature Modules
- User Guide
- Metric Descriptions
- PC Monitoring
- Page Metrics
- File Metrics
- Transaction Metrics
- Streaming Media Metrics
- Ping Metrics
- MTR Metrics
- Private Protocol Metrics
- Private Protocol Metrics Overview
- WebSocket Plugin Configuration Guide
- DIG Plugin Configuration Guide
- Socket(TCP/UDP) Plugin Configuration Guide
- Telnet Plugin Configuration Guide
- FTP Plugin Configuration Guide
- SMTP/IMAP/POP3 Plugin Configuration Guide
- MTR Plugin Configuration Guide
- Traceroute Plugin Configuration Guide
- DeepSeek Plugin Configuration Guide
- TCP Send Plugin Configuration Guide
- UDP Plugin Configuration Guide
- HTTP(SM) Plugin Configuration Guide
- HTTP3 Plugin Configuration Guide
- OCSP Plugin Configuration Guide
- WIFI Plugin Configuration Guide
- VPN Plugin Configuration Guide
- Mobile (H5) Monitoring
- PC Monitoring
- Script Recorder
- FAQs
- Feature Analysis
- Create Task
- Create Probe Group
- Advanced Parameters - End Conditions
- Advanced Parameters - Diagnostics
- Verify Probe DNS When Report Has No Data
- No Data After Configuring a Streaming Media Monitoring Task
- Does the Platform Support Checking Whether a Specified CNAME Takes Effect
- Real Device Single File Task Download Crash
- Tingyun Monitoring Does Not Match Actual Browser Access Data
- Error Caused by Incomplete Monitoring Address
- Bound Host Does Not Take Effect and Host IP Outside List Appears
- Bound Host Does Not Take Effect and Host IP Outside List Appears
- Same IP Has Different Resolution Results Across Task Types
- Copied Task Cannot Be Bound
- Instant Testing IPv6 Page-Level Explanation
- Private Protocol Socket (TCP/ UDP)
- Error Analysis
- Failed to open streaming media
- Failed to open streaming media (2)
- Failed to open streaming media (3)
- Troubleshooting Blocking Time for Page Task Elements
- Unable to Resolve Server Name or Address
- Unable to Resolve Server Name or Address (2)
- Unable to Resolve Server Name or Address (3)
- Unable to Resolve Server Name or Address (4)
- Unable to Resolve Server Name or Address (5)
- Unable to Establish Connection with Server
- Unable to Establish Connection with Server (2)
- Unable to Establish Connection with Server (3)
- Unable to Establish Connection with Server (4)
- Failed to establish connection with server
- Operation Timeout
- Chrome 90 Operation Timeout
- Task timeout
- Task timeout (2)
- Server Connection Reset
- The connection to the server was reset
- The connection to the server was reset (2)
- Invalid Application Certificate
- Invalid Application Certificate (2)
- Invalid Application Certificate (3)
- Secure channel support error
- Secure channel support error (2)
- Secure channel support error (3)
- Certificate Error
- -100 Error When Accessing Private Platform Page
- 404 - Not Found error
- HTTP/1.1 403 Forbidden
- HTTP412 error
- Element Report Values Do Not Match
- Data Analysis
- How to Distinguish Live and VOD HLS Formats
- Report Data Does Not Match Customer Server Statistics
- Troubleshooting Long DNS Time
- Different Point Consumption for Bound Comparison Tasks
- Incorrect HTTP Via Reported in 4G Real Device Monitoring
- Inaccurate Probe IP Location
- No Data for Tasks on Private Platform
- CDN Vendor CNAME No Response Issue
- No Data After Creating Single File Download Task
- Long SSL Handshake Time
- Low Monitoring Data Volume Does Not Match Probe Group Frequency
- Cross-Province and Cross-Carrier Phenomenon Analysis
- Large Data Volume Difference Across Three Streaming Media Tasks
- Different Vendors Download Different Byte Counts for Same File
- Single File Download with MD5 Configured Does Not Report Incomplete Download
- Long DNS Time Analysis
- Ping Task Warning - Request Timed Out
- Ping Task 100 Percent Packet Loss
- Duplicate Elements Loaded in Element Waterfall Chart
- Scatter Data Does Not Match Packet Capture Data
- How to View Transmitted Content in Packet Capture
- No or Insufficient Task Data
- Additional Wait Time Affects Onload Time for Same URL
- Large Difference Between Tingyun Monitoring and Browser Total Download Bytes
- Long DNS Time
- Cross-Carrier Access
- Blocking Time Appears for Page Task Elements
- TCP Zero Window Appears in Packet Capture
- Probe Analysis
- Alert Analysis
- Q&A
Does the Platform Support Checking Whether a Specified CNAME Takes Effect
Answer: Not supported#
Problem description#
Existing data’s explanation of CNAME functional indicators#
2. Currently there is no visual place to check which CNAME is specified.
3. It is a make-up in Nslookup and cannot be controlled.
4. On Chrome 79, you can refer to packet capture. On chrome90, because CNAME is specified, DNS is filtered out.