UNIX, Linux, Programare, Scripting, Retele
unix, linux, programare, script, hosting, server, retele
Lista Forumurilor Pe Tematici
UNIX, Linux, Programare, Scripting, Retele | Reguli | Inregistrare | Login

POZE UNIX, LINUX, PROGRAMARE, SCRIPTING, RETELE

Nu sunteti logat.
Nou pe simpatie:
surender_lady
Femeie
25 ani
Arad
cauta Barbat
26 - 47 ani
UNIX, Linux, Programare, Scripting, Retele / UNIX / Server dns pe suse 10.0 naravas rau !  
Autor
Mesaj Pagini: 1
fasole
Newbi

Inregistrat: acum 19 ani
Postari: 32
Doua pc-uri simple cu suse pe ele .
Pc1 are instalat apacheul si tot pe el si dns server , si samba server pt . relatiile cu celelate pc-uri din windows.
Pc2 numai susele fara nici un server in afara de samba server .
       Pc1-- 192.168.3.105   (veb)                         pc2 - 192.168.3.104   toate pe 255.255.240.0 (netmask)
De vazut se vad in smb explorer , vad si restul retelei , merg pingurile ok pe toate directile .
pe pc1 se pune la domain name pt. dns server workgroup ca sa corespunda cu pc2 .
Local in mozilla la introducerea http://localhost fumctioneaza apacheul.
DAr cand se introduce adresa http://veb in pc2 (mozila brovser) nu apare decat mesajul urm:
Name Error: The domain name does not exist.

I need help !


_______________________________________


pus acum 19 ani
   
operabilus
B.O.F.H.

Din: Sillycon Valley
Inregistrat: acum 20 ani
Postari: 200
PC2 are in /etc/resolv.conf IP-ul pentru PC1 ?
PC1 are editata zona corespunzatoare pentru "veb" ?
Ping pe veb zice ceva ?


_______________________________________
Portal SkullBox
SkullBox Forum
IP Finder and web browser details revealer


pus acum 19 ani
   
fasole
Newbi

Inregistrat: acum 19 ani
Postari: 32
pe pc2 la /etc/resolv.conf este asa
   nameserver 192.168.3.105
   search workgroup
numai liniile astea .

pc1 are editata zona corespunzatoare pt. "veb"  nu am inteles intrebarea !

La ping veb e ok :

64 bytes from veb.workgroup (192.168.3.105): icmp_seq=4 ttl=64 time=0.216 ms
64 bytes from veb.workgroup (192.168.3.105): icmp_seq=5 ttl=64 time=0.231 ms
64 bytes from veb.workgroup (192.168.3.105): icmp_seq=6 ttl=64 time=0.208 ms
64 bytes from veb.workgroup (192.168.3.105): icmp_seq=7 ttl=64 time=0.233 ms
64 bytes from veb.workgroup (192.168.3.105): icmp_seq=8 ttl=64 time=0.207 ms
64 bytes from veb.workgroup (192.168.3.105): icmp_seq=9 ttl=64 time=0.223 ms
64 bytes from veb.workgroup (192.168.3.105): icmp_seq=10 ttl=64 time=0.206 ms
64 bytes from veb.workgroup (192.168.3.105): icmp_seq=11

I wait next instroctions !


_______________________________________


pus acum 19 ani
   
operabilus
B.O.F.H.

Din: Sillycon Valley
Inregistrat: acum 20 ani
Postari: 200
Ai putea sa areti aici un named.conf ? Daca e local banuiesc ca nu ar fi o problema...

Si referitor la zona... vroiam sa stiu daca exista in named.conf un bloc de genul:

Code:

zone "veb"{
   type master;
   file "veb.zone";
}

iar fisierul "veb.zone" are un continut de genul:

Code:

$TTL 1D
@         IN    SOA veb.  veb(
                         1234567890
                         1D
                         2H
                         1W
                         1D)
           IN    NS  ns.web

veb.     IN    A    192.168.3.105

