How to make DNS master server?? Problems!!!

billymayday · 09-22-2008, 07:19 PM

Also - check bind is listening

netstat -nalp | grep :953

kayasaman · 09-22-2008, 07:24 PM

Ok I created the record:

Code:

ns1.optiplex-networks.com      IN      A     192.168.1.51

within the forward zone file.

Now dig gives this result from server:

Code:

; <<>> DiG 9.3.4-P1.1 <<>> @localhost optiplex-networks.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3826
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;optiplex-networks.com.         IN      A

;; ANSWER SECTION:
optiplex-networks.com.  764     IN      A       81.178.2.118

;; AUTHORITY SECTION:
optiplex-networks.com.  4139    IN      NS      ns1.active-dns.com.
optiplex-networks.com.  4139    IN      NS      ns2.active-dns.com.

;; Query time: 92 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Sep 23 03:22:21 2008
;; MSG SIZE  rcvd: 102

kayasaman · 09-22-2008, 07:25 PM

Output of Netstat:

Code:

tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN     32106/named

billymayday · 09-22-2008, 07:34 PM

Just to rule out other issues, put

Code:

zone "optiplex-networks.com" {
       type master;
       file "/var/named/optiplex-networks.db";
};

zone "1.168.192.IN-ADDR.ARPA" {
       type master;
       file "/var/named/192.168.1.rev";
};

in your main bind config and comment out the include statement that's there. I get the feeling it isn't finding you master statement.

kayasaman · 09-22-2008, 07:39 PM

Ok this is interesting, these are records from my Cisco routers DNS implementation:

Code:

ip host notinoc2200 ns ns1.optiplex-networks.com
ip host notinoc2200 ns ns2.optiplex-networks.com

However in my zone files there are no ns styled records? I based them on config from HowtoForge when I originally designed the DNS server.

shouldn't there be something a bit more then

Code:

@       IN      NS      ns1.optiplex-networks.com.

like say:

Code:

optiplex-networks.com     IN      NS    ns1.optiplex-networks.com

which means that the domain would be in NS record rather then just pointing the domain name to an IP address.

kayasaman · 09-22-2008, 07:44 PM

Ok this is interesting, these are records from my Cisco routers DNS implementation:

Code:

ip host notinoc2200 ns ns1.optiplex-networks.com
ip host notinoc2200 ns ns2.optiplex-networks.com

However in my zone files there are no ns styled records? I based them on config from HowtoForge when I originally designed the DNS server.

shouldn't there be something a bit more then

Code:

@       IN      NS      ns1.optiplex-networks.com.

like say:

Code:

optiplex-networks.com     IN      NS    ns1.optiplex-networks.com

which means that the domain would be in NS record rather then just pointing the domain name to an IP address.

billymayday · 09-22-2008, 07:44 PM

Here's a mocked-up snippet from one of my zone files

Code:

$ORIGIN .
$TTL 604800     ; 1 week
example.com         IN SOA  ns1.example.com. hostmaster.example.com. (
                                2008090901 ; serial
                                86400      ; refresh (1 day)
                                7200       ; retry (2 hours)
                                1209600    ; expire (2 weeks)
                                604800     ; minimum (1 week)
                                )
                        NS      192.168.1.1.example.com.
                        A       192.168.1.1
                        MX      5 mail.example.com.
$ORIGIN example.com.
server                  A       192.168.1.1
ns1                     CNAME   server

