name resolution works starnge ???

[bl00dy]

hello,

Just install OpenViX 5.1.012 (2018-01-18)... and FQDN name resolution stop to work, see below:

root@vu-sr:~# nslookup vu-4k
Server: 192.168.10.254
Address 1: 192.168.10.254 ccr0.home.local
Name: vu-4k
Address 1: 192.168.10.15 vu-4k.home.local
root@vu-sr:~# nslookup vu-4k.home.local
Server: 192.168.10.254
ddress 1: 192.168.10.254 ccr0.home.local
nslookup: can't resolve 'vu-4k.home.local'
root@vu-sr:~#

the same output from windows 10 box, works fine:
C:\Users\efili>nslookup vu-4k
Server: ccr0.home.local
Address: 192.168.10.254
Non-authoritative answer:
Name: vu-4k.home.local
Address: 192.168.10.15
C:\Users\efili>nslookup vu-4k.home.local
Server: ccr0.home.local
Address: 192.168.10.254
Non-authoritative answer:
Name: vu-4k.home.local
Address: 192.168.10.15

and now one more output from Delian:
root@sm0-srv:~# nslookup vu-4k
Server: 192.168.10.254
Address: 192.168.10.254#53
Non-authoritative answer:
Name: vu-4k.home.local
Address: 192.168.10.15
root@sm0-srv:~# nslookup vu-4k.home.local
Server: 192.168.10.254
Address: 192.168.10.254#53
Non-authoritative answer:
Name: vu-4k.home.local
Address: 192.168.10.15


As you can see all works fine, but openvix correctly resolve only hostname with default suffix, but have a problem for FQDN

Seems like a bug???

[bl00dy]

The same problem with OpenViX 5.1.013. Seems it's a bug. when install blackhole, name resolution works fine.

where it can be a problem?

[Sicilian]

It's not a bug, you're using the wrong address, see below:

vuuno4k.local

[bl00dy]

Hello,

not sure I understand your answer. and Seems it's a problem related to .local domain. which I use at home. please see my output:

root@vu-4k:~# uname -a
Linux vu-4k 3.14.28-1.12 #1 SMP Mon Apr 16 21:37:14 BST 2018 armv7l GNU/Linux

root@vu-4k:~# hostname -f
vu-4k.home.local

root@vu-4k:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

root@vu-4k:~# cat /etc/resolv.conf
domain home.local
nameserver 192.168.10.254
nameserver 192.168.10.253

root@vu-4k:~# nslookup vu-4k
Server: 192.168.10.254
Address 1: 192.168.10.254 ccr0.home.local
Name: vu-4k
Address 1: 192.168.10.15 vu-4k.home.local

root@vu-4k:~# nslookup vu-4k.home.local
Server: 192.168.10.254
Address 1: 192.168.10.254 ccr0.home.local
nslookup: can't resolve 'vu-4k.home.local'

Anything I try to do nslookup with my domain home.local actually I do not see this request going to my DNS server. DNS server works fine, I am 100% sure, because other systems (windows, Debian) resolve this domain without any problem...

Also I try Vu 4k Uno, and Vu 4k Ultimo (both do not resolve FQDN)

[birdman]

It's not a bug, you're using the wrong address, see below:

vuuno4k.localNot strictly true.
It's a feature of the fact that Vix uses avahi, which implements Apple's Zeroconf architecture (also known as "Rendezvous" or "Bonjour").
Apple basically hijacked the .local DNS zone for this to use it as a dynamic DNS zone (appliances can register names in here as they start up).
The result is that you can't use a sub-domain of the .local zone as your home DNS zone.

I know, as I also had a similar set-up at one point, and had to switch away from it.

If you want to set up your own local DNS domain you should use .corp, .home or .mail ;probably the middle one.


http://www.theregister.co.uk/2018/02/12/icann_corp_home_mail_gtlds/