DNS issues for certain customers - not sure how to fix

Hi, I used to have the DNS and domain for my getadelante.com site and subdomain hosted by 1&1. I migrated the DNS to cloudflare last week, and it's now showing up as propagated.
However, some customers are still getting non-existent domain errors when accessing my site or subdomains - what can I dig into to try and solve it? it seems to be a subset of customers in the US that are behind a VPN/security tool. Once they disable the VPN/security limitations it normally works. Specifically, this customer is also using Cloudflare for their network management. Thanks
No description
5 Replies
SuperHelpflare
SuperHelpflare2mo ago
Feedback
Feedback has been submitted! Thank you :)
spiritk51421
spiritk51421OP2mo ago
it already propgated, it's been a week.
DarkDeviL
DarkDeviL2mo ago
As you're mentioning "customer"; - get the customer(s), that are having these problem(s) to also run: 1. nslookup -class=CHAOS -type=TXT id.server 1.1.1.1 2. tracert 1.1.1.1 3. nslookup -class=CHAOS -type=TXT id.server 8.8.8.8 4. tracert 8.8.8.8 And also report back with that information.
spiritk51421
spiritk51421OP2mo ago
what does it do? here it is Microsoft Windows [Version 10.0.26100.4946] (c) Microsoft Corporation. All rights reserved. C:\Users>nslookup -q=class=CHAOS -type=TXT id.server 1.1.1.1 Server: Unknown Address: 1.1.1.1 *** Unknown can't find id.server: Non-existent domain C:\Users>tracert 1.1.1.1 Tracing route to one.one.one.one [1.1.1.1] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.254 2 4 ms 6 ms 5 ms 108-67-164-1.lightspeed.hstntx.sbcglobal.net [108.67.164.1] 3 5 ms 5 ms 5 ms 71.149.7.166 4 8 ms 7 ms 8 ms 32.130.20.42 5 * * * Request timed out. 6 6 ms 7 ms * 32.130.20.14 7 8 ms 9 ms 9 ms 32.130.16.255 8 36 ms 10 ms 13 ms 141.101.74.63 9 13 ms 13 ms 11 ms one.one.one.one [1.1.1.1] Trace complete. C:\Users>tracert 8.8.8.8 Tracing route to dns.google [8.8.8.8] over a maximum of 30 hops: 1 3 ms 1 ms 3 ms 192.168.1.254 2 5 ms 3 ms 3 ms 108-67-164-1.lightspeed.hstntx.sbcglobal.net [108.67.164.1] 3 35 ms 9 ms 5 ms 71.149.7.166 4 56 ms 12 ms 7 ms 32.130.20.42 5 * * * Request timed out. 6 7 ms 6 ms * 32.130.20.14 7 11 ms 11 ms 11 ms 32.130.17.87 8 12 ms 12 ms 11 ms 108.170.231.44 9 36 ms 13 ms 12 ms 142.250.46.47 10 12 ms 15 ms 8 ms dns.google [8.8.8.8] Trace complete.
DarkDeviL
DarkDeviL2mo ago
Is this trace from a different network, than the first screenshot you attached? And are you still seeing issues?

Did you find this page helpful?