Bug 773326

Summary: The full dyndns update message should be logged into debug logs
Product: Red Hat Enterprise Linux 6 Reporter: Stephen Gallagher <sgallagh>
Component: sssdAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED DUPLICATE QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: grajaiya, jgalipea, prc
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 773327 (view as bug list) Environment:
Last Closed: 2012-01-11 15:09:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 773327    

Description Stephen Gallagher 2012-01-11 14:42:02 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/893

Right now, the dynamic DNS update message is not logged anywhere. I suspect that the reason for not including it were security concerns.

I think the message should be logged, because the logs are readable by root only anyway and moreover the update message only contains the following data:

 * hostname of the client
 * IP addresses of clients's network interface (either the one the client uses to connect to LDAP or one selected in the sssd config file)
 * client DNS zone
 * Kerberos realm of the client
 * IPA server hostname

Adding the full nsupdate message would help in debugging dyndns issues as it would be possible to use the same message directly with nsupdate from the command line.
Comment 1 Stephen Gallagher 2012-01-11 15:09:05 UTC 

*** This bug has been marked as a duplicate of bug 766941 ***