with help of https://internet.nl/site/fido.unen.net/3038781/ i found
out that none of my nameservers supported ipv6 so i added ipv6 AAAA records for the nameservers and updated the glue records and now it's better.
So does a recursive DNS query fallback into ipv4 if none of the nameservers for a domain have an ipv6 address? Because people could
still find my ipv6 AAAA record on my ipv4-only nameservers...
Hello Floris,
On Wednesday November 13 2024 13:20, you wrote to All:
with help of https://internet.nl/site/fido.unen.net/3038781/ i
found out that none of my nameservers supported ipv6 so i added
ipv6 AAAA records for the nameservers and updated the glue
records and now it's better.
Great!
So what do http://test-ipv6.com and https://ipv6-test.com say?
So does a recursive DNS query fallback into ipv4 if none of the
nameservers for a domain have an ipv6 address? Because people
could still find my ipv6 AAAA record on my ipv4-only
nameservers...
Don't confuse the accesability with the content of name servers. Most
name servers that are accesible by IPv4 only do respond with an AAAA record when that is present for the requested host.
But of course we should all prepare to function in an IPv6 only environment, so the use of name servers that are accesable via IPv6 is much preferred.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)
Its great to see progress on enabling IPv6 for your nameservers,
Floris! Adding AAAA records and updating the glue records is a smart
move to enhance IPv6 compatibility.
Hello David,
On Saturday November 16 2024 22:18, you wrote to All:
Its great to see progress on enabling IPv6 for your nameservers,
Floris! Adding AAAA records and updating the glue records is a
smart move to enhance IPv6 compatibility.
Thanks for you elaborate response.
From your response I presume that you yourself have IPv6 capability. I
can not test if your node answers on IPv6, you are not (yet) in the nodelist, so I do not haven your contact data. If you publish your
connect info here, I can try to make an IPv6 connection with your
system and if hat succeeds, I will enter you in the list of IPv6 nodes
as a prospective member of the Fiodonet IPv6 club.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)
With regards to your question, yes I'm on bbs.skynetbbs.com which
points to 2800:e2:5480:60::20, I think I created the AAAA on my DNS control panel, so if you poll it should let you in, word of caution my
BBS is still very stock but that's because I've found it difficult to modify Mystic default theme and menus.
I'll try to be active on this area because I'm an IPv6 advocate and
very pasionate about it, in fact I teach IPv6 classes for "living".
^^With regards to your question, yes I'm on bbs.skynetbbs.com which
points to 2800:e2:5480:60::20,
So no IPv6 connect yet. The first thing to look at would be the
firewall. You should create an IPv6 pinhole fo port 24554.
On 2024-11-17 21:27:14, you wrote to David Gonzalez:MvdV>> 21:25 [1060] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
^^With regards to your question, yes I'm on bbs.skynetbbs.com
which points to 2800:e2:5480:60::20,
^
I think you forgot a '0' !?
So congratulations and welcome to the Fidonet IPv6 club!
Hallo again Michael, yes, I'm coming back to fido after 30 years and indeed my provider assigned me a half-ass /64, which they consider is
more than enough for a home user, so I had to decide what I wanetd to
have IPv6 connectivity for my home lab or my house, so the LAB won.
Hello David,
On Sunday November 17 2024 14:23, you wrote to me:
With regards to your question, yes I'm on bbs.skynetbbs.com which
points to 2800:e2:5480:60::20, I think I created the AAAA on my
DNS control panel, so if you poll it should let you in, word of
caution my BBS is still very stock but that's because I've found
it difficult to modify Mystic default theme and menus.
I tried it:
+ 21:25 [1060] call to 4:930/1@fidonet
21:25 [1060] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
? 21:26 [1060] connection to 4:930/1@fidonet failed: {W32
API error 10060} Connection timed out
21:26 [1060] trying bbs.skynetbbs.com [181.142.97.252]...
21:26 [1060] connected
+ 21:26 [1060] outgoing session with bbs.skynetbbs.com:24554 [181.142.97.252] - 21:26 [1060] OPT CRAM-MD5-d622da334d8cd27747b0356c9cb4cd70 + 21:26 [1060] Remote
requests MD mode - 21:26 [1060] SYS SkyNet BBS - 21:26 [1060] LOC Medellin, Colombia - 21:26 [1060] ZYZ DavidG - 21:26 [1060] TIME Sun,
17 Nov 2024 20:26:08 -0500 - 21:26 [1060] VER Mystic/1.12A48 binkp/1.0
- 21:26 [1060] BUILD 2023/01/15 15:29:47 Windows/32
+ 21:26 [1060] addr: 21:3/188@fsxnet (n/a or busy)
+ 21:26 [1060] addr: 3:633/2744.188@fidonet
+ 21:26 [1060] addr: 4:930/1@fidonet
+ 21:26 [1060] addr: 4:930/0@fidonet
+ 21:26 [1060] addr: 4:93/0@fidonet
- 21:26 [1060] QSIZE 0 files 0 bytes
+ 21:26 [1060] done (to 4:930/1@fidonet, OK, S/R: 0/0 (0/0 bytes))
21:26 [1060] session closed, quitting...
21:26 [4008] the queue is empty, quitting...
D:\FIDO6\BINKD>
So no IPv6 connect yet. The first thing to look at would be the
firewall. You should create an IPv6 pinhole fo port 24554.
I'll try to be active on this area because I'm an IPv6 advocate
and very pasionate about it, in fact I teach IPv6 classes for
"living".
Great!
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)
Hello David,
Sunday November 17 2024 21:27, I wrote to you:
So no IPv6 connect yet. The first thing to look at would be the
firewall. You should create an IPv6 pinhole fo port 24554.
I see you goy it fixed already:
+ 22:06 [4472] call to 4:930/1@fidonet
22:06 [4472] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
22:06 [4472] connected
+ 22:06 [4472] outgoing session with bbs.skynetbbs.com:24554
[2800:e2:5480:60::2]
- 22:06 [4472] OPT CRAM-MD5-566231661606aa412c74fee39a672079
+ 22:06 [4472] Remote requests MD mode
- 22:06 [4472] SYS SkyNet BBS
- 22:06 [4472] LOC Medellin, Colombia
- 22:06 [4472] ZYZ DavidG
- 22:06 [4472] TIME Sun, 17 Nov 2024 21:06:38 -0500
- 22:06 [4472] VER Mystic/1.12A48 binkp/1.0
- 22:06 [4472] BUILD 2023/01/15 15:29:47 Windows/32
+ 22:06 [4472] addr: 21:3/188@fsxnet (n/a or busy)
+ 22:06 [4472] addr: 3:633/2744.188@fidonet
+ 22:06 [4472] addr: 4:930/1@fidonet
+ 22:06 [4472] addr: 4:930/0@fidonet
So congratulations and welcome to the Fidonet IPv6 club!
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)
Hello David,
Sunday November 17 2024 22:07, I wrote to you:
So congratulations and welcome to the Fidonet IPv6 club!
Normally the update for the list as published in Fidonews is hatched
at Sunday 22:00 my local time (21:00 UTC). so you just missed that.
But I rehatched it and if all goes well, you will be in the list of tomorrows Fidonews.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)
Hello David,
On Sunday November 17 2024 14:23, you wrote to me:
Hallo again Michael, yes, I'm coming back to fido after 30 years
and indeed my provider assigned me a half-ass /64, which they
consider is more than enough for a home user, so I had to decide
what I wanetd to have IPv6 connectivity for my home lab or my
house, so the LAB won.
Just a /64 is very scroogy. Best Opeating Practice has it that
customers should at least get a /56. many give a /48.
Are you sure you can't get more than just a /64? If not, for me that would be a reason to take my bussines elsewhere...
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)
So congratulations and welcome to the Fidonet IPv6 club!
Yup, but I just changed the IPv6 to match my (local) ipv4, so it's now ::20, give it a go and it should also reply.
I also had to disable SLAAC from My Mikrotik edge so did not get
EUI-64.
1) You forgot to update the AAAA record for bbs.skynetbbs.com.
I did indeed, that plus I use a shitty provider namecheap, but it's updated now.
Are you sure you can't get more than just a /64? If not, for me
that would be a reason to take my bussines elsewhere...
Yup, trust me, been there, done that, but that unfortunately is the
only one that you can get to do bridge mode on the CPE for IPv4,
we're way behind down here in South America (except Brazil) when it
comes to v6, as I said I throw hate everytime I can to those grumpy old-men with their brains stuck on IPv4 and the /30 and v4 VLSM
practices migrated to IPv6.
The otehr issue I do not want to rn n into is using Tunnelbroker, it's slow because of it's 6to4 tunnel nature, but it's an alternative, I do like HE, but being a VPN and its inherent drawbacks drives me away.
Sysop: | Sarah |
---|---|
Location: | Portland, Oregon |
Users: | 19 |
Nodes: | 16 (0 / 16) |
Uptime: | 53:44:07 |
Calls: | 126 |
Calls today: | 126 |
Files: | 84,009 |
U/L today: |
5 files (318K bytes) |
D/L today: |
33 files (8,385K bytes) |
Messages: | 38,259 |
Posted today: | 25 |