Recent posts

[IPv4]

#1

IPv6 on Windows / Re: unreachable from outside

Last post by cnsh - March 14, 2026, 06:55:02 AM

what do you mean by 41 for IPv4? There isn't a selection for which whether I accept 41 on IPv4 or IPv6. Just a "Protocol 41".
Can you tell me where I can allow protocol 41 on IPv4? redefining doesn't help...

#2

IPv6 on Windows / Re: unreachable from outside

Last post by snarked - March 14, 2026, 12:55:02 AM

I have protocol 41 Core Networking enabled, I have no idea about 41 for IPv4...
Both inbound and outbound protocol 41 rules are set.

Protocol 41 has to be allowed for IPv4.  Unless you are also doing IPv6 in IPv6, it need not be allowed for IPv6.

#3

IPv6 on Windows / Re: unreachable from outside

Last post by cnsh - March 12, 2026, 09:30:04 PM

I changed the tunnel to london, and this problem reoccurs. Even when I turn edge traversing on. Same issue happens, everything works fine and the port is reachable when the firewall is down, but not when it's up.

#4

IPv6 Basics & Questions & General Chatter / Re: TunnelBroker.net domain ex...

Last post by idealneck - March 11, 2026, 05:30:43 AM

P.S. HE support is already aware so don't bother them with emails

#5

IPv6 Basics & Questions & General Chatter / Re: TunnelBroker.net domain ex...

Last post by idealneck - March 11, 2026, 05:16:01 AM

To keep DDNS working you can add the following to your /etc/hosts:

Code Select Expand

64.62.200.2 tunnelbroker.net ipv4.tunnelbroker.net www.tunnelbroker.net

Retrieved via

Code Select Expand

dig @ns1.he.net tunnelbroker.net

#6

IPv6 Basics & Questions & General Chatter / TunnelBroker.net domain expire...

Last post by idealneck - March 11, 2026, 05:11:12 AM

Seems like HE forgot to renew their TunnelBroker.net domain :(

#7

IPv6 on Windows / Re: unreachable from outside

Last post by cnsh - March 07, 2026, 06:22:48 PM

I could solve the issue by allowing edge traversal on Core Networking protocol 41 firewall rule. And, I have moved my tunnel's endpoint to a physically closer geolocation, Hongkong.

#8

IPv6 on Windows / Re: unreachable from outside

Last post by cnsh - March 01, 2026, 04:38:50 AM

I have protocol 41 Core Networking enabled, I have no idea about 41 for IPv4...
Both inbound and outbound protocol 41 rules are set.

#9

General Questions & Suggestions / Re: SOA EXPIRE number is: 3600...

Last post by dizik - February 28, 2026, 05:48:04 AM

Thank you.

[SUGGESTS]

#10

General Questions & Suggestions / Re: SOA EXPIRE number is: 3600...

Last post by snarked - February 28, 2026, 01:25:10 AM

That DNS checker believes that the expire value should be between 2 to 4 weeks (14 to 28 days) per RFC 1912 section 2.2 (now 30 years old) which merely SUGGESTS the range.  1000 hours is 41 days 16 hours.  I personally use 5 weeks (35 days), which it doesn't like either.  I prefer to have a handful of days beyond 1 full month in case I'm having a hardware problem which requires buying replacement equipment.

The only TTL-type value I use in excess of 5w is for RFC-fixed values defined as constant such as (e.g.):

localhost. 13w IN AAAA ::1
localhost. 13w IN A 127.0.0.1

13 weeks is 91 days, or about 3 standard months, or a quarter of one year.  A maximum TTL of 136.1+ years is overkill.

The minimum (negative cache) value should be close to the retry value for zones which are either dynamic or manually changed often, if not less.  Exceeding (half of) the refresh value is definently bad.

Don't read too much into warnings.  It's just the tool's opinion.