CentOS

What do you mean by:
My Issue is when I search for my servers Info itself

In general only what is the the CN (Common Name) of the certificates certificate as well as an items in the SAN (Subject Alternative Name) of the certificate are what a client will accept as being a valid host to connect to. Most clients do not do reverse DNS lookup to avoid poisoned DNS entry attac...

I support over 100 linux server running either RHEL and CentOS. We do build out own OpenSSL and various services for our needs. This is a full time job to mange the patching and versions releases. Unless you are willing and able to devote a lot of time to doing this you are far better off leaving it...

I work on 120+ linux servers maintaing environments for Web and Java applications. We run a mixture of RedHat, CentOS and Oracle Linux, mainly CentOS but RedHat or Oracle Linux only if required. These were chosen for their stability and vender certification for their applications. When dealing with ...

I deal with many CentoOS servers that have been updated to 6.5 and we rely heavily on sudo for developers to access application UIDs and we have not see any issues.

All BIND does is resolve a name to an IP address or IP address to a name. There is no routeing involved.

If you are hosting multiple domains in BIND you need to have individual zone files for each domain you are going to resolve for.

The "dc=example,dc=com" is normally used to define the LDAP search base not the host to bind to and doesn't require DNS entry.

Is there a host entry on the phone configuration for LDAP user lookup? Or does it look for a _ldap._tcp SRV entry in DNS?

This kind of error is usually caused by the server not providing the entire CA chain to a client. Most browser trust stores have the CA Root certificates of the public CAs. When a browser connects to an SSL site the the server will send the host certificate as well as the whole CA chain and if the r...

As someone who is new to linux it is probably not a good thing to try and setup your own firewall. Hardened appliances like the SonicWall are inherently more secure that a general purpose computer. If you still want to move away from the SonicWall I would suggest using something like pfSense instead...

You need to bind the dhcpd service to the eth1 interface only. You do this in /etc/sysconfig/dhcpd by adding the name of the interface to the list of DHCPDARGS:
DHCPDARGS=eth1