How is the reversed domain handled, or is it not. Rowland, you did not
have that in your sample you cobbled together.
In /usr/share/samba/setup/named.conf there is:
zone "123.168.192.in-addr.arpa" in {
type master;
file "123.168.192.in-addr.arpa.zone";
update-policy {
grant ${REALM_WC} wildcard *.123.168.192.in-addr.arpa. PTR;
};
};
But that raises more questions than answers.
On 03/09/15 21:38, Robert Moskowitz wrote:> How is the reversed domain handled, or is it not. Rowland, you did > not have that in your sample you cobbled together. > > In /usr/share/samba/setup/named.conf there is: > > zone "123.168.192.in-addr.arpa" in { > type master; > file "123.168.192.in-addr.arpa.zone"; > update-policy { > grant ${REALM_WC} wildcard *.123.168.192.in-addr.arpa. > PTR; > }; > }; > > But that raises more questions than answers. > > >First and foremost, I am sure I have already told you this, you must create the reverse zone, it is not created for you, use samba-tool. You do not add the reverse zone to the name flat files it goes in AD. And finally, the dhcp set up you say I 'cobbled together' works, it leads to logs like this: Sep 3 20:49:38 dc01 dhcpd: Commit: IP: 192.168.0.119 DHCID: 1:84:a6:c8:3b:da:7b Name: ThinkPad Sep 3 20:49:38 dc01 dhcpd: execute_statement argv[0] = /usr/local/sbin/dhcp-dyndns.sh Sep 3 20:49:38 dc01 dhcpd: execute_statement argv[1] = add Sep 3 20:49:38 dc01 dhcpd: execute_statement argv[2] = 192.168.0.119 Sep 3 20:49:38 dc01 dhcpd: execute_statement argv[3] = 1:84:a6:c8:3b:da:7b Sep 3 20:49:38 dc01 dhcpd: execute_statement argv[4] = ThinkPad Sep 3 20:49:39 dc01 named[29751]: samba_dlz: starting transaction on zone example.com Sep 3 20:49:39 dc01 named[29751]: samba_dlz: allowing update of signer=dhcpduser\@EXAMPLE.COM name=ThinkPad.example.com tcpaddr=127.0.0.1 type=A key=361144448.sig-dc01.example.com/160/0 Sep 3 20:49:39 dc01 named[29751]: samba_dlz: allowing update of signer=dhcpduser\@EXAMPLE.COM name=ThinkPad.example.com tcpaddr=127.0.0.1 type=A key=361144448.sig-dc01.example.com/160/0 Sep 3 20:49:39 dc01 named[29751]: client 127.0.0.1#38551/key dhcpduser\@EXAMPLE.COM: updating zone 'example.com/NONE': deleting rrset at 'ThinkPad.example.com' A Sep 3 20:49:39 dc01 named[29751]: samba_dlz: subtracted rdataset ThinkPad.example.com 'ThinkPad.example.com.#0113600#011IN#011A#011192.168.0.119' Sep 3 20:49:39 dc01 named[29751]: client 127.0.0.1#38551/key dhcpduser\@EXAMPLE.COM: updating zone 'example.com/NONE': adding an RR at 'ThinkPad.example.com' A Sep 3 20:49:39 dc01 named[29751]: samba_dlz: added rdataset ThinkPad.example.com 'ThinkPad.example.com.#0113600#011IN#011A#011192.168.0.119' Sep 3 20:49:40 dc01 named[29751]: samba_dlz: committed transaction on zone example.com Sep 3 20:49:40 dc01 named[29751]: samba_dlz: starting transaction on zone 0.168.192.in-addr.arpa Sep 3 20:49:40 dc01 named[29751]: samba_dlz: allowing update of signer=dhcpduser\@EXAMPLE.COM name=119.0.168.192.in-addr.arpa tcpaddr=127.0.0.1 type=PTR key=2712376528.sig-dc01.example.com/160/0 Sep 3 20:49:40 dc01 named[29751]: samba_dlz: allowing update of signer=dhcpduser\@EXAMPLE.COM name=119.0.168.192.in-addr.arpa tcpaddr=127.0.0.1 type=PTR key=2712376528.sig-dc01.example.com/160/0 Sep 3 20:49:40 dc01 named[29751]: client 127.0.0.1#39585/key dhcpduser\@EXAMPLE.COM: updating zone '0.168.192.in-addr.arpa/NONE': deleting rrset at '119.0.168.192.in-addr.arpa' PTR Sep 3 20:49:40 dc01 named[29751]: samba_dlz: subtracted rdataset 119.0.168.192.in-addr.arpa '119.0.168.192.in-addr.arpa.#0113600#011IN#011PTR#011ThinkPad.example.com.' Sep 3 20:49:40 dc01 named[29751]: client 127.0.0.1#39585/key dhcpduser\@EXAMPLE.COM: updating zone '0.168.192.in-addr.arpa/NONE': adding an RR at '119.0.168.192.in-addr.arpa' PTR Sep 3 20:49:40 dc01 named[29751]: samba_dlz: added rdataset 119.0.168.192.in-addr.arpa '119.0.168.192.in-addr.arpa.#0113600#011IN#011PTR#011ThinkPad.example.com.' Sep 3 20:49:40 dc01 named[29751]: samba_dlz: committed transaction on zone 0.168.192.in-addr.arpa Sep 3 20:49:40 dc01 logger: DHCP-DNS Update succeeded Rowland
On 09/03/2015 04:55 PM, Rowland Penny wrote:> On 03/09/15 21:38, Robert Moskowitz wrote: >> How is the reversed domain handled, or is it not. Rowland, you did >> not have that in your sample you cobbled together. >> >> In /usr/share/samba/setup/named.conf there is: >> >> zone "123.168.192.in-addr.arpa" in { >> type master; >> file "123.168.192.in-addr.arpa.zone"; >> update-policy { >> grant ${REALM_WC} wildcard >> *.123.168.192.in-addr.arpa. PTR; >> }; >> }; >> >> But that raises more questions than answers. >> >> >> > > First and foremost, I am sure I have already told you this, you must > create the reverse zone, it is not created for you, use samba-tool.I will look at the wiki for this. thaks> > You do not add the reverse zone to the name flat files it goes in AD. > > And finally, the dhcp set up you say I 'cobbled together' works, it > leads to logs like this:I meant your named.conf that you said you took from mulitple files. Sorry. Did not at all mean to imply a hack job.