Bineinteles, chestiile de mai sus nu-s batute in cuie, da' cam asa ar trebui sa arate...


_______________________________________
Portal SkullBox
SkullBox Forum
IP Finder and web browser details revealer


pus acum 19 ani
   
fasole
Newbi

Inregistrat: acum 19 ani
Postari: 32
ok ! I wait !

Modificat de fasole (acum 19 ani)


_______________________________________


pus acum 19 ani
   
fasole
Newbi

Inregistrat: acum 19 ani
Postari: 32
named.conf is :

# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Frank Bodammer, Lars Mueller < >
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND 9.  It works as
# a caching only name server without modification.
#
# A sample configuration for setting up your own domain can be found in
# /usr/share/doc/packages/bind/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind/misc/options.

options {

    # The directory statement defines the name server's working directory

    directory "/var/lib/named";

    # Write dump and statistics file to the log subdirectory.  The
    # pathenames are relative to the chroot jail.

    dump-file "/var/log/named_dump.db";
    statistics-file "/var/log/named.stats";

    # The forwarders record contains a list of servers to which queries
    # should be forwarded.  Enable this line and modify the IP address to
    # your provider's name server.  Up to three servers may be listed.

    #forwarders { 192.0.2.1; 192.0.2.2; };

    # Enable the next entry to prefer usage of the name server declared in
    # the forwarders section.

    #forward first;

    # The listen-on record contains a list of local network interfaces to
    # listen on.  Optionally the port can be specified.  Default is to
    # listen on all interfaces found on your system.  The default port is
    # 53.

    #listen-on port 53 { 127.0.0.1; };

    # The listen-on-v6 record enables or disables listening on IPv6
    # interfaces.  Allowed values are 'any' and 'none' or a list of
    # addresses.

    listen-on-v6 { any; };

    # The next three statements may be needed if a firewall stands between
    # the local server and the internet.

    #query-source address * port 53;
    #transfer-source * port 53;
    #notify-source * port 53;

    # The allow-query record contains a list of networks or IP addresses
    # to accept and deny queries from. The default is to allow queries
    # from all hosts.

    #allow-query { 127.0.0.1; };

    # If notify is set to yes (default), notify messages are sent to other
    # name servers when the the zone data is changed.  Instead of setting
    # a global 'notify' statement in the 'options' section, a separate
    # 'notify' can be added to each zone definition.

    notify no;
    include "/etc/named.d/forwarders.conf";
};

# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
#    # Log queries to a file limited to a size of 100 MB.
#    channel query_logging {
#        file "/var/log/named_querylog"
#            versions 3 size 100M;
#        print-time yes;            // timestamp log entries
#    };
#    category queries {
#        query_logging;
#    };
#
#    # Or log this kind alternatively to syslog.
#    channel syslog_queries {
#        syslog user;
#        severity info;
#    };
#    category queries { syslog_queries; };
#
#    # Log general name server errors to syslog.
#    channel syslog_errors {
#        syslog user;
#        severity error;
#    };
#    category default { syslog_errors;  };
#
#    # Don't log lame server messages.
#    category lame-servers { null; };
#};

# The following zone definitions don't need any modification.  The first one
# is the definition of the root name servers.  The second one defines
# localhost while the third defines the reverse lookup for localhost.

zone "." in {
    type hint;
    file "root.hint";
};

zone "localhost" in {
    type master;
    file "localhost.zone";
};

zone "0.0.127.in-addr.arpa" in {
    type master;
    file "127.0.0.zone";
};

# Include the meta include file generated by createNamedConfInclude.  This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named

include "/etc/named.conf.include";
logging {
    category queries { log_syslog; };
    category default { log_syslog; };
    channel log_syslog { syslog; };
};
zone "workgroup" in {
    allow-transfer { any; localhost; localnets; };
    file "master/workgroup";
    type master;
};

# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.


IAR IN /var/lib/named unde ar trebui sa fie fisierul veb.zone NU ESTE NIMIC , NICI IN CELELALTE SUBFOLDERE AL LUI /VAR/LIB

