[URGENT !!] Setting DNS Server Menggunakan BIND


Status
Not open for further replies.

Ruby On Rails

Beginner 1.0
saya saykin masalah allow-query, kl ditest di servernya langsung (localhost dan 103.31.xxx.0/24) mau resolv, sedangkan ip diluar itu pasti error, jadi disetting allow-query { any; };

hasil nya gini Tuan

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13011
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1


bisa liat isi dari named.conf ?

sama liat file zone yg dibuat yg ada di /var/named/
ini Tuan saya di paste di pastebin, soalnya post disini gabisa..

pastebin.com/gBQ8c9CA

kok jadi REFUSED ya?
coba cek SELinux sama firewall nya

Code:
# sestatus

# iptables -L

[root@user sysconfig]# sestatus
SELinux status: disabled
[root@user sysconfig]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
 

Ruby On Rails

Beginner 1.0
Sekarang sudah bisa buka domainnya Tuan tapi di intodns belum fix semua

Mismatched NS records WARNING:
One or more of your nameservers did not return any of your NS records.

DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
103.31.xxx.126

SOA record No valid
SOA record came back!

MX MX Records Oh well,
I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!
 

Fuji Ahmad

Apprentice 2.0
hasil nya gini Tuan

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13011
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

pesan diatas statusnya NOERROR alias udah bener,
Answer 1 artinya hanya ada 1 A record, Authority 2 artinya ada 2 NS, Additional 1 berarti ns1 sama ns2 terdeteksi dan IP nya sama.
 

andhi

Hosting Guru
dibikin jd satu aja mas untuk zonenya coba bikin baru pake nama namadomain.info.zone


Code:
$TTL 14400
@      86400    IN      SOA     ns1.namadomain.info. admin.namadomain.info. (
                2013022802      ; serial, todays date+todays
                86400           ; refresh, seconds
                7200            ; retry, seconds
                3600000         ; expire, seconds
                86400 )         ; minimum, seconds

namadomain.info. IN NS ns1.namadomain.info.
namadomain.info. IN NS ns2.namadomain.info.


namadomain.info. IN A ipnya

ns1 IN A ipnya

ns2 IN A ipnya

localhost.namadomain.info. IN A 127.0.0.1

namadomain.info. IN MX 0 namadomain.info.

www IN CNAME namadomain.info.
ftp IN A ipnya
 

Ruby On Rails

Beginner 1.0
pesan diatas statusnya NOERROR alias udah bener,
Answer 1 artinya hanya ada 1 A record, Authority 2 artinya ada 2 NS, Additional 1 berarti ns1 sama ns2 terdeteksi dan IP nya sama.

kira kira masalah yang terakhir itu kenapa ya Tuan di cek di intodns masih belum fix semua. tapi domainnya udah bisa di akses..

kira-kira masalah yang tadi (yang awal) kenapa ya bisa seperti itu, bisa dijelasin ga kenapa mesti query nya any?
kalo misalkan any berarti siapa saja bisa nge query dong Tuan.
 

Ruby On Rails

Beginner 1.0
dibikin jd satu aja mas untuk zonenya coba bikin baru pake nama namadomain.info.zone


Code:
$TTL 14400
@      86400    IN      SOA     ns1.namadomain.info. admin.namadomain.info. (
                2013022802      ; serial, todays date+todays
                86400           ; refresh, seconds
                7200            ; retry, seconds
                3600000         ; expire, seconds
                86400 )         ; minimum, seconds

namadomain.info. IN NS ns1.namadomain.info.
namadomain.info. IN NS ns2.namadomain.info.


namadomain.info. IN A ipnya

ns1 IN A ipnya

ns2 IN A ipnya

localhost.namadomain.info. IN A 127.0.0.1

namadomain.info. IN MX 0 namadomain.info.

www IN CNAME namadomain.info.
ftp IN A ipnya


kalo di named.conf nya itu 1 zone aja Tuan? untuk query nya gimana?
 

andhi

Hosting Guru
Code:
include "/etc/rndc.key";

controls {
        inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
};

options {
    /* make named use port 53 for the source of all queries, to allow
         * firewalls to block all ports except 53:
         */

    // query-source    port 53;

    /* We no longer enable this by default as the dns posion exploit
        has forced many providers to open up their firewalls a bit */

    // Put files that named is allowed to write in the data/ directory:
    directory                "/var/named"; // the default
    pid-file                 "/var/run/named/named.pid";
    dump-file                "data/cache_dump.db";
    statistics-file          "data/named_stats.txt";
   /* memstatistics-file     "data/named_mem_stats.txt"; */
    allow-transfer {"none";};
};

logging {
/*      If you want to enable debugging, eg. using the 'rndc trace' command,
 *      named will try to write the 'named.run' file in the $directory (/var/nam                                                                                        ed").
 *      By default, SELinux policy does not allow named to modify the /var/named                                                                                        " directory,
 *      so put the default debug log file in data/ :
 */
    channel default_debug {
            file "data/named.run";
            severity dynamic;
    };
};


// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.

view "localhost_resolver" {
/* This view sets up named to be a localhost resolver ( caching only nameserver                                                                                         ).
 * If all you want is a caching-only nameserver, then you need only define this                                                                                         view:
 */
    match-clients         { 127.0.0.0/24; };
    match-destinations    { localhost; };
    recursion yes;

    zone "." IN {
        type hint;
        file "/var/named/named.ca";
    };

    /* these are zones that contain definitions for all the localhost
     * names and addresses, as recommended in RFC1912 - these names should
     * ONLY be served to localhost clients:
     */
    include "/var/named/named.rfc1912.zones";
};

view "internal" {
/* This view will contain zones you want to serve only to "internal" clients
   that connect via your directly attached LAN interfaces - "localnets" .
 */
    match-clients        { localnets; };
    match-destinations    { localnets; };
    recursion yes;

    zone "." IN {
        type hint;
        file "/var/named/named.ca";
    };

    // include "/var/named/named.rfc1912.zones";
    // you should not serve your rfc1912 names to non-localhost clients.

    // These are your "authoritative" internal zones, and would probably
    // also be included in the "localhost_resolver" view above :

zone "namadomain.info" {
        type master;
        file "/var/named/namadomain.info.zone";
};




};

view    "external" {
/* This view will contain zones you want to serve only to "external" clients
 * that have addresses that are not on your directly attached LAN interface subn                                                                                        ets:
 */
    recursion no;
    // you'd probably want to deny recursion to external clients, so you don't
    // end up providing free DNS service to all takers

    // all views must contain the root hints zone:
    zone "." IN {
        type hint;
        file "/var/named/named.ca";
    };

    // These are your "authoritative" external zones, and would probably
    // contain entries for just your web and mail servers:

    // BEGIN external zone entries

zone "namadomain.info" {
        type master;
        file "/var/named/namadomain.info.zone";
};

};

diatas sih setingan named.conf di vps saya :D sama file zone td itu setingan di vps jg ya coba aja dulu :D

klo di dig kaya gini

Code:
[root@xxxx named]# dig namadomain.info

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>> cyberdata.info
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9103
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;namadomain.info.                        IN      A

;; ANSWER SECTION:
namadomain.info.         14400   IN      A       ipnya

;; Query time: 48 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat May  4 16:12:20 2013
;; MSG SIZE  rcvd: 48
 
Status
Not open for further replies.

Top