"The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for."

I've written about this strange error before, but nobody seemed to know what it's all about, so let me try again.

It only happens on incoming calls. And it only happens from Andrew, Bill, Nicholas and Wilfred, all IPv6. Plus, strangely enough, from Gert (IPv4!).

It obviously is a DNS issue of some kind, but what?

Google wasn't much help, the first hundred or so links I tried all ended up in program specific discussions.

No big deal really, the connections are made just fine, I'm just curious.

..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

Hi,

On 2017-04-05 17:03:43, Bj�rn Felten wrote to All:
about: "WSANO_DATA (11004)":

"The requested name is valid and was found in the database, but it
does not have the correct associated data being resolved for."

I've written about this strange error before, but nobody seemed to
know what it's all about, so let me try again.

It only happens on incoming calls. And it only happens from Andrew,
Bill, Nicholas and Wilfred, all IPv6. Plus, strangely enough, from
Gert (IPv4!).

Gert is always strange! ;)

It obviously is a DNS issue of some kind, but what?

Maybe it's a reverse dns issue. That is kind of the norm for IPv6. And Gert hasn't got one either on his IPv4 address:

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

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

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

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


Bye, Wilfred.


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

Maybe it's a reverse dns issue.

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

That is kind of the norm for IPv6.

Ouch! 8-)

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

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

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

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

So, that kinda proves our theory then.

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

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

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





..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

Hello Wilfred,

On Wednesday April 05 2017 18:11, you wrote to Bj�rn Felten:

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

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

In order to test that hypothesis, I have entered the backresolv keyword in my binkd.cfg


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

Hi,

On 2017-04-05 19:13:11, Michiel van der Vlist wrote to Wilfred van Velzen:
about: "WSANO_DATA (11004)":

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

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

MvdV> In order to test that hypothesis, I have entered the backresolv keyword in
MvdV> my binkd.cfg

Do you see the same error as Bjorn?

It worked for Bjorn...

Bye, Wilfred.


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

Hello, Wilfred van Velzen.
On 05/04/2017 6:11 p.m. you wrote:

Hi, On 2017-04-05 17:03:43, Bj�rn Felten wrote to All:
about: "WSANO_DATA (11004)":

It obviously is a DNS issue of some kind, but what?

Maybe it's a reverse dns issue. That is kind of the norm for IPv6.
And Gert hasn't got one either on his IPv4 address:

My vote also for rdns. Björn didnt list my system which has reverse for both ipv6 and ipv4.

'Tommi
--- Hotdoged/2.13.5/Android
* Origin: native ipv6 point (2:221/1.100)

Hello Wilfred,

On Wednesday April 05 2017 19:36, you wrote to me:

backresolv

MvdV>> In order to test that hypothesis, I have entered the backresolv
MvdV>> keyword in my binkd.cfg

Do you see the same error as Bjorn?

Yes, I see it /now/, now that I have entered backresolv in my config:


- 05 Apr 19:30:07 [436] incoming from 92.241.103.6 (55584)
+ 05 Apr 19:30:08 [2756] Error in getnameinfo(): Der angeforderte Name ist g�ltig und wurde in der Datenbank gefunden. Er verf�gt jedoch nicht �ber die richtigen zugeordneten Daten, die ausgewertet werden sollten. (11004)
+ 05 Apr 19:30:08 [2756] incoming session with 92.241.103.6
- 05 Apr 19:30:08 [2756] SYS GaNJaNET STaTi0N
- 05 Apr 19:30:08 [2756] ZYZ Konstantin Kuzov
- 05 Apr 19:30:08 [2756] LOC Smolensk, Russia
- 05 Apr 19:30:08 [2756] NDL 1Gbit,TCP,BINKP


