FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции IPV6


	Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.

Введите FGHI ссылку:

Присутствуют сообщения из эхоконференции IPV6 с датами от 31 Jul 11 14:37:00 до 03 Oct 24 21:46:09, всего сообщений: 7440

Ответить на сообщение

К списку сообщений

Предыдущее сообщение

Следующее сообщение

= Сообщение: 4244 из 7440 ============================================= IPV6 =
От   : Wilfred van Velzen               2:280/464          05 Apr 17 21:19:32
Кому : Björn Felten                                        05 Apr 17 21:19:32
Тема : Re: WSANO_DATA (11004)
FGHI : area://IPV6?msgid=2:280/464+58e5465c
На   : area://IPV6?msgid=2:203/2+58e52826
= Кодировка сообщения определена как: CP437 ==================================
Ответ: area://IPV6?msgid=2704.fido-ipv6@3:633/410+1d4aa556
==============================================================================
Hi,

On 2017-04-05 19:23:59, Björn Felten wrote to Wilfred van Velzen:
about: "WSANO_DATA (11004)":

WvV>> Maybe it's a reverse dns issue.

BF> I would definitely think so, yes. Do you have any problems with your
BF> AAAA setting?

No.

WvV>> That is kind of the norm for IPv6.

BF>    Ouch!  8-)

I think it's a configuration problem for the isp's that provide IPv6 to their customers.

If I check my "regular" IPv6 number. There is some kind of standard reverse dns assigned to it:

# host 2001:981:8a54:1:230:1bff:febc:8a61
1.6.a.8.c.b.e.f.f.f.b.1.0.3.2.0.1.0.0.0.4.5.a.8.1.8.9.0.1.0.0.2.ip6.arpa domain name pointer vlzn.xs4all.nl.

But my fido IPv6 address hasn't got one.

# host 2001:981:8a54:1:f1d0:2:280:464
Host 4.6.4.0.0.8.2.0.2.0.0.0.0.d.1.f.1.0.0.0.4.5.a.8.1.8.9.0.1.0.0.2.ip6.arpa not found: 3(NXDOMAIN)

And I think on outgoing connections a random (privacy) address is used.

I don't know why the first reverse dns method isn't used for my complete /48 range?

BF> Well, out of about a dozen IPv6 calls here regularly only four causes
BF> the error.

So the others might have a reverse dns attached to them.

WvV>> And Gert hasn't got one either on his IPv4 address:

WvV>> # host fido0.kofobbs.net
WvV>> fido0.kofobbs.net has address 80.63.101.234

WvV>> # host 80.63.101.234
WvV>> Host 234.101.63.80.in-addr.arpa. not found: 3(NXDOMAIN)

BF>    So, that kinda proves our theory then.

It's evidence, not proof! ;)

WvV>> If you are using binkd, you could try what happens if you un-set:

WvV>> #
WvV>> # Perform reverse resolving (for logging only)
WvV>> #
WvV>> backresolv

BF>    I did, and the error does no longer show in the log file. But I think
BF> that's just fixing the symptom not the error.

I think the windows version of binkd can be improved, by not showing this "warning" and just deal with the fact there is no reverse dns for some IP numbers, as the linux version does...

Bye, Wilfred.

--- FMail-W32 2.1.0.2-B20170403
* Origin: Native IPv6 connectable node (2:280/464)

К главной странице гейта