I've got a Nas doing DHCP and DNS ip adress = 192.168.0.1
local names are correctly resolved when raspberrypi-0-w ip is set to dynamic
pi@raspberrypi0-w2:~ $ ping munin PING munin.cesan.lan (192.168.0.51) 56(84) bytes of data. 64 bytes from 192.168.0.51 (192.168.0.51): icmp_seq=1 ttl=64 time=5.07 ms
After setting static ip in
/etc/dhcpcd.conf, adress is outside dhcp range
# Inform the DHCP server of our hostname for DDNS. hostname # Use the hardware address of the interface for the Client ID. clientid # Persist interface configuration when dhcpcd exits. persistent # Rapid commit support. # Safe to enable by default because it requires the equivalent option set # on the server to actually work. option rapid_commit # A list of options to request from the DHCP server. option domain_name_servers, domain_name, domain_search, host_name option classless_static_routes # Most distributions have NTP support. option ntp_servers # Respect the network MTU. This is applied to DHCP routes. option interface_mtu # A ServerID is required by RFC2131. require dhcp_server_identifier # Generate Stable Private IPv6 Addresses instead of hardware based ones slaac private # Static IP configuration: interface wlan0 static ip_address=192.168.0.53/24 static routers=192.168.0.1 static domain_name_servers=192.168.0.1
pi@raspberrypi0-w2:~ $ ping munin ping: munin: Nom ou service inconnu
local host is unknown
If I ping with adress it's ok
pi@raspberrypi0-w2:~ $ ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.48 ms
if I ping outside LAN it seems to resolve the name but I don't get the ping
pi@raspberrypi0-w2:~ $ ping raspberrypi.stackexchange.com PING raspberrypi.stackexchange.com (188.8.131.52) 56(84) bytes of data.
Is it a problem on Raspbian side or on the DNS side?
# Generated by resolvconf nameserver 192.168.0.1