Tuesday, December 6, 2016

Setting DNS update Desember 2016

named.conf.local

zone "cloudgng.com" {
        type master;
        file "/etc/bind/db.cloudgng.local-fwd";
};

zone "1.168.192.in-addr.arpa" {
        type master;
        file "/etc/bind/db.cloudgng.local-rev";
};

zone "." IN {
        type forward;
        forwarders { 192.168.1.61; 192.168.1.1; };
};

# zona lainnya

    zone "localhost" {
        type master;
        file "/etc/bind/db.local";
    };

    zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
    };

    zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
    };

    zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
    };

named.conf.options

dnssec-enable no;
dnssec-validation no;
dnssec-lookaside auto;

        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { none; };
};

db.cloudgng.local-fwd

; BIND data file for zone "cloudgng.local" [via] Internal view forward
;

$TTL    604800
@       IN      SOA     ns1.cloudgng.  root.cloudgng. (
                         2016112900     ; Serial
                             604800         ; Refresh
                              86400          ; Retry
                            2419200        ; Expire
                             604800 )       ; Negative Cache TTL
;
@               IN      NS          ns1.cloudgng.
@               IN      A           192.168.1.61


;ip vm

ubuntu60        IN      A       192.168.1.60
ubuntu61        IN      A       192.168.1.61
ubuntu62        IN      A       192.168.1.62
ns1             IN      A       192.168.1.61

db.cloudgng.local-rev

; BIND data file for REVERSE zone "1.168.192.in-addr.arpa"
;

$TTL    604800
@       IN      SOA     ns1.cloudgng.   ubuntu61.cloudgng. (
                         2016112900         ; Serial
                             604800             ; Refresh
                              86400              ; Retry
                            2419200            ; Expire
                             604800 )           ; Negative Cache TTL

@       IN      NS      ns1.cloudgng.

;PTR VM
60       IN      PTR     ubuntu60.
61       IN      PTR     ubuntu61.
62       IN      PTR     ubuntu62.
61       IN      PTR     ns1.

/bin/bash ./main permission denied

solusi :

Pada saat eksekusi program.. pindahkan file ke direktori home. :D

Friday, December 2, 2016

Mematikan suatu service di Linux secara permanent..

How to Kill a Process in Linux

In order to kill a running process in Linux, use the ‘Kill PID‘ command. But, before running Kill command, we must know the PID of the process. For example, here I want to find a PID of ‘cupsd‘ process.
[avishek@tecmint]# ps ax | grep cupsd
1511 ?        Ss     0:00 cupsd -C /etc/cups/cupsd.conf
So, the PID of ‘cupsd‘ process is ‘1511‘. To kill that PID, run the following command.
[avishek@tecmint]# kill -9 1511
To find out more about kill command with their examples, read the article A Guide to Kill Command to Terminate a Process in Linux

How to Disable a Services in Linux

In Red Hat based distributions such as Fedora and CentOS, make use of a script called ‘chkconfig‘ to enable and disable the running services in Linux.
For example, lets disable the Apache web server at the system startup.
[avishek@tecmint]# chkconfig httpd off
[avishek@tecmint]# chkconfig httpd --del
In Debian based distributions such as UbuntuLinux Mint and other Debian based distributions use a script called update-rc.d.
For example, to disable the Apache service at the system startup execute the following command. Here ‘-f’option stands for force is mandatory.
[avishek@tecmint]# update-rc.d -f apache2 remove
After making these changes, The system next time will boot without these UN-necessary process which in-fact will be saving our system resource and the server would be more practical, fast, safe and secure.

Thursday, December 1, 2016

dns error, network unreachable

Sep 11 15:47:59 zimbra named-sdb[4009]: error (network unreachable) resolving 'google.com/A/IN': 2001:7fd::1#53
Sep 11 15:47:59 zimbra named-sdb[4009]: error (network unreachable) resolving './NS/IN': 2001:7fd::1#53
Sep 11 15:48:02 zimbra named-sdb[4009]: error (network unreachable) resolving 'google.com/A/IN': 2001:dc3::35#53
Sep 11 15:48:02 zimbra named-sdb[4009]: error (network unreachable) resolving './NS/IN': 2001:dc3::35#53
Sep 11 15:48:10 zimbra named-sdb[4009]: error (network unreachable) resolving 'google.com/A/IN': 2001:500:1::803f:235#53
Sep 11 15:48:10 zimbra named-sdb[4009]: error (network unreachable) resolving 'google.com/A/IN': 2001:503:c27::2:30#53
Sep 11 15:48:10 zimbra named-sdb[4009]: error (network unreachable) resolving './NS/IN': 2001:500:1::803f:235#53
Sep 11 15:48:10 zimbra named-sdb[4009]: error (network unreachable) resolving './NS/IN': 2001:503:c27::2:30#53
Sep 11 15:48:22 zimbra named-sdb[4009]: error (network unreachable) resolving 'google.com/A/IN': 2001:503:ba3e::2:30#53
Sep 11 15:48:22 zimbra named-sdb[4009]: error (network unreachable) resolving './NS/IN': 2001:503:ba3e::2:30#53


solusi, setting di named.conf.options di bind

dnssec-enable no;

dnssec-validation no;
dnssec-lookaside auto;