[Samba] samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates

Billy Bob billysbobs at yahoo.com
Fri Jan 11 16:13:50 UTC 2019


 

    On Friday, January 11, 2019 3:14 AM, Rowland Penny via samba <samba at lists.samba.org> wrote:
 
>
 >I have no idea where the above is coming from, but it isn't from the dhcp scripts.
>

I don't know what to tell you, Rowland. The previous logs were with the -d option in place, and those extra lines were what was added as a result of the -d option.

Here is what the logs show WITHOUT the -d option:

Jan 11 10:00:36 dc01 dhcpd[1704]: Commit: IP: 172.20.10.165 DHCID: 1:d4:be:d9:22:9f:7d Name: mgmt01
Jan 11 10:00:36 dc01 dhcpd[1704]: execute_statement argv[0] = /usr/local/bin/dhcp-dyndns.sh
Jan 11 10:00:36 dc01 dhcpd[1704]: execute_statement argv[1] = add
Jan 11 10:00:36 dc01 dhcpd[1704]: execute_statement argv[2] = 172.20.10.165
Jan 11 10:00:36 dc01 dhcpd[1704]: execute_statement argv[3] = 1:d4:be:d9:22:9f:7d
Jan 11 10:00:36 dc01 dhcpd[1704]: execute_statement argv[4] = mgmt01
Jan 11 10:00:36 dc01 sh[1704]: dns_tkey_gssnegotiate: TKEY is unacceptable
Jan 11 10:00:36 dc01 sh[1704]: dns_tkey_gssnegotiate: TKEY is unacceptable
Jan 11 10:00:36 dc01 dhcpd[1704]: execute: /usr/local/bin/dhcp-dyndns.sh exit status 2816
Jan 11 10:00:36 dc01 dhcpd[1704]: reuse_lease: lease age 364 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.10.165
Jan 11 10:00:36 dc01 dhcpd[1704]: DHCPREQUEST for 172.20.10.165 from d4:be:d9:22:9f:7d (mgmt01) via eno1
Jan 11 10:00:36 dc01 dhcpd[1704]: DHCPACK on 172.20.10.165 to d4:be:d9:22:9f:7d (mgmt01) via eno1

and here is the same/similar transaction WITH the -d option, showing the mystery lines being added:

