Hey,
When using remote logging (*.* @syslog.example.com) "syslog" is an alias
(CNAME with low TTL) in our DNS, like all service names.
Now it seems when we change this alias' destination in DNS, the change
is never picked up. Not even on reload, only on restart. On reload would
at least make it use the new IP address after logrotation for example.
I don't even think it's about rsyslog. Seems to be how all syslog
implementations usually behave. But it is still a topic of discussion:
Are people just not using hostnames? I understand that for example on
network equipment you would rather hardcode IPs than use hostnames. But
what do you do on the servers?
Is there a best practice with valid reasons why it should be done that
way? What do you think?
Cheers.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
