[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:dynamic-residential-failed":3,"blog-article:\u002Fblog\u002Fdynamic-residential-failed":856,"blog-related:\u002Fblog\u002Fdynamic-residential-failed":857,"blog-translations:\u002Fblog\u002Fdynamic-residential-failed":858},{"available":4,"article":5,"relatedArticles":236,"translations":698},true,{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":18,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":23,"bodyHtml":235},"strapi",2080,"oyqo5f9ffpwasyi3duwbm4qy","zh","dynamic-residential-failed","\u002Fblog\u002Fdynamic-residential-failed","动态住宅代理 IP 的并发数怎么评估：目标站、预算和失败率","动态住宅代理 IP 的并发数要结合目标站限制、程序资源、失败率和预算评估。本文说明如何用阶梯测试观察成功率、429、验证码、P95 响应和单位成功请求成本。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_ip_cover_a5e21de633.webp","2026-08-19T02:36:02.311Z","2026-08-19T02:36:02.290Z","Global Proxies Team",[],false,0,2,"blocks",[24,30,35,39,43,47,51,55,59,84,88,92,96,100,104,108,113,117,121,125,129,133,137,141,145,149,153,157,161,183,187,191,195,199,203,207,211,215,219,223,227,231],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"动态住宅代理 IP 的并发数不能只看机器性能或套餐上限。更可靠的方法是：**先用低并发建立目标站基线，再逐级加压，同时记录成功率、429、验证码、P95 响应时间、流量和单位成功请求成本**。当失败率或成本明显上升时回退一级，并为业务高峰保留余量。","text",{"type":31,"level":21,"children":32},"heading",[33],{"text":34,"type":29},"先估算起始并发",{"type":25,"children":36},[37],{"text":38,"type":29},"容量估算可以从一个简单公式开始。这里的“并发”是同一时间同时进行的请求数量，“QPS”是每秒完成的请求数量；“连接池”则是程序可以同时保持和复用的网络连接数量。",{"type":25,"children":40},[41],{"text":42,"type":29},"```text\n所需并发 ≈ 目标每秒请求数 × P95 响应时间（秒）\n```",{"type":25,"children":44},[45],{"text":46,"type":29},"例如，目标是每秒完成 5 个请求，低并发测试得到 P95 响应时间为 2 秒，估算起点约为 10 并发。这只是计算示例，不代表目标站允许的请求频率，也不能替代实际压测。这个公式只能告诉你从哪里开始测试，不能直接告诉你应该开到多少并发。",{"type":25,"children":48},[49],{"text":50,"type":29},"需要同时规划并发、QPS 与程序连接池时，可参考[代理 IP 并发、QPS 和连接池规划](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-ip-concurrency-qps-connection-pool)统一这些指标的口径。",{"type":31,"level":21,"children":52},[53],{"text":54,"type":29},"并发测试必须固定哪些变量",{"type":25,"children":56},[57],{"text":58,"type":29},"每一级测试应保持以下条件一致：",{"type":60,"format":61,"children":62},"list","unordered",[63,68,72,76,80],{"type":64,"children":65},"list-item",[66],{"text":67,"type":29},"相同目标 URL 和请求方法。",{"type":64,"children":69},[70],{"text":71,"type":29},"相同请求头、Cookie 与响应校验方式。",{"type":64,"children":73},[74],{"text":75,"type":29},"相同测试时长和地区。",{"type":64,"children":77},[78],{"text":79,"type":29},"相同超时、重试和退避策略。",{"type":64,"children":81},[82],{"text":83,"type":29},"相同的成功判定标准。",{"type":25,"children":85},[86],{"text":87,"type":29},"如果同时更换地区、请求结构和并发数，就无法判断失败来自并发、目标站还是代理 IP。这里的“请求结构”包括请求方法、请求头、Cookie 和返回校验方式。",{"type":25,"children":89},[90],{"text":91,"type":29},"测试使用的出口类型也应保持一致；需要轮换出口和多地区覆盖时，可先核对[动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)的产品说明。",{"type":31,"level":21,"children":93},[94],{"text":95,"type":29},"用阶梯方式增加并发",{"type":25,"children":97},[98],{"text":99,"type":29},"不要从 1 直接拉到套餐上限。可以按 1、2、5、10、20 等阶梯逐级测试，每一级运行足够时间以覆盖正常波动。",{"type":25,"children":101},[102],{"text":103,"type":29},"达到业务预设的失败率、429 或预算阈值时，停止继续加压，回退到上一个稳定等级。比如 5 并发时成功率稳定、10 并发开始出现 429，通常应把 5 并发视为当前稳定档位，而不是继续加压。阈值应由真实业务要求制定，不要为追求更高并发忽略目标站规则。",{"type":31,"level":21,"children":105},[106],{"text":107,"type":29},"怎么区分三类瓶颈",{"type":31,"level":109,"children":110},3,[111],{"text":112,"type":29},"目标站限流",{"type":25,"children":114},[115],{"text":116,"type":29},"并发或请求频率上升后 429、验证码明显增加，而程序和网络资源仍正常，更像目标站限流。应降低频率、增加合理间隔并遵守目标站使用规则。",{"type":31,"level":109,"children":118},[119],{"text":120,"type":29},"程序或本地资源瓶颈",{"type":25,"children":122},[123],{"text":124,"type":29},"CPU、内存、连接池或文件描述符接近上限，且直连测试也变慢，优先优化程序和机器资源。增加代理 IP 数量不会解决本地连接池不足。",{"type":31,"level":109,"children":126},[127],{"text":128,"type":29},"代理 IP 或链路瓶颈",{"type":25,"children":130},[131],{"text":132,"type":29},"相同程序和目标站下，只有某组代理 IP 的超时率或 P95 明显上升；更换同地区出口后恢复，才更像具体出口或链路问题。",{"type":31,"level":21,"children":134},[135],{"text":136,"type":29},"预算应该怎么算",{"type":25,"children":138},[139],{"text":140,"type":29},"不要只看流量单价。建议同时计算：",{"type":25,"children":142},[143],{"text":144,"type":29},"```text\n单位成功请求成本 = 本轮代理 IP 流量或套餐成本 ÷ 成功请求数\n```",{"type":25,"children":146},[147],{"text":148,"type":29},"重试、验证码页面和无效响应同样会消耗流量。并发提高后，如果总请求数增加但成功请求增长很少，单位成功请求成本通常会变差。",{"type":25,"children":150},[151],{"text":152,"type":29},"套餐、流量和单位成功成本需要一起比较时，可参考[代理 IP 价格和套餐怎么判断](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-ip-pricing-plan-selection)建立购买前测试口径。",{"type":25,"children":154},[155],{"text":156,"type":29},"需要连续测试时，可使用[30天动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential-30-day)记录跨时段波动；具体并发、流量和价格以当前产品页面与商务确认结果为准。",{"type":31,"level":21,"children":158},[159],{"text":160,"type":29},"什么时候不该继续加并发",{"type":60,"format":61,"children":162},[163,167,171,175,179],{"type":64,"children":164},[165],{"text":166,"type":29},"429 或验证码比例持续上升。",{"type":64,"children":168},[169],{"text":170,"type":29},"P95 和超时率明显恶化。",{"type":64,"children":172},[173],{"text":174,"type":29},"单位成功请求成本连续上升。",{"type":64,"children":176},[177],{"text":178,"type":29},"目标站关键步骤成功率下降。",{"type":64,"children":180},[181],{"text":182,"type":29},"本地 CPU、内存或连接池已接近上限。",{"type":25,"children":184},[185],{"text":186,"type":29},"此时应回退并发、检查请求结构和重试策略，而不是继续增加出口或并发。",{"type":25,"children":188},[189],{"text":190,"type":29},"并发越高不等于效率越高；当失败请求、重试和验证码增长时，表面请求量增加，真正完成的有效任务反而可能减少。",{"type":31,"level":21,"children":192},[193],{"text":194,"type":29},"常见问题",{"type":31,"level":109,"children":196},[197],{"text":198,"type":29},"并发数和每秒请求数是同一回事吗？",{"type":25,"children":200},[201],{"text":202,"type":29},"不是。并发表示同时进行的请求数量，每秒请求数还受响应时间影响；响应越慢，相同并发下完成的请求越少。",{"type":31,"level":109,"children":204},[205],{"text":206,"type":29},"动态住宅代理 IP 并发越高越好吗？",{"type":25,"children":208},[209],{"text":210,"type":29},"不是。并发超过目标站、本地程序或预算能够承受的范围后，失败率和单位成功成本可能上升。",{"type":31,"level":109,"children":212},[213],{"text":214,"type":29},"429 增加时应该立即换 IP 吗？",{"type":25,"children":216},[217],{"text":218,"type":29},"先降低请求频率并检查目标站规则。只换 IP 而保持不合理频率，问题可能继续出现。",{"type":31,"level":109,"children":220},[221],{"text":222,"type":29},"应该保留多少峰值余量？",{"type":25,"children":224},[225],{"text":226,"type":29},"没有统一比例。先通过跨时段测试找到稳定等级，再根据高峰波动和预算确定余量，不要用未经验证的固定百分比。",{"type":25,"children":228},[229],{"text":230,"type":29},"---",{"type":25,"children":232},[233],{"text":234,"type":29},"先用小样本和低并发跑完整阶梯，保存请求结构、测试时长、成功率、429、P95 和流量记录。需要协助时，通过[全球代理 FAQ](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F)提交脱敏结果。","",[237,392,538],{"source":6,"id":238,"documentId":239,"translationKey":239,"locale":9,"slug":240,"path":241,"_path":241,"title":242,"description":243,"excerpt":243,"image":244,"publishedAt":245,"updatedAt":246,"author":17,"tags":247,"featured":19,"sortOrder":20,"readingTime":109,"bodyType":22,"bodyBlocks":248,"bodyHtml":235},2086,"azci4x5s7h2sdoy025xyz4ad","api-ip-port-proxy-ip-guide","\u002Fblog\u002Fapi-ip-port-proxy-ip-guide","API 提取返回 IP:端口后怎么填到工具里？","API 返回 IP:端口后，要拆分主机和端口，并根据白名单或账号密码方式完成认证。本文说明不同工具的字段填写、HTTP\u002FSOCKS5 验证和常见连接失败排查。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_api_ip_cover_a732ecd583.webp","2026-08-19T02:38:23.025Z","2026-08-19T02:38:23.005Z",[],[249,253,257,261,265,269,273,277,281,285,289,294,298,302,306,310,314,318,322,326,330,334,338,342,346,350,353,357,361,365,369,373,377,381,385,388],{"type":25,"children":250},[251],{"text":252,"type":29},"API 提取返回的 `IP:端口` 要拆成两个字段填写：冒号前是**主机或代理 IP**，冒号后是**端口**。例如返回 `203.0.113.10:8000`，工具里的 Host\u002FIP 填 `203.0.113.10`，Port 填 `8000`。不要把整串内容粘到主机字段，也不要把冒号带进端口字段。你只需要记住三件事：冒号前填主机，冒号后填端口，是否填写账号密码要看产品的认证方式。",{"type":31,"level":21,"children":254},[255],{"text":256,"type":29},"先确认这条代理信息怎么认证",{"type":25,"children":258},[259],{"text":260,"type":29},"动态住宅代理 IP 的 API 提取通常配合白名单使用。白名单就是允许某个终端出口 IP 使用代理服务的认证方式。终端当前的公网出口 IP 已加入白名单后，提取到的每行 `IP:端口` 可直接连接，不需要再填账号和密码。若终端公网出口发生变化，应先更新白名单再重试。",{"type":25,"children":262},[263],{"text":264,"type":29},"如果产品页面明确提供主机、端口、账号和密码，则按账号密码方式填写。不要添加产品说明之外的配置项；普通 HTTP、HTTPS、SOCKS5 代理接入通常只涉及主机、端口、账号、密码或白名单。",{"type":25,"children":266},[267],{"text":268,"type":29},"不确定各字段分别代表什么时，先查看[代理参数说明](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fintro)，再按产品实际提供的认证方式填写。",{"type":31,"level":21,"children":270},[271],{"text":272,"type":29},"API 返回多行时怎么读取",{"type":25,"children":274},[275],{"text":276,"type":29},"API 一次提取多个代理 IP 时，常见结果是一行一个地址：",{"type":25,"children":278},[279],{"text":280,"type":29},"```text\n203.0.113.10:8000\n203.0.113.11:8000\n203.0.113.12:8000\n```",{"type":25,"children":282},[283],{"text":284,"type":29},"每一行都是一组独立的代理 IP 与端口。工具只允许填写一个代理时，先选其中一行测试；支持批量导入时，再按工具要求保留一行一条的格式。复制前应删除空格、引号、逗号和多余换行。",{"type":31,"level":21,"children":286},[287],{"text":288,"type":29},"不同工具里的字段怎么对应",{"type":290,"children":291},"code",[292],{"text":293,"type":29},"| API 返回内容 | 工具常见字段 | 示例 |\n| --- | --- | --- |\n| 冒号前的 IP | Host、Server、Proxy Host、主机 | `203.0.113.10` |\n| 冒号后的数字 | Port、Proxy Port、端口 | `8000` |\n| 产品说明的协议 | HTTP、HTTPS 或 SOCKS5 | 按产品说明选择 |\n| 账号密码 | Username\u002FPassword | 仅在该连接方式提供时填写 |",{"type":25,"children":295},[296],{"text":297,"type":29},"在指纹浏览器或代理客户端中，一般按“协议 → 主机 → 端口 → 认证”的顺序填写，保存后点击检查代理或启动连接。系统代理通常只有主机和端口字段；如果系统入口不支持认证，应改用支持相应认证方式的客户端。",{"type":25,"children":299},[300],{"text":301,"type":29},"不同系统和工具的具体入口可从[代理设置帮助](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings)选择对应教程，避免把其它客户端的字段位置直接套用过来。",{"type":31,"level":21,"children":303},[304],{"text":305,"type":29},"命令行和程序如何验证",{"type":25,"children":307},[308],{"text":309,"type":29},"先用出口检测页（用来查看目标网站实际看到哪个 IP 的检测页面）确认 IP 是否变化，再访问真实目标 URL。下面仅展示字段位置，地址需替换为实际提取结果。",{"type":25,"children":311},[312],{"text":313,"type":29},"HTTP 代理 IP 示例：",{"type":25,"children":315},[316],{"text":317,"type":29},"```bash\ncurl -x http:\u002F\u002F203.0.113.10:8000 https:\u002F\u002Fexample.com\n```",{"type":25,"children":319},[320],{"text":321,"type":29},"SOCKS5 且需要远端解析时，可使用支持远端 DNS 的写法：",{"type":25,"children":323},[324],{"text":325,"type":29},"```bash\ncurl --proxy socks5h:\u002F\u002F203.0.113.10:8000 https:\u002F\u002Fexample.com\n```",{"type":25,"children":327},[328],{"text":329,"type":29},"不要只看命令是否返回内容。还要核对出口 IP、目标站状态码、地区展示和关键业务步骤。",{"type":31,"level":21,"children":331},[332],{"text":333,"type":29},"常见失败怎么排查",{"type":290,"children":335},[336],{"text":337,"type":29},"| 现象 | 优先检查 | 下一步 |\n| --- | --- | --- |\n| 工具提示格式错误 | 是否把 `IP:端口` 整串填进一个字段 | 拆分主机和端口 |\n| 连接超时 | 本地网络、海外网络环境、端口可达性、资源有效期 | 换网络或重新提取后复测 |\n| 407 或认证失败 | 账号密码是否正确，或白名单是否匹配当前公网出口 | 重新复制凭据或更新白名单 |\n| 连接成功但出口没变 | 工具是否已启用、代理是否覆盖目标应用 | 检查代理覆盖范围和系统代理冲突 |\n| 刚才可用、稍后失效 | 提取结果是否已过有效期 | 重新调用 API 获取新结果 |\n| 只有目标站失败 | 状态码、地区限制、Cookie、账号状态和访问频率 | 固定变量后测试同地区另一代理 IP |",{"type":25,"children":339},[340],{"text":341,"type":29},"如果问题集中在认证环节，可先核对[白名单和账号密码的区别](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-whitelist-vs-username-password)，确认当前连接是否还需要填写账号密码。",{"type":31,"level":21,"children":343},[344],{"text":345,"type":29},"从填写到验证的完整流程",{"type":25,"children":347},[348],{"text":349,"type":29},"1. 在[动态住宅 API 提取教程](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FGet-Proxy\u002FDynamic-flow-api-ip)确认提取参数、协议和有效期。\n2. 将终端公网出口加入白名单，再调用 API 获取 `IP:端口`。\n3. 把 IP 与端口拆开填入工具，选择产品支持的协议。\n4. 保存并启用连接，先检查出口 IP 是否变化。\n5. 再测试目标 URL、状态码、地区结果和失效时间。",{"type":31,"level":21,"children":351},[352],{"text":194,"type":29},{"type":31,"level":109,"children":354},[355],{"text":356,"type":29},"IP:端口可以整串粘贴吗？",{"type":25,"children":358},[359],{"text":360,"type":29},"只有工具明确提供“批量导入”或“代理地址”输入框时才可能支持。普通主机和端口字段必须拆开填写。",{"type":31,"level":109,"children":362},[363],{"text":364,"type":29},"API 提取后为什么没有账号密码？",{"type":25,"children":366},[367],{"text":368,"type":29},"白名单方式下，系统根据终端公网出口识别权限，提取到的 `IP:端口` 通常可直接使用。应先确认当前终端已经加入白名单。",{"type":31,"level":109,"children":370},[371],{"text":372,"type":29},"为什么同一条代理信息过一会儿不能用了？",{"type":25,"children":374},[375],{"text":376,"type":29},"动态住宅代理 IP 的 API 提取结果通常有有效期。记录提取时间和失效时间，过期后重新获取，不要继续重复测试旧地址。",{"type":31,"level":109,"children":378},[379],{"text":380,"type":29},"配置完成后怎样确认生效？",{"type":25,"children":382},[383],{"text":384,"type":29},"先确认出口检测页显示的 IP 已改变，再验证真实目标站的状态码、地区展示和关键步骤。",{"type":25,"children":386},[387],{"text":230,"type":29},{"type":25,"children":389},[390],{"text":391,"type":29},"配置失败时，准备脱敏后的 API 返回格式、使用工具、协议、错误码、提取时间和出口检测结果，再通过[全球代理 FAQ](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F)定位对应问题。",{"source":6,"id":393,"documentId":394,"translationKey":394,"locale":9,"slug":395,"path":396,"_path":396,"title":397,"description":398,"excerpt":398,"image":399,"publishedAt":400,"updatedAt":401,"author":17,"tags":402,"featured":19,"sortOrder":20,"readingTime":109,"bodyType":22,"bodyBlocks":403,"bodyHtml":235},2085,"n8u852zjoo2vdkbb6fo5miy2","browserleaks-ip-webrtc-dns-proxy-troubleshooting","\u002Fblog\u002Fbrowserleaks-ip-webrtc-dns-proxy-troubleshooting","BrowserLeaks 看到真实 IP 怎么办？WebRTC、DNS 和系统代理排查","BrowserLeaks 看到真实 IP 时，应先区分 HTTP 出口、WebRTC 和 DNS 问题。本文说明如何检查浏览器代理、远端 DNS、WebRTC 地址和系统代理冲突，并确认修复结果。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_browserleaks_ip_webrtc_dns_cover_94b716144a.webp","2026-08-19T02:37:56.370Z","2026-08-19T02:37:56.352Z",[],[404,408,412,416,420,424,428,432,436,440,444,448,452,456,460,464,468,472,476,480,484,488,492,496,499,503,507,511,515,519,523,527,531,534],{"type":25,"children":405},[406],{"text":407,"type":29},"BrowserLeaks 显示真实公网 IP 时，先判断泄漏发生在 **HTTP 出口、WebRTC 还是 DNS**。HTTP 出口指网页请求最终从哪个 IP 发出；WebRTC 是浏览器用于实时音视频通信的功能，可能暴露额外地址；DNS 是把网址转换成 IP 的查询过程。三类结果来自不同网络环节：HTTP 出口仍是本地公网 IP，通常说明代理没有覆盖当前浏览器；WebRTC 出现本地候选地址不一定等于公网 IP 泄漏；DNS 显示本地运营商，则要检查解析是否走远端。不要一看到地址不同就连续更换代理 IP。",{"type":31,"level":21,"children":409},[410],{"text":411,"type":29},"先看哪一项最关键",{"type":290,"children":413},[414],{"text":415,"type":29},"| 检测结果 | 可能含义 | 优先处理位置 |\n| --- | --- | --- |\n| HTTP\u002FIP 页面仍显示本地公网 IP | 浏览器没有走代理或规则未覆盖该页面 | 系统代理、浏览器扩展、客户端接管范围 |\n| WebRTC 显示本地网段地址 | 浏览器暴露了局域网候选地址 | 浏览器 WebRTC 设置；先确认是否同时出现本地公网 IP |\n| WebRTC 显示本地公网 IP | WebRTC 流量可能绕开代理 | 浏览器策略、扩展冲突、客户端 UDP\u002FWebRTC 支持 |\n| DNS 显示本地运营商 | DNS 请求仍由本地网络解析 | 远端 DNS、DoH、SOCKS5 远端解析设置 |",{"type":25,"children":417},[418],{"text":419,"type":29},"应先解决 HTTP 出口没有变化的问题。只有浏览器请求已经从代理 IP 出口发出，继续检查 WebRTC 和 DNS 才有意义。",{"type":31,"level":109,"children":421},[422],{"text":423,"type":29},"第一步：确认 HTTP 出口是否已变化",{"type":25,"children":425},[426],{"text":427,"type":29},"1. 记录未启用代理前的本地公网 IP。\n2. 启用代理客户端或浏览器扩展，确认配置已保存并生效。\n3. 重新打开无痕窗口访问 IP 检测页。\n4. 对比检测结果是否变成购买或提取到的代理 IP 地区。",{"type":25,"children":429},[430],{"text":431,"type":29},"如果仍是本地公网 IP，依次检查协议、主机、端口和认证信息，再确认目标浏览器是否包含在代理实际覆盖的应用和网页范围内。系统代理与浏览器扩展同时运行时，应暂时关闭其中一层做单独测试，避免规则互相覆盖。",{"type":25,"children":433},[434],{"text":435,"type":29},"如果容易混淆连接地址与实际出口，可以先确认[代理主机、端口和出口 IP 的区别](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-host-port-exit-ip-difference)，再对照检测页结果。",{"type":31,"level":109,"children":437},[438],{"text":439,"type":29},"第二步：判断 WebRTC 地址是否真的泄漏",{"type":25,"children":441},[442],{"text":443,"type":29},"WebRTC 页面可能列出多种候选地址。`192.168.x.x`、`10.x.x.x` 或 `172.16.x.x—172.31.x.x` 属于常见本地网段，和运营商分配的公网 IP 不是一回事。",{"type":25,"children":445},[446],{"text":447,"type":29},"需要重点处理的是：HTTP 出口已经是代理 IP，但 WebRTC 结果同时出现了启用代理前记录的本地公网 IP。此时可以在浏览器隐私设置、企业策略或可信扩展中限制 WebRTC 暴露范围，然后关闭浏览器并重新测试。不要安装来源不明的扩展，也不要把“彻底关闭 WebRTC”当成所有浏览器的统一答案；视频会议等功能可能因此受影响。",{"type":31,"level":109,"children":449},[450],{"text":451,"type":29},"第三步：检查 DNS 是否走远端解析",{"type":25,"children":453},[454],{"text":455,"type":29},"DNS 显示本地运营商不一定说明网页请求没有经过代理 IP，但可能暴露本地解析路径，也就是 DNS 请求仍由本地网络完成。检查顺序如下：",{"type":25,"children":457},[458],{"text":459,"type":29},"1. 确认代理客户端是否提供“远端 DNS”或“通过代理解析”选项。\n2. SOCKS5 工具中区分本地解析与远端解析；程序测试可用支持远端 DNS 的 `socks5h`，其中 `h` 表示由远端解析域名。\n3. 检查浏览器 DoH（通过 HTTPS 发起 DNS 查询的方式）设置是否与客户端策略冲突。\n4. 修改后关闭浏览器、清理 DNS 缓存，再使用同一检测页复测。",{"type":25,"children":461},[462],{"text":463,"type":29},"最终应同时记录 HTTP 出口、WebRTC 公网地址和 DNS 运营商，不能只截取其中一项下结论。",{"type":25,"children":465},[466],{"text":467,"type":29},"DNS 结果仍显示本地网络时，可继续按[DNS 显示本地运营商怎么判断](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fdns-local-proxy)做分层检查。",{"type":31,"level":21,"children":469},[470],{"text":471,"type":29},"系统代理和浏览器代理怎么做对照",{"type":290,"children":473},[474],{"text":475,"type":29},"| 测试轮次 | 系统代理 | 浏览器扩展 | 要观察的结果 |\n| --- | --- | --- | --- |\n| A | 关闭 | 关闭 | 记录本地公网 IP 与 DNS 基线 |\n| B | 开启 | 关闭 | 判断系统代理是否接管浏览器 |\n| C | 关闭 | 开启 | 判断浏览器扩展是否单独有效 |\n| D | 开启 | 开启 | 仅用于确认是否存在规则冲突 |",{"type":25,"children":477},[478],{"text":479,"type":29},"每轮都使用相同浏览器、检测页和网络环境。若 B、C 单独正常而 D 异常，优先处理双重代理或规则冲突，而不是更换代理 IP。",{"type":25,"children":481},[482],{"text":483,"type":29},"需要核对系统或具体客户端入口时，可从[代理设置帮助](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings)进入对应设备教程。",{"type":31,"level":21,"children":485},[486],{"text":487,"type":29},"什么时候换代理 IP 没用",{"type":25,"children":489},[490],{"text":491,"type":29},"HTTP 出口仍是本地公网 IP、只有某个浏览器异常，或关闭冲突扩展后恢复，说明问题主要在本机配置。更换代理 IP 不会改变接管范围、WebRTC 策略或 DNS 设置。",{"type":25,"children":493},[494],{"text":495,"type":29},"只有参数和接管范围确认无误，同地区某个代理 IP 持续无法连接或地区长期错误，而替换同地区代理 IP 后恢复，才值得继续排查具体出口。",{"type":31,"level":21,"children":497},[498],{"text":194,"type":29},{"type":31,"level":109,"children":500},[501],{"text":502,"type":29},"WebRTC 出现 192.168 开头的地址要紧吗？",{"type":25,"children":504},[505],{"text":506,"type":29},"这是常见局域网地址，不等同于运营商公网 IP。应对照启用代理前记录的公网 IP，确认它是否也出现在结果中。",{"type":31,"level":109,"children":508},[509],{"text":510,"type":29},"DNS 显示本地运营商就代表代理没生效吗？",{"type":25,"children":512},[513],{"text":514,"type":29},"不一定。先看 HTTP 出口是否已经变化，再单独检查 DNS 是否通过代理或远端服务解析。",{"type":31,"level":109,"children":516},[517],{"text":518,"type":29},"为什么无痕窗口和普通窗口结果不同？",{"type":25,"children":520},[521],{"text":522,"type":29},"普通窗口可能保留 Cookie、缓存或扩展权限，无痕窗口也可能默认禁用部分扩展。应检查扩展是否获准在无痕模式运行。",{"type":31,"level":109,"children":524},[525],{"text":526,"type":29},"修复后怎么确认问题已解决？",{"type":25,"children":528},[529],{"text":530,"type":29},"重新打开浏览器，依次记录 HTTP 出口、WebRTC 公网地址和 DNS 结果，并用真实目标 URL 复测。",{"type":25,"children":532},[533],{"text":230,"type":29},{"type":25,"children":535},[536],{"text":537,"type":29},"保存修改前后的检测结果、浏览器版本、代理方式和扩展列表。如果仍无法定位，可参考[BrowserLeaks 真实 IP 与 DNS 排查说明](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fbrowserleaks-real-ip-dns-local)或通过[全球代理 FAQ](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F)继续排查。",{"source":6,"id":539,"documentId":540,"translationKey":540,"locale":9,"slug":541,"path":542,"_path":542,"title":543,"description":544,"excerpt":544,"image":545,"publishedAt":546,"updatedAt":547,"author":17,"tags":548,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":549,"bodyHtml":235},2084,"weegjjnlgjn55jccuh4xwhnd","dns-local-proxy","\u002Fblog\u002Fdns-local-proxy","DNS 显示本地运营商是不是代理没生效？","DNS 显示本地运营商不一定代表代理 IP 失效，需先确认网页出口是否变化，再检查远端 DNS、DoH 和浏览器设置。本文提供分层判断和复测步骤。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_dns_cover_e8966d312c.webp","2026-08-19T02:37:39.302Z","2026-08-19T02:37:39.280Z",[],[550,554,558,562,566,570,574,578,582,586,590,594,612,616,620,624,628,632,636,640,644,648,652,656,659,663,667,671,675,679,683,687,691,694],{"type":25,"children":551},[552],{"text":553,"type":29},"**DNS 显示本地运营商，不一定代表代理 IP 没生效。**先看网页出口 IP 是否已经变成代理 IP：出口已变化而 DNS 仍显示本地运营商，通常是解析仍走本地网络；出口也没变化，则应先检查代理是否覆盖当前应用。简单判断就是：出口没变，先查代理；出口变了但 DNS 没变，再查 DNS；两者都变了而目标站仍显示错误地区，再查目标站自己的 IP 库、Cookie 或账号资料。",{"type":31,"level":21,"children":555},[556],{"text":557,"type":29},"三个结果要分开判断",{"type":290,"children":559},[560],{"text":561,"type":29},"| 检查项 | 它说明什么 | 不能单独证明什么 |\n| --- | --- | --- |\n| 网页出口 IP | 当前网页请求从哪里发出 | 不能证明 DNS 一定走远端 |\n| DNS 服务器或运营商 | 域名由谁解析 | 不能单独证明网页没有走代理 |\n| 目标站地区展示 | 目标站结合自身数据后的判断 | 不能代表所有 IP 库都会一致 |",{"type":25,"children":563},[564],{"text":565,"type":29},"排查时同时记录这三项。只看 DNS 检测页的一行运营商名称，容易把解析问题误判成代理连接失败。",{"type":31,"level":21,"children":567},[568],{"text":569,"type":29},"DNS 显示本地运营商的排查步骤",{"type":31,"level":109,"children":571},[572],{"text":573,"type":29},"1. 确认出口 IP 是否变化",{"type":25,"children":575},[576],{"text":577,"type":29},"先记录未启用代理前的本地公网 IP，再启用代理并重新访问 IP 检测页。如果仍显示本地公网 IP，检查协议、主机、端口、认证信息以及代理是否覆盖当前浏览器或应用。",{"type":25,"children":579},[580],{"text":581,"type":29},"如果出口已经变化，再继续查 DNS。此时反复更换代理 IP 通常没有帮助，因为问题更可能出在客户端的解析方式。",{"type":25,"children":583},[584],{"text":585,"type":29},"若出口检测、WebRTC 和 DNS 结果同时出现异常，可先参考[BrowserLeaks 真实 IP 或 DNS 排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fbrowserleaks-real-ip-dns-webrtc-leak)区分问题所在环节。",{"type":31,"level":109,"children":587},[588],{"text":589,"type":29},"2. 确认工具是否支持远端解析",{"type":25,"children":591},[592],{"text":593,"type":29},"不同工具处理 DNS（把网址转换成 IP 的查询过程）的方式不同：",{"type":60,"format":61,"children":595},[596,600,604,608],{"type":64,"children":597},[598],{"text":599,"type":29},"系统代理可能只接管 HTTP\u002FHTTPS 流量，DNS 仍由系统网络处理。",{"type":64,"children":601},[602],{"text":603,"type":29},"浏览器可能启用了自己的安全 DNS 或 DoH（通过 HTTPS 发起 DNS 查询的方式），结果未必跟随系统代理。",{"type":64,"children":605},[606],{"text":607,"type":29},"SOCKS5 客户端可能区分本地解析和远端解析；程序中常用 `socks5h` 表示由远端解析，其中 `h` 表示远端解析域名。",{"type":64,"children":609},[610],{"text":611,"type":29},"部分代理扩展只对匹配规则的网页生效，检测页可能没有被同一规则覆盖。",{"type":25,"children":613},[614],{"text":615,"type":29},"应以工具的实际设置和官方说明为准，不要假设所有客户端都自动代理 DNS。如果只在某个浏览器里出现问题，优先检查浏览器扩展、缓存和安全 DNS，不要先更换代理 IP。",{"type":25,"children":617},[618],{"text":619,"type":29},"不确定当前工具应使用哪种接入方式时，可先查看[HTTP、HTTPS、SOCKS5 代理怎么选](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fhttp-https-socks5-proxy-selection)，再核对是否支持远端解析。",{"type":31,"level":109,"children":621},[622],{"text":623,"type":29},"3. 排除系统、浏览器和扩展冲突",{"type":25,"children":625},[626],{"text":627,"type":29},"1. 暂时关闭其它代理扩展或网络接管工具。\n2. 分别测试“只开系统代理”和“只开浏览器代理”。\n3. 检查浏览器 DoH 与客户端远端 DNS 是否互相覆盖。\n4. 修改设置后关闭浏览器，并清理 DNS 缓存再复测。",{"type":25,"children":629},[630],{"text":631,"type":29},"Windows 可在管理员终端执行 `ipconfig \u002Fflushdns` 清理系统 DNS 缓存；浏览器自身缓存还需通过浏览器设置或重启处理。",{"type":31,"level":21,"children":633},[634],{"text":635,"type":29},"如何判断是哪一层的问题",{"type":290,"children":637},[638],{"text":639,"type":29},"| 现象 | 更可能的问题层 | 下一步 |\n| --- | --- | --- |\n| 出口 IP 和 DNS 都是本地 | 代理未覆盖当前应用或配置未生效 | 查主机、端口、认证和代理覆盖范围 |\n| 出口是代理 IP，DNS 是本地运营商 | DNS 仍在本地解析 | 开启远端 DNS或检查 DoH |\n| 出口和 DNS 都变化，目标站地区仍错误 | 目标站 IP 库、Cookie 或账号资料 | 无痕测试并对比目标站实际展示 |\n| 只有一个浏览器异常 | 浏览器扩展、权限或缓存 | 与其它浏览器做对照 |",{"type":25,"children":641},[642],{"text":643,"type":29},"如果表格中的对照仍无法确定问题更可能出在哪一环，可进入[代理 IP 故障排查中心](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-ip-troubleshooting-hub)按连接、认证、DNS 和目标站问题继续分流。",{"type":31,"level":21,"children":645},[646],{"text":647,"type":29},"什么时候需要换代理 IP",{"type":25,"children":649},[650],{"text":651,"type":29},"同一客户端配置下，只有某个代理 IP 的目标地区长期识别错误，而替换同地区代理 IP 后恢复，可以继续检查具体出口。",{"type":25,"children":653},[654],{"text":655,"type":29},"如果所有代理 IP 都显示相同的本地 DNS，优先修复解析和接管设置。账号资料、Cookie 或目标站自己的地区规则也不会因为连续更换代理 IP 自动消失。",{"type":31,"level":21,"children":657},[658],{"text":194,"type":29},{"type":31,"level":109,"children":660},[661],{"text":662,"type":29},"DNS 运营商必须和代理 IP 运营商相同吗？",{"type":25,"children":664},[665],{"text":666,"type":29},"不一定。DNS 服务可能来自公共解析服务、浏览器 DoH 或客户端指定的解析器，名称无需与代理 IP 所属运营商完全相同。",{"type":31,"level":109,"children":668},[669],{"text":670,"type":29},"出口 IP 已变化，还需要处理 DNS 吗？",{"type":25,"children":672},[673],{"text":674,"type":29},"如果业务对地区一致性或环境隔离要求较高，建议继续检查；普通连通性测试则应以目标站实际结果为准。",{"type":31,"level":109,"children":676},[677],{"text":678,"type":29},"为什么不同检测网站结果不同？",{"type":25,"children":680},[681],{"text":682,"type":29},"检测网站使用的数据库、测试域名和判断方法不同。应保持同一网络和客户端，记录多个结果而不是只看一次。",{"type":31,"level":109,"children":684},[685],{"text":686,"type":29},"修改后怎么复测？",{"type":25,"children":688},[689],{"text":690,"type":29},"清理缓存并重启浏览器，依次记录出口 IP、DNS 结果和目标站地区展示，确认只有一个变量发生变化。",{"type":25,"children":692},[693],{"text":230,"type":29},{"type":25,"children":695},[696],{"text":697,"type":29},"保存出口 IP、DNS 运营商、客户端名称、协议和修改前后截图。仍无法定位时，可通过[全球代理 FAQ](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F)查找对应设置与排障入口。",[699],{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":700,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":701,"bodyHtml":235},[],[702,705,708,711,714,717,720,723,726,743,746,749,752,755,758,761,764,767,770,773,776,779,782,785,788,791,794,797,800,817,820,823,826,829,832,835,838,841,844,847,850,853],{"type":25,"children":703},[704],{"text":28,"type":29},{"type":31,"level":21,"children":706},[707],{"text":34,"type":29},{"type":25,"children":709},[710],{"text":38,"type":29},{"type":25,"children":712},[713],{"text":42,"type":29},{"type":25,"children":715},[716],{"text":46,"type":29},{"type":25,"children":718},[719],{"text":50,"type":29},{"type":31,"level":21,"children":721},[722],{"text":54,"type":29},{"type":25,"children":724},[725],{"text":58,"type":29},{"type":60,"format":61,"children":727},[728,731,734,737,740],{"type":64,"children":729},[730],{"text":67,"type":29},{"type":64,"children":732},[733],{"text":71,"type":29},{"type":64,"children":735},[736],{"text":75,"type":29},{"type":64,"children":738},[739],{"text":79,"type":29},{"type":64,"children":741},[742],{"text":83,"type":29},{"type":25,"children":744},[745],{"text":87,"type":29},{"type":25,"children":747},[748],{"text":91,"type":29},{"type":31,"level":21,"children":750},[751],{"text":95,"type":29},{"type":25,"children":753},[754],{"text":99,"type":29},{"type":25,"children":756},[757],{"text":103,"type":29},{"type":31,"level":21,"children":759},[760],{"text":107,"type":29},{"type":31,"level":109,"children":762},[763],{"text":112,"type":29},{"type":25,"children":765},[766],{"text":116,"type":29},{"type":31,"level":109,"children":768},[769],{"text":120,"type":29},{"type":25,"children":771},[772],{"text":124,"type":29},{"type":31,"level":109,"children":774},[775],{"text":128,"type":29},{"type":25,"children":777},[778],{"text":132,"type":29},{"type":31,"level":21,"children":780},[781],{"text":136,"type":29},{"type":25,"children":783},[784],{"text":140,"type":29},{"type":25,"children":786},[787],{"text":144,"type":29},{"type":25,"children":789},[790],{"text":148,"type":29},{"type":25,"children":792},[793],{"text":152,"type":29},{"type":25,"children":795},[796],{"text":156,"type":29},{"type":31,"level":21,"children":798},[799],{"text":160,"type":29},{"type":60,"format":61,"children":801},[802,805,808,811,814],{"type":64,"children":803},[804],{"text":166,"type":29},{"type":64,"children":806},[807],{"text":170,"type":29},{"type":64,"children":809},[810],{"text":174,"type":29},{"type":64,"children":812},[813],{"text":178,"type":29},{"type":64,"children":815},[816],{"text":182,"type":29},{"type":25,"children":818},[819],{"text":186,"type":29},{"type":25,"children":821},[822],{"text":190,"type":29},{"type":31,"level":21,"children":824},[825],{"text":194,"type":29},{"type":31,"level":109,"children":827},[828],{"text":198,"type":29},{"type":25,"children":830},[831],{"text":202,"type":29},{"type":31,"level":109,"children":833},[834],{"text":206,"type":29},{"type":25,"children":836},[837],{"text":210,"type":29},{"type":31,"level":109,"children":839},[840],{"text":214,"type":29},{"type":25,"children":842},[843],{"text":218,"type":29},{"type":31,"level":109,"children":845},[846],{"text":222,"type":29},{"type":25,"children":848},[849],{"text":226,"type":29},{"type":25,"children":851},[852],{"text":230,"type":29},{"type":25,"children":854},[855],{"text":234,"type":29},null,[],[]]