Se vede ca chiar stii pe suse cum sta treaba !


_______________________________________


pus acum 19 ani
   
fasole
Newbi

Inregistrat: acum 19 ani
Postari: 32
deci , eu am bifat si allow-query .......... si tot de geaba .
???????????????????????????


_______________________________________


pus acum 19 ani
   
fasole
Newbi

Inregistrat: acum 19 ani
Postari: 32
ANTICIPAND intrebarea , ce ai in /var/lib/named/master  : un singur fisier denumit workgroup care  e compus asa :

$TTL 3d
@        IN SOA        veb.workgroup.    root.veb.workgroup. (
                2006091200    ; serial
                3h        ; refresh
                1h        ; retry
                1w        ; expiry
                1d )        ; minimum

web1        IN A        192.168.3.104
veb        IN A        192.168.3.105

unde web1 este hostname-ul lui pc2


_______________________________________


pus acum 19 ani
   
fasole
Newbi

Inregistrat: acum 19 ani
Postari: 32
am luat veb.zone ce ai aratat si l-am introdus in /var/lib/named si tot la fel =>

EROARE
URL-ul cerut nu a putut fi citit
ÃŽn timp ce citeam URL-ul: http://veb/
Am întâlnit următoarea eroare:
Nu pot determina adresa IP din numele host-ului pentru veb
Serverul de DNS a returnat:
Name Error: The domain name does not exist.
Aceasta înseamnă că:
Cache-ul nu a putut rezolva numele host-ului scris în URL.
Verificaţi dacă adresa este corectă.

Aceasta apare cand doresc sa accesez apacheul de pe pc1 .
Chiar daca in fisierul host din  /etc   
am asa pe pc2 :

#
# hosts         This file describes a number of hostname-to-address
#               mappings for the TCP/IP subsystem.  It is mostly
#               used at boot time, when no name servers are running.
#               On small systems, this file can be used instead of a
#               "named" name server.
# Syntax:
#   
# IP-Address  Full-Qualified-Hostname  Short-Hostname
#
192.168.3.105   veb.workgroup veb
127.0.0.1       localhost

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts
192.168.3.104   web1.workgroup web1


AICI MA OPRESC , ASTEPT REPLAY CU MULTUMIRI PT. TIMPUL ACORDAT , AR FII CHIAR CULMEA CA O SINGURA PERSOANA SA FACA CAT TOT FORUMUL LINUX.RO !


_______________________________________


pus acum 19 ani
   
operabilus
B.O.F.H.

Din: Sillycon Valley
Inregistrat: acum 20 ani
Postari: 200
Ioi... complicat... sper sa am timp in zilele astea sa fac un tutorial despre cum se configureaza un server DNS minimal. Is o gramada de chestii acolo care is in plus... dar nu incurca prea mult...
Anyway, in named.conf creaza o inregistrare cum am pus in postul anterior ( zone "veb" ) si apo creaza fisierul veb.zone care sa aiba continutul care e in al doilea exemplu din postul anterior (sau cum ai fisierul master cu diferenta ca inlocuiesti veb.workgroup cu veb si pui IP-urile corespunzatoare). Fa asa si vezi daca nu se rezolva problema.


offtopic: ai putea sa modifici posturile de mai sus si sa stergi tutorialele ? muta-le intr-o alta sectiune (Retele/unix) sau unde consideri ca se potrivesc cel mai bine si lasa aici doar link-uri catre tutoriale


_______________________________________
Portal SkullBox
SkullBox Forum
IP Finder and web browser details revealer


pus acum 19 ani
   
fasole
Newbi

Inregistrat: acum 19 ani
Postari: 32
lucrurile foarte simple sunt grele , tot nu merge si dupa modificarile indicate de tine !
Am zile de cand citesc tutoriale si fac teste si tot un drac ,  !!
Astept cu interes tutorialul !


_______________________________________


pus acum 19 ani
   
Pagini: 1  

Mergi la