Displaying 3 results from an estimated 3 matches for "dhcp_dyndn".
Did you mean:
dhcp_dyndns
2019 Jan 23
1
Odd behavior with "allow dns updates" (+dhcp_dyndns.sh)
>
>
>
>
> > All,
> >
> > I'm hoping somebody could help explain this: with the Wiki
> > dhcp_dyndns.sh script and "allow dns updates = secure and nonsecure",
> > I have the following log snippet for a single machine:
>
> The two have absolutely nothing to do with each other.
>
>
OK, now I'm reading that "allow dns updates" only applies to the Internal
D...
2019 Jan 23
2
Odd behavior with "allow dns updates" (+dhcp_dyndns.sh)
All,
I'm hoping somebody could help explain this: with the Wiki dhcp_dyndns.sh
script and "allow dns updates = secure and nonsecure", I have the following
log snippet for a single machine:
Jan 22 13:37:35 DC1 dhcpd: Commit: IP: 172.250.250.19 DHCID:
> 1:be:a9:c5:4f:5f:cd Name: SERVER
> <stuff>
> Jan 22 13:37:35 DC1 named[20138]: samba_dlz: start...
2018 Jan 09
3
samba_dlz shutting down on named reload
...cceeded
Jan 09 15:28:52 dc03.rvx.is named[15585]: all zones loaded
Jan 09 15:28:52 dc03.rvx.is named[15585]: *samba_dlz: shutting down*
Jan 09 15:28:52 dc03.rvx.is named[15585]: running
Jan 09 15:28:52 dc03.rvx.is systemd[1]: Reloaded Berkeley Internet Name
Domain (DNS).
This breaks the system and dhcp_dyndns.sh stops working.
I can get it working again by *restarting * named:
"*systemctl restart named*"
...
Jan 09 15:31:18 dc03.rvx.is named[15974]: zone localhost/IN: loaded serial 0
Jan 09 15:31:18 dc03.rvx.is named[15974]: all zones loaded
Jan 09 15:31:18 dc03.rvx.is named[15974]: running...