Re: Need Help W/ DNS Server
I tried everything and, considering my head felt like mush and I couldn't
think, I probably tried things I never would have done normally. A few
notes:
1) Bind 9 seems to be bad news on Linux. Bind worked fine with the same files
Bind 9 wouldn't use.
2) I had problems with host not reporting the info (and saying there were no
such hosts). Once I used ssh the first time, host worked fine from then on.
3) I did not need a key hash to get it to work. I may add it for security
later. Right now my head feels so grungy I'm not thinking clearly and it
takes me forever to understand a man page, so it'll have to wait until I can
think better.
Thank you, all for your help.
Hal
On Wednesday 23 February 2005 02:18 pm, Hal Vaughan wrote:
> I REALLY need some help with setting up a DNS server on Mepis. I've been
> working hard on this since Monday, I'm short on sleep, so I really feel
> like I'm not thinking clearly, but I need to get this (and NIS, which is
> fubar, too) working as quickly as possible, so I'd really appreciate help
> with this (since nobody on the Mepis IRC channels or forums seems to know
> what to do). I've tried other mailing lists, but I'm not getting any
> suggestions. Please don't hesitate to tell me if I'm missing the obvious,
> since, at this point, my brain feels like it's mud.
>
> I've been using the Debian reference manuals online, but even when I follow
> their instructions, it doesn't seem to be enough. I tried using Webmin to
> set this up, figuring that would ensure the config files were in proper
> shape, but it didn't help.
>
> I think there are several issues. The first is that everytime I try to
> start the dns with /etc/init.d/bind9, I get this:
>
> Stopping domain name service: namedrndc: connect failed: connection refused
> .
> Starting domain name service: namednamed: capset failed: Operation not
> permitted
> named: capset failed: Operation not permitted
> .
>
> I found a reference that capset is a module I can install in the kernel
> (Mepis is using 2.6.7). I'd rather not have to recompile the kernel, but I
> don't see the source on the install (I can't remember the directory, but I
> thought it was in /var/libs somewhere), and other than just running insmod,
> I can't remember how to get capset installed. (Note: I have not always
> been getting the error about capset.)
>
> I used nslint and it thinks everything is okay. I run dnswalk, and I get
> the following:
>
> Checking thresh.loc.
> BAD: SOA record not found for thresh.loc.
> BAD: thresh.loc. has NO authoritative nameservers!
> BAD: All zone transfer attempts of thresh.loc. failed!
> 0 failures, 0 warnings, 3 errors.
>
> While all the Debian docs say the config is in /etc/named.conf, I've
> found /etc/init.d/bind9 references /etc/bind/named.conf, so I'm keeping
> both files the same. I have the zone files stored in /var/named. Below, I
> have listed the files. (I've excluded named.ca, which I downloaded
> directly from internic.net, which was named.root on their ftp.)
>
> Any help -- especially any help soon is GREATLY appreciated!
>
> Hal
> ----------------------------------------Files:-----------------------------
>
> /etc/named.conf:
> --------------------------------------------
> options {
> pid-file "/var/run/named/named.pid";
> directory "/var/named";
> /*
> * If there is a firewall between you and nameservers you want
> * to talk to, you might need to uncomment the query-source
> * directive below. Previous versions of BIND always asked
> * questions using port 53, but BIND 8.1 uses an unprivileged
> * port by default.
> */
> // query-source address * port 53;
> };
>
> //
> // a caching only nameserver config
> //
> zone "." {
> type hint;
> file "named.ca";
> };
>
> zone "localhost" {
> type master;
> file "named.localhost";
> };
>
> zone "0.0.127" {
> type master;
> file "named.127.0.0";
> };
>
> zone "thresh.loc" {
> type master;
> file "named.thresh.loc";
> };
>
> zone "7.16.172" {
> type master;
> file "named.172.16.7";
> };
>
> --------------------------------------------
>
> /var/named/named.thresh.loc:
> --------------------------------------------
> $TTL 86400
> @ IN SOA thresh.loc. root.thresh.loc. (
> 2005022203 ; Serial
> 28800 ; Refresh
> 14400 ; Retry
> 3600000 ; Expire
> 86400 ) ; Minimum
> IN NS ozma.thresh.loc.
> IN MX 10 ozma
>
> ozma IN A 172.16.7.2
> tiktok IN A 172.16.7.1
> tinman IN A 172.16.7.3
> scarecrow IN A 172.16.7.4
> thewizard IN A 172.16.7.11
> toto IN A 172.16.7.12
> scraps IN A 172.16.7.13
> mail IN CNAME ozma
> smtp IN CNAME ozma
> pop IN CNAME ozma
> imap IN CNAME ozma
> print IN CNAME ozma
> fax IN CNAME ozma
> server IN CNAME ozma
> www IN CNAME tinman
> threshnet IN CNAME scarecrow
> ldnet IN CNAME scarecrow
>
> --------------------------------------------
>
> /var/named/named.7.16.172:
> --------------------------------------------
> $TTL 86400
> @ IN SOA thresh.loc. root.thresh.loc. (
> 2005022203 ; Serial
> 28800 ; Refresh
> 14400 ; Retry
> 3600000 ; Expire
> 86400 ) ; Minimum
> IN NS ozma.thresh.loc.
>
> 1 IN PTR tiktok.thresh.loc.
> 2 IN PTR ozma.thresh.loc.
> 3 IN PTR tinman.thresh.loc.
> 4 IN PTR scarecrow.thresh.loc.
> 11 IN PTR thewizard.thresh.loc.
> 12 IN PTR toto.thresh.loc.
> 13 IN PTR scraps.thresh.loc.
>
> --------------------------------------------
>
> /var/named/named.localhost:
> --------------------------------------------
> $TTL 86400
> @ IN SOA localhost. root.localhost. (
> 2005022203 ; Serial
> 28800 ; Refresh
> 14400 ; Retry
> 3600000 ; Expire
> 86400 ) ; Minimum
> IN NS localhost.
>
> localhost. IN A 127.0.0.1
>
> --------------------------------------------
>
> /var/named/named.0.0.127:
> --------------------------------------------
> $TTL 86400
> @ IN SOA localhost. root.localhost. (
> 2005022203 ; Serial
> 28800 ; Refresh
> 14400 ; Retry
> 3600000 ; Expire
> 86400 ) ; Minimum
> IN NS localhost.
>
> 1 IN PTR localhost.
Reply to: