[Pdns-users] Updated PDNS to Current, Now What?

[David Jones]

?Normally you should compare your active pdns.conf to the pdns.conf.rpmnew to see if there are any new features/options added.  Use "diff pdns.conf pdns.conf.rpmnew" to get the differences then ignore the same options that merely have your specific settings on the right side of the equals sign.  Look for differences in lines on the left side of the equals sign.


This is true in general for any new RPM package update, not just pdns.


________________________________
From: pdns-users-bounces at mailman.powerdns.com <pdns-users-bounces at mailman.powerdns.com> on behalf of Hoy Henry <hoy at datacruz.com>
Sent: Thursday, June 12, 2014 12:15 PM
To: pdns-users at mailman.powerdns.com
Subject: [Pdns-users] Updated PDNS to Current, Now What?

Good Day.   In November 2013 I  had successfully deployed  PDNS in a 2 server configuration with a web front end ans a MYSQL Backend.  Everything Worked Just Fine.   Today, without really thinking about it I ran a YUM Update and ultimately updated PDNS to the New current version (Along with everything else)   The 2 servers came up fine and appear to be working properly however I am paranoid that I might have missed something or not done something that I should have done.   I saw a message during the update about the updated pdns.conf file being named as pdns.conf.rpmnew  Should I be doing something with that?

Please excuse my Ignorance, I am still what I consider kind of new at all of this stuff....But as I break and fix things I feel I am getting better :)


Any help would be appreciated.

Thanks!

Hoy Henry

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20140612/dcb1668b/attachment-0001.html>