Torch Log Service
Torch Log Service
Torch Log Service
Document
Product News
Product Overview
Product Billing
User Guide
TLS Agent
AgentLoop
Resource management
Host group
Data collection
LogCollector collection
Introduction to LogCollector
Installation and upgrade
Collect host logs
Collect container logs
LogCollector plugins
Manage LogCollector
general reference
Data import
Cloud product log collection
TOS log collection
DBW log collection
VPN Log collection
VKE log collection
CLB log collection
CloudTrail log collection
CFW log collection
NTA log collection
ALB log collection
APMPlus log collection
veFaaS log collection
VPC log collection
veImageX log collection
TrafficRoute DNS log collection
DDoS log collection
WAF log collection
DCDN log collection
Multi-cloud security platform log collection
APIG log collection
Machine learning task log collection
CR log collection
Volcano Ark application lab log collection
FileNAS log collection
LLM Application Firewall Service log collection
vePFS log collection
Cloud security center log collection
EFS log collection
Data storage
Query and analysis
Configure log indexes
Query log
Analyze logs
Query and analyze logs using third-party tools
Associate external data source for log query
SQL function
SQL syntax
Visualization
Query and analysis charts
Summaries of query and analysis charts
Create dashboard
Use dashboard
Add dashboard filters and variables
Use other systems to analyze logs
Log application
Log applications for product observability
Log applications for large models observability
Coding Agent log app
ModelProvider log app
No-coding Agent log app
Log applications for basic service monitoring
Data processing
Data transformation
Syntax and functions
Global operation function
expression function
Data processing best practices
general reference
Data write processor
Data consumer processor
Data consumption and shipping
Ship logs to TOS
Ship logs to Kafka
Ship logs to Splunk
Alarm
Alarm policy
Alarm notification content
Alarm notification content template
alarm notification channel
Tracing service
Monitor Log Service
API reference
Project management API
Topic management API
Shard management API
Index management API
Log management API
Host group management API
Collection configuration management API
Data import API
Data processor API
Data transformation API
Data backflow API
SQL analysis API
Alarm management API
Consumer group management API
Kafka protocol consumption API
Tag management API
Trace storage API
Account management API
SDK reference
Go SDK
Java SDK
Python SDK
iOS SDK
C++ SDK
CLI reference
Best practices
Data collection
Query and analysis
permission management
Consumption and delivery
Visualization
Alarm
FAQs
Billing and cost FAQ
Data collection FAQ
Data storage FAQ
Index configuration FAQ
Query and analysis FAQ
Scheduled SQL tasks FAQ
Alarm FAQ
- Documentation
Torch Log ServiceUser GuideData collectionCloud product log collectionTrafficRoute DNS log collectionCollect TrafficRoute DNS logs
Copy page
Download PDFTrafficRoute DNS log collection
Collect TrafficRoute DNS logs
Copy pageDownload PDFCollect TrafficRoute DNS logs
This topic describes the features and collection methods related to Cloud DNS logs in the TrafficRoute DNS Suite.
Features overview
Volcengine Cloud DNS is an authoritative DNS service designed for internet domain names. Domain name instances with the flagship or premium edition support enabling access log functionality and can deliver access logs to TLS.
The related configuration is as follows:
Configuration | Description |
Configuration | Description |
Log type | TrafficRoute DNS access logs. |
Log storage location | When creating a log delivery task in TrafficRoute DNS, manually select the corresponding project and log topic. For details on managing log resources, see Manage TrafficRoute DNS log resources.
|
Log storage period |
|
Log shards |
|
Index settings | Configure indexes are automatically configured. |
Log fields |
Collect TrafficRoute DNS logs
For usage limits and instructions on delivering TrafficRoute DNS logs to TLS, see Deliver Access Logs to TLS.
TrafficRoute DNS log fields
The fields for TrafficRoute DNS access logs are as follows:
Field name | Description |
Field name | Description |
client_ecs_ip | The client IP address in the ECS protocol information contained in the DNS query request. If the DNS query request does not contain ECS protocol information, this field uses the value of the client_ip field. |
client_ecs_ip_info | The network line of the client IP in the ECS protocol information contained in the DNS query request. If the DNS query request does not contain ECS protocol information, this field typically refers to the network line of the outbound IP address of the Local DNS server. |
client_ecs_line_info | The network line configured by the user for the client IP in the ECS protocol information contained in the DNS query request. |
client_ip | The client IP address that Cloud DNS parses from the UDP packet of the DNS query request is typically the outgoing IP address of the Local DNS server. |
ds_req_target_domain | The target domain name of the DNS query request. |
ds_req_target_type | The record type for DNS query requests. |
ds_resp_code | DNS response code. |
ds_resp_content | DNS response content. |
server_proc_ts | The time recorded by the DNS server of Cloud DNS (UTC+8). |
- client_ecs_ip_info field description
- ParametersDescriptionParametersDescriptionContinentContinent. For example, AS refers to Asia.CountryCountry or region. For example, JP refers to Japan.ispCarrier. For example, TELECOM refers to China Telecom.provinceProvince. For example, HB refers to Hebei.scopeGeographical scope. For example, DOMESTIC refers to the Mainland of China.
- ds_resp_content field description
- ParametersDescriptionParametersDescriptionOwnerThe requested domain.rrtypeThe type of the DNS record.valuesThe value of the DNS record.
Last updated: 2026.08.13 11:04:47
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
