Kvm - Problem Z Konfiguracją

[mskiba]

Dzięki. Pomoglo dodanie bramy:

GATEWAY=192.168.122.1

[mskiba]

Pojawil sie jeszcze jeden problem, ale z innej beczki

 

Na jednym z gosci skonfigurowalem binda:

 

/etc/named.conf

//
// named.conf
//
// 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).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//

options {
        listen-on port 53 { 127.0.0.1; };
        listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        allow-query     { localhost; };

        /* 
         - If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.
         - If you are building a RECURSIVE (caching) DNS server, you need to enable 
           recursion. 
         - If your recursive DNS server has a public IP address, you MUST enable access 
           control to limit queries to your legitimate users. Failing to do so will
           cause your server to become part of large scale DNS amplification 
           attacks. Implementing BCP38 within your network would greatly
           reduce such attack surface 
        */
        recursion yes;

        dnssec-enable yes;
        dnssec-validation yes;
        dnssec-lookaside auto;

        /* Path to ISC DLV key */
        bindkeys-file "/etc/named.iscdlv.key";

        managed-keys-directory "/var/named/dynamic";

        pid-file "/run/named/named.pid";
        session-keyfile "/run/named/session.key";
};

logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};

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


include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";

zone "test.pl" {
        type master;
        file "/var/named/test.pl";
        allow-query { any; };
        notify yes;
};

 

/var/named/test.pl

$TTL 86400
$ORIGIN test.pl.

@       IN      SOA     ns1.test.pl. root.test.pl. (
        2011022400 ;; Serial
        2d         ;; Refresh
        15m        ;; Update retry
        2w         ;; Expiry
        1h         ;; Minimum
)

@       IN      NS      ns1.test.pl.

ns1     IN      A       192.168.122.10
@       IN      A       192.168.122.10
bayer   IN      A       192.168.122.100

cat /etc/resolv.conf

nameserver 127.0.0.1
nameserver 192.168.122.1

nslookup test.pl

Server:         127.0.0.1
Address:        127.0.0.1#53

Name:   test.pl
Address: 192.168.122.10

Do tej pory wszystko pieknie.

 

Problem pojawia sie gdy chce na innym gosciu wykonac to samo polecenie

 

INNY GOSC:

 

cat /etc/resolv.conf

nameserver 192.168.122.10 - to jest adres serwera dns

nslookup test.pl

;; connection timed out; trying next origin
;; connection timed out; no servers could be reached

Gdzie czegos nie zrobilem Z gory dziekuje za pomoc.

[Miszcz]

To jest twój problem :

listen-on port 53 { 127.0.0.1; };

Dla każdego systemu adres 127.0.0.1 to jest on sam. Zamień to na właściwy adres serwera i powinno banglać. 

Ponadto polecam na przyszłość polecenie: netstat -tulpn (czyli co i na jakim adresie nasłuchuje).

[mskiba]

Dzieki za pomoc, ale udalo mi sie do tego dojsc chwile po napisaniu posta

 

Tak jak mowiles:

listen-on port 53 { 127.0.0.1; 192.168.122.0/24; };

to zalatwilo sprawe, plus odblokowanie portu 53.

 

 

Jeszcze jedno:

Dodalem domene: test.pl juz na kazdym gosniu ladnie rozwiazuje ta nazwe. Jak dodam adres ip np:

autobaza        IN      A       192.168.122.100

to czy jest jakas mozliwosc, zeby na gosciach pingowac to wywoluja tylko:

 

ping autobaza

 

W windowsie dodaje sie po prostu dns w ustawieniach karty sieciowej, a na fedorce nie moge tego znalezc

[mskiba]

Znalazlem

/etc/resolv.conf

search test.pl

[mskiba]

Mam jeszcze pytanko, jak na gosciu w konsoli sprawdzic jak nazywa sie dysk na gospodarzu?

[root@md01 dev]# lsblk 
NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sr0              11:0    1 1024M  0 rom  
vda             252:0    0   10G  0 disk 
├─vda1          252:1    0  200M  0 part /boot
└─vda2          252:2    0  7,8G  0 part 
  ├─md01vg-root 253:0    0  4,9G  0 lvm  /
  ├─md01vg-swap 253:1    0 1000M  0 lvm  [SWAP]
  ├─md01vg-home 253:2    0 1000M  0 lvm  /home
  └─md01vg-var  253:3    0 1000M  0 lvm  /var
vdb             252:16   0    2G  0 disk 
vdc             252:32   0    2G  0 disk 
vdd             252:48   0    2G  0 disk 
vde             252:64   0    2G  0 disk 
vdf             252:80   0    2G  0 disk 
vdg             252:96   0    2G  0 disk 
vdh             252:112  0    2G  0 disk 
vdi             252:128  0    2G  0 disk 
vdj             252:144  0    2G  0 disk 
vdk             252:160  0    2G  0 disk 

chodzi mi o te dyski

vdb             252:16   0    2G  0 disk 
vdc             252:32   0    2G  0 disk 

[Miszcz]

Raczej nie wydaje mi się, że to jest możliwe.