- 05 Apr 19:44:07 [436] incoming from 2001:980:42ea:1:f1d0:2:280:5003 (52671)
+ 05 Apr 19:44:07 [2308] Error in getnameinfo(): Der angeforderte Name ist g�l + 05 Apr 19:44:07 [2308] incoming session with 2001:980:42ea:1:f1d0:2:280:5003 g�ltig und wurde in der Datenbank gefunden. Er verf�gt jedoch nicht �ber die richtigen zugeordneten Daten, die ausgewertet werden sollten. (11004)
- 05 Apr 19:44:07 [2308] SYS Double Dutch
- 05 Apr 19:44:07 [2308] ZYZ Kees Van Eeten
- 05 Apr 19:44:07 [2308] LOC Heerhugowaard, The Netherlands

For IP numbers that backresolve I get this:

- 05 Apr 19:27:50 [436] incoming from 2001:470:27:302::2 (4180)
+ 05 Apr 19:27:50 [2584] incoming session with bfelten-1-pt.tunnel.tserv24.
sto1.ipv6.he.net [2001:470:27:302::2]
- 05 Apr 19:27:51 [2584] SYS Felten's Sharp System
- 05 Apr 19:27:51 [2584] ZYZ Bj�rn Felten
- 05 Apr 19:27:51 [2584] LOC S�ve, Sweden
- 05 Apr 19:27:51 [2584] NDL 115200,TCP,BINKP


So it is not IPv6 related, but related to IPs that do not backresolve.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

Hi,

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

Maybe it's a reverse dns issue.

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

No.

That is kind of the norm for IPv6.

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?

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

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

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

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

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

So, that kinda proves our theory then.

It's evidence, not proof! ;)

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

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

I did, and the error does no longer show in the log file. But I think 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)

Hi,

On 2017-04-05 19:48:11, Michiel van der Vlist wrote to Wilfred van Velzen:
about: "WSANO_DATA (11004)":

Do you see the same error as Bjorn?

MvdV> Yes, I see it /now/, now that I have entered backresolv in my config:

MvdV> So it is not IPv6 related, but related to IPs that do not
MvdV> backresolve.

It seems so. The windows binkd version should be improved to handle this situation more gracefully...

Bye, Wilfred.


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

Wilfred van Velzen wrote to Bj�rn Felten <=-

# 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.

You should be able to host your own reverse DNS for IPv6 in many cases. On my setup, only the IPv6 address assigned by my ISP to the router's PPPoE interface has a reverse DNS (it's outside my /56). Inside my /56, I have reverse DNS delegated to a DNS provider and my records are in there for the hosts with static IPv6 addresses. The BBSs should resolve to the same hostnames that are in their AAAA records. If not, then I have to update my reverse DNS. :D

[root@dedicated06 ~]# host 2001:44b8:4176:f100::6 6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.6.7.1.4.8.b.4.4.1.0.0.2.ip6.arpa domain name pointer freeway.vkradio.com.
[root@dedicated06 ~]# host 2001:44b8:4176:f100::7 7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.6.7.1.4.8.b.4.4.1.0.0.2.ip6.arpa domain name pointer bridge.vkradio.com.

Yep, the BBSs have reverse DNS. :)

That is one thing I do like about IPv6, control of reverse DNS is very often possible. :)


... god@universe:~ # cvs up && make world
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

Hello Wilfred,

On Wednesday April 05 2017 21:33, you wrote to me:

MvdV>> So it is not IPv6 related, but related to IPs that do not
MvdV>> backresolve.

It seems so. The windows binkd version should be improved to handle
this situation more gracefully...

Yes, the error message is not all thet informative as it is.

OTOH, I do not find the backresolve function all that usefull in itself. There is a reason I had it disabled. It slows things down and especially in the case of IPv6 it does not provide very usefull information. Sometimes it resolves, ever so often it does not.
All Ziggo native IPv6 numbers resolve to ipv6.dynamic.ziggo.nl.

Your IPv6 number does not resolve en neither does that of Kees. Joe's IPv6 address resolves.

