Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 12 of 12
Of course you can host your own domain, but it is customary to have two name servers, and a fixed IP address. It would be a bit awkward to do ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Engineer rcgreen's Avatar
    Join Date
    May 2006
    Location
    the hills
    Posts
    1,134

    Of course you can host your own domain, but it is customary
    to have two name servers, and a fixed IP address. It would be a bit awkward to
    do it on a consumer grade internet connection. (your isp could advise you).
    They may insist that you pay for more bandwidth, or put other conditions
    on it. Check Dyndns. There are ways to work around these issues.

  2. #12
    Just Joined!
    Join Date
    Jul 2007
    Posts
    5
    So here is a setup I use for this.

    Step 1: Register your domain via provider, i.e. Misk.com - Domains, Essentials, Email
    Step 2: Once you register your domain, you then would give the provider your nameserver ip address ( I know misk.com will allow you to create a custom nameserver record by IP )
    Step 3: configure BIND to host your domain.

    Now I use a single server with 2 network cards. One on a local network and the other is public. Since I use one server hosting internal and external DNS, I needed to take advantage of Views in BIND.

    /etc/named.conf


    Code:
    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 { 222.222.222.222; };
    
    	# 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;
    };
    
    controls {
    	inet 127.0.0.1 port 953
    		allow { 127.0.0.1; } keys { "rndc-key"; };
    };
    
    # 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.
    
    acl internal { 127.0.0.1; 172.16.0.0/16; };
    
    view "private" {
    	match-clients { internal; };
    	recursion yes;
    
    	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";
    	};
    
    	zone "mydomain.local" in {
    		type master;
    		file "master/mydomain.local.db";
    		allow-query { internal; };
    		allow-update { key rndc-key; };
    	};
    
    	zone "0.16.172.in-addr.arpa" in {
    		type master;
    		file "master/mydomain.local.reverse.db";
    		allow-query { internal; };
    		allow-update { key rndc-key; };
    	};
    };
    
    view "public" {
    	match-clients { any; };
    	recursion no;
    
    	zone "mydomain.us" in {
    		type master;
    		file "master/mydomain.us.db";
    	};
    };
    
    include "/etc/rndc.key";
    include "/etc/named.conf.include";
    I also host DHCP and DDNS on my local NIC -

    master/mydomain.local.db

    Code:
    $TTL 604800	; 1 week
    mydomain.local		IN SOA	master.mydomain.local. root.mydomain.local. (
    				128        ; serial
    				172800     ; refresh (2 days)
    				14400      ; retry (4 hours)
    				3628800    ; expire (6 weeks)
    				604800     ; minimum (1 week)
    				)
    			NS	master.mydomain.local.
    ftp			CNAME	master
    mail			CNAME	master
    master		A	172.16.0.1
    www			CNAME	master
    master/mydomain.us.db

    Code:
    $TTL 1W
    @		IN SOA	master.mydomain.us.   root.mydomain.us. (
    				42		; serial (d. adams)
    				2D		; refresh
    				4H		; retry
    				6W		; expiry
    				1W )		; minimum
    
    		IN NS		master.mydomain.us.
    		IN MX	10	master.mydomain.us.
    master		IN A		333.333.333.333
    www		IN CNAME	master
    ftp		IN CNAME	master
    smtp		IN CNAME	master
    mail		IN CNAME	master
    I hope this helps. I have several domains hosted on my server. When adding a new domain I just add to the public view in the named.conf.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •