Static vs. "dynamic" DHCP Leases and DNS IPv4

Installing and Using OpenWrt
1

Hi,
i newly installed LEDE 17.01 final, after various experiments with RC and trunk.
i've configured dnsmasq and network as default except IPv4 Subnet range: 192.168.13.0/24.
And i have two NAS, that i put in the Static Leases part. The NAS are configured to use DHCP.

Problem is: DNS seems to be only working, when the NAS refreshes their DHCP Lease. So the static entries are of no use, after the router is rebooted.

Anybody noticed this and has an idea how to make the static DHCP leases permanently available in DNS?

2

I have my Synology NAS configured to use a static IP served by DHCP as well. I'm using the NAS as Pi Hole server, so the DHCP server on my router points back to the NAS as a DNS server. The NAS connects fine after rebooting. The only other change I've made is to disable IPv6 on the router and NAS.

Is there a lease time set for the NAS under Static Leases? Mine is blank.

Can you set the NAS network to not use DHCP and manually enter the IP address?

3

i put "infinite" as a text in it. Will try replacing it with "".
I could set the NAS to static IP, but thought of LEDE as the central point to configure every static address.

4

leaving it empty instead of infinite leads to the same behaviour.
in the config there's no active dynamic lease.
the static is configured like this:

Hostname  MAC-Address                             IPv4-Address    Lease time    IPv6-Suffix
NAS       00:08:9b:d1:aa:d2(192.168.13.10)       192.168.13.10

C:\Users\benutzer>nslookup nas
Server: LEDE.lan
Address: 192.168.13.1

*** LEDE.lan can't find nas: Non-existent domain

C:\Users\benutzer>nslookup nas.lan
Server: LEDE.lan
Address: 192.168.13.1

*** LEDE.lan can't find nas.lan: Non-existent domain

C:\Users\benutzer>nslookup 192.168.13.10
Server: LEDE.lan
Address: 192.168.13.1

*** LEDE.lan can't find 192.168.13.10: Non-existent domain