- 05 Apr 19:54:28 [436] incoming from 2607:f2c0:a000:54:6ef0:49ff:fedb:3822 (449498)
+ 05 Apr 19:54:28 [1604] incoming session with node-4stumtkuebu8foqrgv6.ipv6.
t4stumtkuebu8foqrgv6.ipv6.teksavvy.com
[2607:f2c0:a000:54:6ef0:49ff:fedb:3822]
- 05 Apr 19:54:28 [1604] SYS The Lion's Den
- 05 Apr 19:54:28 [1604] ZYZ Joe Delahaye
- 05 Apr 19:54:28 [1604] LOC Trenton, Ont. Cdn
- 05 Apr 19:54:28 [1604] NDL 115200,TCP,BINKP



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
* Origin: he.net certified sage (2:280/5555)

Hi Michiel.

06 Apr 17 00:19:12, you wrote to Wilfred van Velzen:

On Wednesday April 05 2017 21:33, you wrote to me:

MvdV>>> So it is not IPv6 related, but related to IPs that do not
MvdV>>> backresolve.

It seems so. The windows binkd version should be improved to handle
this situation more gracefully...

Yes, the error message is not all thet informative as it is.

It seems to be a winsock message. I don't see it in my cygwin version of binkd.

All Ziggo native IPv6 numbers resolve to ipv6.dynamic.ziggo.nl.

That's not very nice from Ziggo...

Elisa native ipv6 backresolves like this:

nep76ziaoz7vbzoes-2.v6.elisa-mobile.fi

Not very informative but it is unique.

'Tommi

... he.net certified sage
---
* Origin: IPv6 Point at [2001:470:1f15:cb0::4] (2:221/1.1)

Hi Tony.

06 Apr 17 07:26:00, you wrote to Wilfred van Velzen:

Wilfred van Velzen wrote to Bj�rn Felten <=-

# 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.

You should be able to host your own reverse DNS for IPv6 in many cases.

He.net allows me to run my own dns server for reverse. :)

'Tommi

... he.net certified sage
---
* Origin: IPv6 Point at [2001:470:1f15:cb0::4] (2:221/1.1)

Tommi Koivula wrote to Tony Langdon <=-

You should be able to host your own reverse DNS for IPv6 in many cases.

He.net allows me to run my own dns server for reverse. :)

So does my ISP. :)


... Truth has nothing to fear from examination
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

TK> He.net allows me to run my own dns server for reverse. :)

So does my ISP. :)

But you have no tunnel, are you? :)

tommi@boy:~$ host freeway.vkradio.com
freeway.vkradio.com has address 202.12.89.162
freeway.vkradio.com has IPv6 address 2001:44b8:4176:f100::6

tommi@boy:~$ host 2001:44b8:4176:f100::6 6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.6.7.1.4.8.b.4.4.1.0.0.2.ip6.arpa domain name pointer freeway.vkradio.com.

tommi@boy:~$ host 202.12.89.162
Host 162.89.12.202.in-addr.arpa. not found: 3(NXDOMAIN)

'Tommi

---
* Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6.0)

Tommi Koivula wrote to Tony Langdon <=-

@MSGID: <58E9EFF6.2711.fido-ipv6@freeway.apana.org.au>
@TZ: 00b4

TK> He.net allows me to run my own dns server for reverse. :)

So does my ISP. :)

But you have no tunnel, are you? :)

Nope, no tunnel here. :)

tommi@boy:~$ host freeway.vkradio.com
freeway.vkradio.com has address 202.12.89.162
freeway.vkradio.com has IPv6 address 2001:44b8:4176:f100::6

tommi@boy:~$ host 2001:44b8:4176:f100::6 6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.f.6.7.1.4.8.b.4.4.1.0.0.2.ip6.arpa
domain
name pointer freeway.vkradio.com.

tommi@boy:~$ host 202.12.89.162
Host 162.89.12.202.in-addr.arpa. not found: 3(NXDOMAIN)

IPv4 is outside my control, but I could get them to add a PTR. :) Oh, and IPv4 _does_ use a tunnel! :D


... Bachelors don't have Mother-in-laws.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)