Skocz do zawartości

tobroz

Użytkownicy
  • Zawartość

    4
  • Rejestracja

  • Ostatnio

Posty napisane przez tobroz


  1. Witam

    mam VPS na superhost.pl

     

    przy konfiguracji cpanelu pada pytanie

    1. czy tworzyć rekord A dla ns1.superhost.pl i ns2

    2. czy tworzyć rekord A dla hosta

    przypuszczam choć pewność mnie opuściła że:

    1. nie tworzyć bo rekord A jest już w superhost

    2. tworzyć bo to mój host i muszę się jakoś zidentyfikować.

    Czy dobrze myślę? Czy też nie myślę?

    Pozdrawiam

    Tomasz


  2. Witam

    po ciężkim dniu jest tak, chmody trzeba było w wielu miejscach zmienić...:

     

     

    root@vps146018 [~]# named -g
    22-Jul-2011 01:38:46.211 starting BIND 9.3.6-P1-RedHat-9.3.6-16.P1.el5 -g
    22-Jul-2011 01:38:46.211 found 8 CPUs, using 8 worker threads
    22-Jul-2011 01:38:46.212 using up to 4096 sockets
    22-Jul-2011 01:38:46.219 loading configuration from '/etc/named.conf'
    22-Jul-2011 01:38:46.246 max open files (1024) is smaller than max sockets (4096)
    22-Jul-2011 01:38:46.247 using default UDP/IPv4 port range: [1024, 65535]
    22-Jul-2011 01:38:46.248 using default UDP/IPv6 port range: [1024, 65535]
    
    [b]22-Jul-2011 01:38:46.251 listening on IPv4 interface lo, 127.0.0.1#53[/b]
    [b]22-Jul-2011 01:38:46.251 binding TCP socket: address in use[/b]
    [b]22-Jul-2011 01:38:46.252 listening on IPv4 interface venet0:0, 195.2.254.97#53[/b]
    [b]22-Jul-2011 01:38:46.252 binding TCP socket: address in use[/b]
    [b]22-Jul-2011 01:38:46.302 /etc/named.conf:4: couldn't add command channel 127.0.0.1#953: address in use[/b]
    [b]22-Jul-2011 01:38:46.302 the working directory is not writable[/b]
    [b]22-Jul-2011 01:38:46.303 ignoring config file logging statement due to -g option[/b]
    [b]
    [/b]
    22-Jul-2011 01:38:46.336 zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42
    22-Jul-2011 01:38:46.336 zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700
    22-Jul-2011 01:38:46.336 zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42
    22-Jul-2011 01:38:46.337 zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN/localhost_resolver: loaded serial 1997022700
    22-Jul-2011 01:38:46.337 zone localdomain/IN/localhost_resolver: loaded serial 42
    22-Jul-2011 01:38:46.338 zone localhost/IN/localhost_resolver: loaded serial 42
    22-Jul-2011 01:38:46.391 zone impresjaweb.com/IN/internal: loaded serial 2011071502
    22-Jul-2011 01:38:46.417 zone pracodawcagodnyzaufania.com/IN/internal: loaded serial 2011071402
    22-Jul-2011 01:38:46.438 zone fanaberie.eu/IN/internal: loaded serial 2011072002
    22-Jul-2011 01:38:46.438 zone kurier365.eu/IN/internal: loaded serial 2011071200
    22-Jul-2011 01:38:46.439 zone ns1.superhost.pl/IN/internal: loaded serial 2011072001
    22-Jul-2011 01:38:46.440 zone ns2.superhost.pl/IN/internal: loaded serial 2011072001
    22-Jul-2011 01:38:46.484 zone vps146018.superhost.pl/IN/internal: loaded serial 2011071901
    22-Jul-2011 01:38:46.509 zone zgaspapierosa.pl/IN/internal: loaded serial 2011071402
    22-Jul-2011 01:38:46.521 zone vps146018.superhost.pl.zz/IN/internal: loaded serial 2011070502
    22-Jul-2011 01:38:46.521 zone impresjaweb.com/IN/external: loaded serial 2011071502
    22-Jul-2011 01:38:46.522 zone pracodawcagodnyzaufania.com/IN/external: loaded serial 2011071402
    22-Jul-2011 01:38:46.522 zone fanaberie.eu/IN/external: loaded serial 2011072002
    22-Jul-2011 01:38:46.522 zone kurier365.eu/IN/external: loaded serial 2011071200
    22-Jul-2011 01:38:46.523 zone ns1.superhost.pl/IN/external: loaded serial 2011072001
    22-Jul-2011 01:38:46.523 zone ns2.superhost.pl/IN/external: loaded serial 2011072001
    22-Jul-2011 01:38:46.524 zone vps146018.superhost.pl/IN/external: loaded serial 2011071901
    22-Jul-2011 01:38:46.524 zone zgaspapierosa.pl/IN/external: loaded serial 2011071402
    22-Jul-2011 01:38:46.524 zone vps146018.superhost.pl.zz/IN/external: loaded serial 2011070502
    22-Jul-2011 01:38:46.526 running
    22-Jul-2011 01:38:46.526 zone zgaspapierosa.pl/IN/internal: sending notifies (serial 2011071402)
    22-Jul-2011 01:38:46.526 zone vps146018.superhost.pl.zz/IN/internal: sending notifies (serial 2011070502)
    22-Jul-2011 01:38:46.527 zone fanaberie.eu/IN/internal: sending notifies (serial 2011072002)
    22-Jul-2011 01:38:46.527 zone zgaspapierosa.pl/IN/external: sending notifies (serial 2011071402)
    22-Jul-2011 01:38:46.527 zone fanaberie.eu/IN/external: sending notifies (serial 2011072002)
    22-Jul-2011 01:38:46.527 zone kurier365.eu/IN/internal: sending notifies (serial 2011071200)
    22-Jul-2011 01:38:46.527 zone pracodawcagodnyzaufania.com/IN/internal: sending notifies (serial 2011071402)
    22-Jul-2011 01:38:46.527 zone ns1.superhost.pl/IN/internal: sending notifies (serial 2011072001)
    22-Jul-2011 01:38:46.528 zone kurier365.eu/IN/external: sending notifies (serial 2011071200)
    22-Jul-2011 01:38:46.528 zone pracodawcagodnyzaufania.com/IN/external: sending notifies (serial 2011071402)
    22-Jul-2011 01:38:46.528 zone ns1.superhost.pl/IN/external: sending notifies (serial 2011072001)
    22-Jul-2011 01:38:46.528 zone impresjaweb.com/IN/internal: sending notifies (serial 2011071502)
    22-Jul-2011 01:38:46.528 zone vps146018.superhost.pl/IN/internal: sending notifies (serial 2011071901)
    22-Jul-2011 01:38:46.529 zone ns2.superhost.pl/IN/internal: sending notifies (serial 2011072001)
    22-Jul-2011 01:38:46.529 zone vps146018.superhost.pl.zz/IN/external: sending notifies (serial 2011070502)
    22-Jul-2011 01:38:46.529 zone impresjaweb.com/IN/external: sending notifies (serial 2011071502)
    
    [b]22-Jul-2011 01:38:46.529 zone vps146018.superhost.pl/IN/external: sending notifies (serial 2011071901)
    22-Jul-2011 01:38:46.529 zone ns2.superhost.pl/IN/external: sending notifies (serial 2011072001)
    22-Jul-2011 01:38:46.529 network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
    22-Jul-2011 01:38:46.529 network unreachable resolving 'ns10.superhost.pl/A/IN': 2001:503:ba3e::2:30#53
    22-Jul-2011 01:38:46.530 network unreachable resolving 'ns10.superhost.pl/AAAA/IN': 2001:503:ba3e::2:30#53
    22-Jul-2011 01:38:46.661 network unreachable resolving 'ns10.superhost.pl/AAAA/IN': 2a02:1778:4::22:17#53

    [/b]

     

     

    ns10.super żyje sprawdziłem

     

    jakby ktoś miał coś, to chętnie ;)

     

    Pozdro

    Tom


  3. Na początek zrób coś z tym.

     

    Dzięki, idę za głosem i daje to efekty, następne permision denided, jak skończę zobaczymy.

    Dam znak

    Na swoje usprawiedliwienie, choć to słaba wymówka, że w jednym z bardzo wielu miejsc które przegrzebałem było żeby się tym nie przejmować. A był to podręcznik jakiejś szkoły...

    I tu przypomina się dowcip: Dlaczego nie wolno wierzyć w słowo pisane.

     

     

     


  4. Witam

    mam VPS na superhoście (centos)

    Podłączyłem do niego posługując się CPanelem kilka domen, tylko jedna zadziałała. Korzystam z ns1.suerhost.pl i ns2...

    Pliki stref są OK

    wygląda to tak jakby wpisy nie były wysyłane do DNS superhosta.

     

    i teraz:

     

    root@vps146018 [~]# named -g

    21-Jul-2011 11:58:59.921 starting BIND 9.3.6-P1-RedHat-9.3.6-16.P1.el5 -g

    21-Jul-2011 11:58:59.921 found 8 CPUs, using 8 worker threads

    21-Jul-2011 11:58:59.922 using up to 4096 sockets

    21-Jul-2011 11:58:59.930 loading configuration from '/etc/named.conf'

    21-Jul-2011 11:58:59.945 /etc/named.conf:1: open: /etc/rndc.key: permission denied

    21-Jul-2011 11:58:59.945 loading configuration: permission denied

    21-Jul-2011 11:58:59.946 exiting (due to fatal error)

     

    named.conf umieszczam bo nie wiem, właśnie się intensywnie douczam

     

    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/named").
    *      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 "kurier365.eu" {
    type master;
    file "/var/named/kurier365.eu.db";
    };
    
    zone "vps146018.superhost.pl.zz" {
    type master;
    file "/var/named/vps146018.superhost.pl.zz.db";
    };
    
    zone "fanaberie.eu" {
    type master;
    file "/var/named/fanaberie.eu.db";
    };
    
    zone "pracodawcagodnyzaufania.com" {
    type master;
    file "/var/named/pracodawcagodnyzaufania.com.db";
    };
    
    zone "zgaspapierosa.pl" {
    type master;
    file "/var/named/zgaspapierosa.pl.db";
    };
    
    zone "impresjaweb.com" {
    type master;
    file "/var/named/impresjaweb.com.db";
    };
    
    
    zone "vps146018.superhost.pl" {
    type master;
    file "/var/named/vps146018.superhost.pl.db";
    };
    
    };
    
    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 subnets:
    */
       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 "kurier365.eu" {
    type master;
    file "/var/named/kurier365.eu.db";
    };
    
    zone "vps146018.superhost.pl.zz" {
    type master;
    file "/var/named/vps146018.superhost.pl.zz.db";
    };
    
    zone "fanaberie.eu" {
    type master;
    file "/var/named/fanaberie.eu.db";
    };
    
    zone "pracodawcagodnyzaufania.com" {
    type master;
    file "/var/named/pracodawcagodnyzaufania.com.db";
    };
    
    zone "zgaspapierosa.pl" {
    type master;
    file "/var/named/zgaspapierosa.pl.db";
    };
    
    zone "impresjaweb.com" {
    type master;
    file "/var/named/impresjaweb.com.db";
    };
    
    
    zone "vps146018.superhost.pl" {
    type master;
    file "/var/named/vps146018.superhost.pl.db";
    };
    
    };
    
    
    

×