Jan 11 09:54:32 dc01 dhcpd[1181]: Commit: IP: 172.20.10.165 DHCID: 1:d4:be:d9:22:9f:7d Name: mgmt01
Jan 11 09:54:32 dc01 dhcpd[1181]: execute_statement argv[0] = /usr/local/bin/dhcp-dyndns.sh
Jan 11 09:54:32 dc01 dhcpd[1181]: execute_statement argv[1] = add
Jan 11 09:54:32 dc01 dhcpd[1181]: execute_statement argv[2] = 172.20.10.165
Jan 11 09:54:32 dc01 dhcpd[1181]: execute_statement argv[3] = 1:d4:be:d9:22:9f:7d
Jan 11 09:54:32 dc01 dhcpd[1181]: execute_statement argv[4] = mgmt01
Jan 11 09:54:32 dc01 sh[1181]: Reply from SOA query:
Jan 11 09:54:32 dc01 sh[1181]: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id:  11079
Jan 11 09:54:32 dc01 sh[1181]: ;; flags: qr aa ra; QUESTION: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
Jan 11 09:54:32 dc01 sh[1181]: ;; QUESTION SECTION:
Jan 11 09:54:32 dc01 sh[1181]: ;mgmt01.corp.<DOMAIN>.com.                IN        SOA
Jan 11 09:54:32 dc01 sh[1181]: ;; AUTHORITY SECTION:
Jan 11 09:54:32 dc01 sh[1181]: corp.<DOMAIN>.com.                0        IN        SOA        dc01.corp.<DOMAIN>.com. hostmaster.corp.<DOMAIN>.com. 38 900 600 86400 3600
Jan 11 09:54:32 dc01 sh[1181]: Found zone name: corp.<DOMAIN>.com
Jan 11 09:54:32 dc01 sh[1181]: The master is: dc01.corp.<DOMAIN>.com
Jan 11 09:54:32 dc01 sh[1181]: start_gssrequest
Jan 11 09:54:32 dc01 sh[1181]: send_gssrequest
Jan 11 09:54:32 dc01 sh[1181]: Outgoing update query:
Jan 11 09:54:32 dc01 sh[1181]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:   1846
Jan 11 09:54:32 dc01 sh[1181]: ;; flags:; QUESTION: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
Jan 11 09:54:32 dc01 sh[1181]: ;; QUESTION SECTION:
Jan 11 09:54:32 dc01 sh[1181]: ;4182804529.sig-dc01.corp.<DOMAIN>.com. ANY        TKEY
Jan 11 09:54:32 dc01 sh[1181]: ;; ADDITIONAL SECTION:
Jan 11 09:54:32 dc01 sh[1181]: 4182804529.sig-dc01.corp.<DOMAIN>.com. 0 ANY TKEY        gss-tsig. 1547222072 1547222072 3 NOERROR 1397 YIIFcQYGKwYBBQUCoIIFZTCCBWGgDTALBgkqhkiG9xIBAgKiggVOBIIF SmCCBUYGCSqGSIb3EgECAgEAboIFNTCCBTGgAwIBBaEDAgEOo
Jan 11 09:54:32 dc01 sh[1181]: recvmsg reply from GSS-TSIG query
Jan 11 09:54:32 dc01 sh[1181]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:   1846
Jan 11 09:54:32 dc01 sh[1181]: ;; flags: qr ra; QUESTION: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
Jan 11 09:54:32 dc01 sh[1181]: ;; QUESTION SECTION:
Jan 11 09:54:32 dc01 sh[1181]: ;4182804529.sig-dc01.corp.<DOMAIN>.com. ANY        TKEY
Jan 11 09:54:32 dc01 sh[1181]: ;; ANSWER SECTION:
Jan 11 09:54:32 dc01 sh[1181]: 4182804529.sig-dc01.corp.<DOMAIN>.com. 0 ANY TKEY        gss-tsig. 0 0 3 BADKEY 0  0
Jan 11 09:54:32 dc01 sh[1181]: dns_tkey_gssnegotiate: TKEY is unacceptable
Jan 11 09:54:32 dc01 sh[1181]: Reply from SOA query:
Jan 11 09:54:32 dc01 sh[1181]: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id:  30544
Jan 11 09:54:32 dc01 sh[1181]: ;; flags: qr aa ra; QUESTION: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
Jan 11 09:54:32 dc01 sh[1181]: ;; QUESTION SECTION:
Jan 11 09:54:32 dc01 sh[1181]: ;165.10.20.172.in-addr.arpa.        IN        SOA
Jan 11 09:54:32 dc01 sh[1181]: ;; AUTHORITY SECTION:
Jan 11 09:54:32 dc01 sh[1181]: 10.20.172.in-addr.arpa.        0        IN        SOA        dc01.corp.<DOMAIN>.com. hostmaster.corp.<DOMAIN>.com. 2 900 600 86400 3600
Jan 11 09:54:32 dc01 sh[1181]: Found zone name: 10.20.172.in-addr.arpa
Jan 11 09:54:32 dc01 sh[1181]: The master is: dc01.corp.<DOMAIN>.com
Jan 11 09:54:32 dc01 sh[1181]: start_gssrequest
Jan 11 09:54:32 dc01 sh[1181]: send_gssrequest
Jan 11 09:54:32 dc01 sh[1181]: Outgoing update query:
Jan 11 09:54:32 dc01 sh[1181]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:  37632
Jan 11 09:54:32 dc01 sh[1181]: ;; flags:; QUESTION: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
Jan 11 09:54:32 dc01 sh[1181]: ;; QUESTION SECTION:
Jan 11 09:54:32 dc01 sh[1181]: ;1779289402.sig-dc01.corp.<DOMAIN>.com. ANY        TKEY
Jan 11 09:54:32 dc01 sh[1181]: ;; ADDITIONAL SECTION:
Jan 11 09:54:32 dc01 sh[1181]: 1779289402.sig-dc01.corp.<DOMAIN>.com. 0 ANY TKEY        gss-tsig. 1547222072 1547222072 3 NOERROR 1397 YIIFcQYGKwYBBQUCoIIFZTCCBWGgDTALBgkqhkiG9xIBAgKiggVOBIIF SmCCBUYGCSqGSIb3EgECAgEAboIFNTCCBTGgAwIBBaEDAgEOo
Jan 11 09:54:32 dc01 sh[1181]: recvmsg reply from GSS-TSIG query
Jan 11 09:54:32 dc01 sh[1181]: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:  37632
Jan 11 09:54:32 dc01 sh[1181]: ;; flags: qr ra; QUESTION: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
Jan 11 09:54:32 dc01 sh[1181]: ;; QUESTION SECTION:
Jan 11 09:54:32 dc01 sh[1181]: ;1779289402.sig-dc01.corp.<DOMAIN>.com. ANY        TKEY
Jan 11 09:54:32 dc01 sh[1181]: ;; ANSWER SECTION:
Jan 11 09:54:32 dc01 sh[1181]: 1779289402.sig-dc01.corp.<DOMAIN>.com. 0 ANY TKEY        gss-tsig. 0 0 3 BADKEY 0  0
Jan 11 09:54:32 dc01 sh[1181]: dns_tkey_gssnegotiate: TKEY is unacceptable
Jan 11 09:54:32 dc01 dhcpd[1181]: execute: /usr/local/bin/dhcp-dyndns.sh exit status 2816
Jan 11 09:54:32 dc01 dhcpd[1181]: DHCPREQUEST for 172.20.10.165 from d4:be:d9:22:9f:7d via eno1
Jan 11 09:54:32 dc01 dhcpd[1181]: DHCPACK on 172.20.10.165 to d4:be:d9:22:9f:7d (mgmt01) via eno1


I appreciate the likelihood that this is some other issue on my part, but am a bit stuck on this (especially as this all worked in the "bad" system).


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

   


More information about the samba mailing list