Error 30 when updating keyfile

22 Jan

nslookup Server: .228 Address: .228#53 Name: Address: .228 my file consist this // // // // Provided by Red Hat bind package to configure the ISC BIND named(8) DNS // server as a caching only nameserver (as a localhost DNS resolver only). The problem is that the Internet does not know how to find you for DNS lookups.// // See /usr/share/doc/bind*/samplix $TTL 86400 @ IN SOA ns1. ( 2011071001 ; Serial 3600 ; Refresh 1800 ; Retry 604800 ; Expire 86400 ; Minimum TTL ) @ IN NS ns1. @ IN A .228 @ IN A .228 and reverse.livedigix file consist of this vi /var/named/reverse.livedigix $TTL 86400 @ IN SOA ns1. ( 2011071001 ; Serial 3600 ; Refresh 1800 ; Retry 604800 ; Expire 86400 ; Minimum TTL ) @ IN NS ns1. You can't point your NS records to host names that are within your own domain. Because I don't know what IP address to send the query to for ns1.in order to lookup ns1.https:// sorry for the html tags i will keep that in mind.

Most Certificate Authorities let you add Subject Alternative Names when submitting the Certificate Signing Request to the Certificate Authority and thus there’s no reason to include Subject Alternative Names in the Certificate Signing Request.

so i installed the bind and followed the instructions on this link . Unless you have at least a /24 allocated to you most ISP's will not delegate PTR zones to you.

when i ssh the server and ping the host i get this result. 64 bytes from mail.(.228): icmp_seq=1 ttl=64 time=0.024 ms 64 bytes from mail.(.228): icmp_seq=2 ttl=64 time=0.053 ms 64 bytes from mail.(.228): icmp_seq=3 ttl=64 time=0.052 ms 64 bytes from mail.(.228): icmp_seq=4 ttl=64 time=0.047 ms 64 bytes from mail.(.228): icmp_seq=5 ttl=64 time=0.276 ms 64 bytes from mail.(.228): icmp_seq=6 ttl=64 time=0.053 ms 64 bytes from mail.(.228): icmp_seq=7 ttl=64 time=0.073 ms 64 bytes from mail.(.228): icmp_seq=8 ttl=64 time=0.047 ms 64 bytes from mail.(.228): icmp_seq=9 ttl=64 time=0.054 ms and when i check the nslookup i get this result while sshing the server. As for the forward setup, it most likely works on your VPS host because you are pointing it to itself for DNS lookup and your DNS configuration is technically correct.

You can replace the default management certificate with a new trusted management certificate.

Only one certificate will be loaded on both nodes in a High Availability pair so make sure the management certificate matches the names of both nodes.