[syslog-ng] [Bug 169] New: Feature Request - reconnect network also resolve dns name
bugzilla at bugzilla.balabit.com
bugzilla at bugzilla.balabit.com
Sat Mar 24 02:39:49 CET 2012
https://bugzilla.balabit.com/show_bug.cgi?id=169
Summary: Feature Request - reconnect network also resolve dns
name
Product: syslog-ng
Version: 3.3.x
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: unspecified
Component: syslog-ng
AssignedTo: bazsi at balabit.hu
ReportedBy: erempel at uvic.ca
Type of the Report: ---
Estimated Hours: 0.0
When a network connection is dropped the destination name should be resolved via DNS prior to the reconnect.
Every couple of years to renew the hardware supporting our core syslog service we move the IP name to
a new host. The desired process is;
1. Build a new host and ensure that syslog-ng is running correctly.
2. Change the DNS for our central syslog server to the address of the new server.
3. Restart the syslog-ng service on the old syslog server.
4. All of the clients will loose the connection to the old syslog server.
5. All of the clients will reconnect to the *IP Name* in their configuration files.
6. Monitor the old syslog server to determine any hosts that have not made the transition.
What really happened in step 5 was that all of the client reconnected to the old syslog server :-(
To accomplish the switch over I had to visit 450 servers and manually restart the syslog service on the
client.
--
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the syslog-ng
mailing list