[ale] bind 9.3.3 on Centos 5
Randy Ramsdell
rramsdell at livedatagroup.com
Tue Jun 24 14:17:56 EDT 2008
Jerry Yu wrote:
> on CentOS 5 (RHEL 5), you can use 'system-config-bind-gui', a nice
> GUI, to configure it from scratch too.
>
This a server without X.
> On Tue, Jun 24, 2008 at 11:56 AM, Jerry Yu <jjj863 at gmail.com
> <mailto:jjj863 at gmail.com>> wrote:
>
> the last section in named.conf, I believe you have extra '.zone'
> suffix for the zone declaration, thus don't really have a section
> for 'dailyezinefun.com <http://dailyezinefun.com>' itself.
>
> Should have been something like this:
> zone "dailyezinefun.com <http://dailyezinefun.com>" IN {
>
> type master;
> file "zone/dailyezinefun.com.zone";
> };
>
Holy crap you are correct. After 5 revisions of the named.conf and the
zone file, I completely missed that. Thanks for noticing this.
> Also, modern distros have named chrooted by default, so your zone
> file may need to under /var/named/chroot/var/named/zone
>
>
Yes this was and soon to be chroot'ed. I was simplifying the config
until everything worked. Since you found my typo, I will put this back
in jail, add internal/external views and tweek the conf file.
>
>
> On Tue, Jun 24, 2008 at 10:00 AM, Randy Ramsdell
> <rramsdell at livedatagroup.com <mailto:rramsdell at livedatagroup.com>>
> wrote:
>
> Hi,
>
> This is the first time I have had to set up named from scratch
> starting
> with a new domain and I don't know the ins and outs of this
> process.
>
> We registered a domain. ( dailyezinefun.com
> <http://dailyezinefun.com> ) a couple of days ago and I
> set the domain to point to our nameserver. I have tried so many
> configurations but nothing seems to work and I now have the
> most basic
> setup for ease of understanding.
>
> So.
>
> ns1.dailyezinefun.com <http://ns1.dailyezinefun.com> ==
> 206.212.244.202 <http://206.212.244.202> --- resolves : no
> other hosts
> do however.
>
> named.conf - simplified for testing
>
> options
> {
> allow-query { any; };
> recursion yes;
> allow-recursion {
> 127.0.0.1 <http://127.0.0.1>;
> 206.212.244.202 <http://206.212.244.202>;
> };
> listen-on {
> 127.0.0.1 <http://127.0.0.1>;
> 206.212.244.202 <http://206.212.244.202>;
> };
> };
> logging
> {
> channel default_debug {
> file "data/named.run";
> severity dynamic;
> };
> channel named_queries {
> file "data/named.queries" versions 5 size 20M;
> severity debug;
> print-time yes;
> };
> };
> zone "." {
> type hint;
> file "named.root";
> };
> zone "dailyezinefun.com.zone" {
> type master;
> file "zone/dailyezinefun.com.zone";
> };
>
> ZONE FILE: "/var/named/zone/dailyezinefun.com.zone" -- it has gone
> through many iterations but this is the latest which shows no
> errors
> when starting named.
>
> $TTL 1D
> @ IN SOA dailyezinefun.com
> <http://dailyezinefun.com>. admin.dailyezinefun.com
> <http://admin.dailyezinefun.com>. (
>
> 2007020400 ; Serial
> 10800 ; Refresh after
> 3 hours
> 3600 ; Retry after 1
> hour
> 604800 ; Expire after
> 1 week
> 86400 ) ; Minimum TTL
> of 1 day
>
> NS dailyezinefun.com
> <http://dailyezinefun.com>.
>
> NS ns1.dailyezinefun.com
> <http://ns1.dailyezinefun.com>.
> MX 1 mx202.dailyezinefun.com
> <http://mx202.dailyezinefun.com>.
> TXT "Dailyezinefun.com: The real deal"
>
> localhost A 127.0.0.1 <http://127.0.0.1>
> ns1 A 206.212.244.202
> <http://206.212.244.202>
> mx202 A 206.212.244.202
> <http://206.212.244.202>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org <mailto:Ale at ale.org>
> http://mail.ale.org/mailman/listinfo/ale
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>
Holy crap you are correct. After 5 revisions of the named.conf and the
zone file, I completely missed that. Thanks for noticing this.
More information about the Ale
mailing list