(Note the lack of @'s is because I specifically declare example.com)

billymayday · 09-22-2008, 07:46 PM

I always find this sit egood

http://www.linuxhomenetworking.com/w...ve_DNS_Servers

kayasaman · 09-22-2008, 09:09 PM

Hi sorry I totally lost DNS altogether???

Have no idea what happened but had to re-add my ISP's DNS servers into resolv.conf and the zone files. Just been trying since last post to get back online.

My server was running backups at the time so that may explain why but had to even reboot the router as everything went down!

kayasaman · 09-22-2008, 09:14 PM

I meant to send you this before everything collapsed:

This is interesting, these are records from my Cisco routers DNS
implementation:

Code:

ip host notinoc2200 ns ns1.optiplex-networks.com
ip host notinoc2200 ns ns2.optiplex-networks.com

However in my zone files there are no ns styled records? I based them on
config from HowtoForge when I originally designed the DNS server.

shouldn't there be something a bit more then

Code:

@       IN      NS      ns1.optiplex-networks.com.

like say:

Code:

optiplex-networks.com     IN      NS    ns1.optiplex-networks.com

which means that the domain would be in NS record rather then just
pointing the domain name to an IP address.

kayasaman · 09-22-2008, 09:48 PM

Ok well the site says to issue the command:

Code:

host www.mydomain.com ns1.mydomain.com

of which I did and it gives me this response?

Code:

Using domain server:
Name: ns1.optiplex-networks.com
Address: 192.168.1.51#53
Aliases:

www.optiplex-networks.com has address 81.178.2.118

I also tried creating a zone file in the named.conf file itself and removing the entries within named.conf.local however bind failed to start totally then??

kayasaman · 09-22-2008, 09:55 PM

However at this point the system still isn't working

I don't have this statement un-commented in my named.conf:

Code:

include "/etc/named.rfc1912.zones";

will this help or make the server authoritive??

I think Mr C. was the person who knew most about DNS out of us!!!

I'm just hoping for the system not to go down again as it was a nightmare to fix.

billymayday · 09-22-2008, 11:15 PM

I think I've worked out your problem. This is sort of where I was going before.

The standard Debian named.conf has 2 include statements

Code:

include "/etc/bind/named.conf.options";

in the position you have it in yours, and the last line is

Code:

include "/etc/bind/named.conf.local";

I had assumed that what you'd said on the first page was a typo when you referred to LOCAL, but it actually looks to me like in following your howto, you've deleted that include.

Hence, bind is never seeing your reference to the zone file for your domain.

Add back the include (I've included the basic named.conf below for your reference). You will then need to follow through on any errors that come up. But they should be easy to fix.

Final point - I have absolutely no doubt that Mr. C knows way more about DNS than I ever want to.

Code:

// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
   type hint;
   file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
   type master;
   file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
   type master;
   file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
   type master;
   file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
   type master;
   file "/etc/bind/db.255";
};

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
//  Because many of our users are uncomfortable receiving undelegated answers
//  from root or top level domains, other than a few for whom that behaviour
//  has been trusted and expected for quite some length of time, we have now
//  introduced the "root-delegations-only" feature which applies delegation-only
//  logic to all top level domains, and to the root domain.  An exception list
//  should be specified, including "MUSEUM" and "DE", and any other top level
//  domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

include "/etc/bind/named.conf.local";

kayasaman · 09-22-2008, 11:33 PM

Quote:

Final point - I have absolutely no doubt that Mr. C knows way more about DNS than I ever want to.

Sorry if you miss-understood I didn't mean any offence by that jsut one of those statements of desperation like "God help me" I guess.

As I said before I really apprieciate your help and since you know a hell of a lot more then I do I really respect and admire you for it

since it's something I'm trying to achieve too through studies and my own research (my network) adn other stuff!

Now you say to add this line:

Code:

include "/etc/bind/named.conf.local";

which I did and again bind failed to start?? I couldn't see any verbose output other then the term "Failed".

Have you got any suggestions??

billymayday · 09-22-2008, 11:40 PM

Absolutely no offense was taken. The guy really knows his stuff and I have no issue with that, and he's also very good at helping out.

Now, hopefully you log the same place my Debian does, so try

tail /car/log/syslog (if you need more lines, try tail -20 or similar instead)

This should tell you where things are going wrong (but do it just after a restart attempt).

Edit - actually I'm not so much saying to add that line, more that it should never have been taken out.