Actions
Bug #6064
closed
GZ
non-fully qualified hostnames included in hosts file and Unbound local-data
Bug #6064:
non-fully qualified hostnames included in hosts file and Unbound local-data
Start date:
04/02/2016
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
Description
mydomain: my.private
add test.my.private 127.0.0.1
add test.yours.private 127.0.0.2
> unbound-control -c /var/unbound/unbound.conf list_local_data | grep test test.yours.private. 3600 IN A 127.0.0.2 test. 3600 IN A 127.0.0.2 test. 3600 IN A 127.0.0.1 2.0.0.127.in-addr.arpa. 3600 IN PTR test.yours.local. test.my.private. 3600 IN A 127.0.0.1
> ping test PING test.yours.private (127.0.0.2): 56 data bytes
That's wrong.
It should ping test.my.private=127.0.0.1 because:
> cat /etc/resolv.conf nameserver 127.0.0.1 search my.private
You should not add hostnames to unbound. Only FQDN.
Actions