Recent posts

This would be the DNS server you're querying, and if you didn't enter one in the tool, it would be the default DNS server for your phone, which should then be displayed as placeholder text in the DNS server field.

If you're trying to query an authoritative DNS server for a domain it does not handle, this is the response you will receive. A few other rare cases it's a non-recoverable error on the remote server, or it has no answer to give you, and doesn't want to return NXDOMAIN instead for some reason.

#54

General Questions & Suggestions / DNS: vague error message "Serv...

Last post by minfrin - October 07, 2023, 05:04:08 AM

While the he.net app is normally very good, I've found a bug in the DNS troubleshooting section.

When encountering an error, it reports "Server rejected query", without telling us which server rejected the query, or what the nature was of the rejection.

Without knowing the server's IP address, this is impossible to troubleshoot.

#55

Questions & Answers / Are there other BGP tunnel pro...

Last post by cjy666 - September 30, 2023, 02:47:33 AM

Hello,Are there other free BGP tunnel providers after he.net do not provide free BGP tunnel?

#56

Questions & Answers / Timeout and poor ping time to ...

Last post by jlde - September 11, 2023, 08:31:14 AM

Hello,
I use the tunnel broker service for a 6in4 tunnel. It's a great service which works very well. But now I get al lot of timeouts during my work over IPv6. The IPv4 connection to the tunnel server shows altough timeouts and poor ping times to the location in Frankfurt. Are there any known issues regarding the location? Any others having trouble with the Frankfurt node?

Here is a ping output:

Ping statistics for 216.66.80.30:
Packets: Sent = 100, Received = 89, Lost = 11 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 226ms, Average = 27ms

And here a traceroute output:
Tracing route to tserv1.fra1.he.net [216.66.80.30]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.101.1
2 2 ms 2 ms 2 ms 192.168.2.1
3 * * * Request timed out.
4 7 ms 6 ms 6 ms 88.79.8.22
5 7 ms 7 ms 7 ms 188.111.161.8
6 * * * Request timed out.
7 8 ms 8 ms 38 ms port-channel16.core2.fra1.he.net [184.104.231.45]
8 80 ms * 8 ms port-channel16.core2.fra1.he.net [184.104.231.45]
9 7 ms 7 ms 7 ms tserv1.fra1.he.net [216.66.80.30]

Best regards Jörg

#57

Questions & Answers / Re: Packet loss e0-30.core2.lo...

Last post by lewislfoster - September 08, 2023, 01:35:36 PM

For the past few months ive been seeing consistent 5-10% packet loss to e0-19.core2.lon2.he.net both through tunnel broker and native IPv6 from linode. Before i tried to ping from linode i thought it might have been something to do with virgin media but it appears to not be

#58

Questions & Answers / Re: Google forcing ReCAPTCHA o...

Last post by Jenick - September 08, 2023, 12:10:58 PM

If it helps, HE.net support told me to change my LAN side networks to my /48 routed, not the /64 default they hand you when you first created your tunnel. However, if you're running pfSense and pfBlockerNG you can give this a try... https://github.com/pahtzo/hurricane-tunnel-dohdot The main issue I believe is chromium based browsers have their own built-in DNS client which automatically goes for DOH-DOT by default and maybe not even against your system based DNS servers. I've disabled my pfBlockerNG no-AAAA for google.com and www.google.com but retained my Windows 10 registry settings to disable the built-in DOH-DOT in Brave, Chrome, and Edge. Still working just fine.

#59

Questions & Answers / Re: Google forcing ReCAPTCHA o...

Last post by supergvozd - September 08, 2023, 05:08:20 AM

Quote from: doktornotor on September 08, 2023, 01:03:18 AM#metoo again - and yeah, the IPv6 no-AAAA hack still works.

More details please

#60

Questions & Answers / Re: Google forcing ReCAPTCHA o...

Last post by doktornotor - September 08, 2023, 01:03:18 AM

#metoo again - and yeah, the IPv6 no-AAAA hack still works.

Sigh.

Pages 1 ... 4 5 6 7 8 ... 10