Dynamic DNS

Discussion in 'HOWTO-Related Questions' started by TheMystery, Oct 16, 2007.

  1. TheMystery

    TheMystery New Member

    Hello i followed the how to for dynamic dns but it won't work.
    i have searched on the internet but it seems good to me.

    this are my configuration files

    zone files:
    Code:
    $TTL 86400	;1day
    
    @       IN     SOA    linux.example.com.     root.example.com. (
                        2007101601 ; serial
                        28800      ; refresh
                        7200       ; retry 
                        1209600    ; expire
                        1440 )     ; TTL
    
    
    	IN	NS	linux
    
    linux	IN	A	192.168.1.10
    Code:
    $TTL 86400	;1day
    
    @     IN     SOA    linux.example.com.     root.example.com. (
                        2007101601 ; serial
                        28800      ; refresh
                        7200       ; retry 
                        120960     ; expire
                        1440 )     ; TTL 
    
    	IN	NS	linux
    
    10	IN	PTR	linux.
    named.conf:
    Code:
    controls {
            inet 127.0.0.1 allow {linux; } keys { "rndckey"; };
    };
    
    zone "." {
    	type hint;
    	file "/etc/db.cache";
    };
    
    zone "example.com" IN {
           type master;
           file "/var/named/zones/db.example.com";
           allow-update { key "rndckey"; };
           notify yes;
    };
    
    zone "1.168.192.in-addr.arpa" {
           type master;
           file "/var/named/zones/db.1.168.192.in-addr.arpa";
           allow-update { key "rndckey"; };
           notify yes;
    };
    
    dhcp.conf:
    Code:
    authoritative;
    include "/etc/rndc.key";
    # Server configuration:
    
    server-identifier    linux;
    ddns-domainname         "example.com.";
    ddns-rev-domainname     "in-addr.arpa.";
    ddns-update-style       interim;
    ddns-updates            on;
    ignore                  client-updates;
    
    # This is the communication zone
    zone example.com. {
        primary 127.0.0.1;
        key rndckey;
    }
    
    default-lease-time 1200;
    max-lease-time 9200;
    
    # Client configuration:
    option ip-forwarding    off;
    subnet 192.168.1.0 netmask 255.255.255.0 {
    	range 192.168.1.20 192.168.1.100;
    	option subnet-mask 255.255.255.0;
    	option broadcast-address 192.168.1.255;
    	option routers 192.168.1.10;
    	option domain-name-servers 192.168.1.10;
    	option domain-name "example.com";
            zone  1.168.192.in-addr.arpa. {
                    primary 192.168.0.1;
                    key rndckey;
            }
            zone localdomain. {
                    primary 192.168.0.1;
                    key rndckey;
            } 
    }
    
    
    the directory /var/named is chmod 770

    is this good or not?
     
  2. falko

    falko Super Moderator ISPConfig Developer

    Which tutorial (URL) exactly? Which distribution are you using?
     
  3. TheMystery

    TheMystery New Member

    Last edited: Oct 17, 2007
  4. TheMystery

    TheMystery New Member

    this are now my configuration files

    dhcpd.conf:
    Code:
    authoritative;
    include "/etc/rndc.key";
    # Server configuration:
    
    server-identifier    linux;
    ddns-domainname         "moosdijk.com.";
    ddns-rev-domainname     "1.168.192.in-addr.arpa.";
    ddns-update-style       interim;
    ddns-updates            on;
    ignore                  client-updates;
    
    # This is the communication zone
    zone moosdijk.com. {
        primary 127.0.0.1;
        key rndckey;
    }
    
    default-lease-time 1200;
    max-lease-time 9200;
    
    # Client configuration:
    option ip-forwarding    off;
    subnet 192.168.1.0 netmask 255.255.255.0 {
    	range 192.168.1.20 192.168.1.100;
    	option subnet-mask 255.255.255.0;
    	option broadcast-address 192.168.1.255;
    	option routers 192.168.1.10;
    	option domain-name-servers 192.168.1.10;
    	option domain-name "moodijk.com";
            zone  1.168.192.in-addr.arpa. {
                    primary 192.168.0.1;
                    key rndckey;
            }
            zone localdomain. {
                    primary 192.168.0.1;
                    key rndckey;
            } 
    }
    
    
    named.conf:
    Code:
    controls {
            inet 127.0.0.1 port 953 
    	allow {127.0.0.1; } keys { "rndckey"; };
    };
    
    include "/etc/rndc.key";
    
    zone "." {
    	type hint;
    	file "/etc/db.cache";
    };
    
    zone "moosdijk.com" {
           type master;
           file "/var/named/zones/db.moosdijk.com.zone";
           allow-update { key "rndckey"; };
           notify yes;
    };
    
    zone "1.168.192.in-addr.arpa" {
           type master;
           file "/var/named/zones/db.1.168.192.in-addr.arpa";
           allow-update { key "rndckey"; };
           notify yes;
    };
    
    
    zone files:
    Code:
    $ORIGIN .
    $TTL 86400	; 1 day
    moosdijk.com		IN SOA	linux.moosdijk.com. root.moosdijk.com. (
    				2007101702 ; serial
    				28800      ; refresh (8 hours)
    				7200       ; retry (2 hours)
    				1209600    ; expire (2 weeks)
    				1440       ; minimum (24 minutes)
    				)
    			NS	linux.moosdijk.com.
    $ORIGIN moosdijk.com.
    linux			A	192.168.1.10
    $TTL 600	; 10 minutes
    winxp			A	192.168.1.97
    			TXT	"31177f6d1c7a91b4c31b091e23fa6235a0"
    
    this file is changed by dynamic dns


    reverse:
    Code:
    $TTL 86400	; 1 day
    
    @     IN     SOA    linux.moosdijk.com.     root.moosdijk.com. (
                        2007101701 ; serial
                        28800      ; refresh
                        7200       ; retry 
                        120960     ; expire
                        1440 )     ; TTL 
    
    	IN	NS	linux
    
    10	IN	PTR	linux.
    
    
     

Share This Page