You are not logged in.

#1 2015-04-26 03:33:43

wolfdogg
Member
From: Portland, OR, USA
Registered: 2011-05-21
Posts: 545

bind, will it work for local dev dns? [solved]

im trying to get bind to work, and trying to get my stack overflow points up lately too,
will bind work for what i need it for?

i have a lamp stack arch box here, and im putting bind on it, hopefully to solve an issue.  briefly, i want this lamp stack to also be my internal network's dns server,  for a specific purpose.  that purpose is so that on my windows dev machine, i dont have to fuck with my etc/hosts file any more, and so that i can finally designate this lamp stack server with a real domain name structure (e.g. on httpd.conf ServeName=finally.domain.pvt, as opposed to ServerName=192.168.1.10:80, and so that i can simplify my vhosts file too, by having a domain standard finally.  so i aim to replace etc/hosts entries (e.g. shitter.domain.pvt, pisser.domain.pvt, pooper.domain.pvt, ideally into *.domain.pvt on zone file) with A record entries so they are propegated to all pcs on the network.  is this possible?

see this for all the details.
http://stackoverflow.com/questions/2987 … -on-server

Last edited by wolfdogg (2015-04-27 08:00:41)


Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Offline

#2 2015-04-26 08:26:47

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: bind, will it work for local dev dns? [solved]

You're asking whether BIND is a DNS server. Yes, of course it is.

Offline

#3 2015-04-26 22:11:20

wolfdogg
Member
From: Portland, OR, USA
Registered: 2011-05-21
Posts: 545

Re: bind, will it work for local dev dns? [solved]

ok so atleast im not going crazy.  and i have chosen a domain, ld.pvt is what its going to me.  so form my websites, wolfdogg.org, i want to map it into /home/wolfdogg/sites/wolfdogg.org, and the domain to be wolfdogg.org.ld.pvt to make it internal.  so im guessing the zone file is ld.pvt, but is teh nameserver whoms hostname is falcon become falcon.ld.pvt, or is that separate totally to where i can call it ns1.ld.pvt?  this part i cant get past.

then, i want forwarders(e.g. 8.8.8.8), but not forward only right?  i.e., it would be great to experiment by setting my redtail dev box DNS settings to point to this falcon box dns server.   so  barring figuring out what to name my dns server, (either falcon.ld.pvt, or ns1.ld.pvt which is on falcon.ld.pvt).  am i on the right track so far?



what i want is to have my arch box


Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Offline

#4 2015-04-27 07:59:41

wolfdogg
Member
From: Portland, OR, USA
Registered: 2011-05-21
Posts: 545

Re: bind, will it work for local dev dns? [solved]

solved

one problem was being shed light from

journalctl -xn

, i needed to do what was mentioned here https://bbs.archlinux.org/viewtopic.php … 4#p1391324  to solve those issues. the file, and dir were missing.

the rest of teh problems were worked out with a better understanding of the zone file, and with finally getting logging working ( see named.conf for that)

if somebody wants to add this to the wiki, and or make a wiki called local dns server, or something, feel free, otherwise, i will end up getting this stuff in there in due time. 

// vim:set ts=4 sw=4 et:

acl "trusted" {
        192.168.1.0/24;
        127.0.0.0/8;
};

options {
    directory "/var/named";
    pid-file "/run/named/named.pid";
    listen-on { trusted; };
    listen-on-v6 { any; };
    allow-query { trusted; };
    allow-transfer { none; };
    allow-update { none; };
    forwarders {
        8.8.4.4;
        8.8.8.8;
    };
    query-source address * port 53;
    version none;
    hostname none;
    server-id none;
};

logging {
    channel default_file {
        file "/var/log/named/default.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel general_file {
        file "/var/log/named/general.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel database_file {
        file "/var/log/named/database.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel security_file {
        file "/var/log/named/security.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
channel config_file {
        file "/var/log/named/config.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel resolver_file {
        file "/var/log/named/resolver.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel xfer-in_file {
        file "/var/log/named/xfer-in.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel xfer-out_file {
        file "/var/log/named/xfer-out.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel notify_file {
        file "/var/log/named/notify.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel client_file {
        file "/var/log/named/client.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel unmatched_file {
        file "/var/log/named/unmatched.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel queries_file {
        file "/var/log/named/queries.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel network_file {
        file "/var/log/named/network.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel update_file {
        file "/var/log/named/update.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel dispatch_file {
        file "/var/log/named/dispatch.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    channel dnssec_file {
        file "/var/log/named/dnssec.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
channel lame-servers_file {
        file "/var/log/named/lame-servers.log" versions 3 size 5m;
        severity dynamic;
        print-time yes;
    };
    category default { default_file; };
    category general { general_file; };
    category database { database_file; };
    category security { security_file; };
    category config { config_file; };
    category resolver { resolver_file; };
    category xfer-in { xfer-in_file; };
    category xfer-out { xfer-out_file; };
    category notify { notify_file; };
    category client { client_file; };
    category unmatched { unmatched_file; };
    category queries { queries_file; };
    category network { network_file; };
    category update { update_file; };
    category dispatch { dispatch_file; };
    category dnssec { dnssec_file; };
    category lame-servers { lame-servers_file; };
};

zone "ld.pvt" IN {
    type master;
    file "ld.pvt.zone";
};
$TTL 7200
@               1D IN SOA       ns1.ld.pvt. root.ld.pvt. (
                                        2007011622      ; Serial
                                        3H              ; Refresh
                                        15M             ; Retry
                                        1W              ; Expire - 1 week
                                        1D )            ; Minimum
                IN      NS      ns1.ld.pvt.
ns1.ld.pvt.     IN      A       192.168.1.10
*.ld.pvt.       IN      CNAME   ns1.ld.pvt.
redtail.ld.pvt. IN      A       192.168.1.99

Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Offline

Board footer

Powered by FluxBB