Simple DNS Configuration

Mikhail Goriachev mikhailg at webanoide.org
Tue Jul 25 06:46:42 UTC 2006


David Stanford wrote:
> On 7/25/06, Mikhail Goriachev <mikhailg at webanoide.org> wrote:
>> David Stanford wrote:
>>>> I've tried everyone's suggestions to no avail. Here's my actual
>>> configuration:
>>>
>>> [root at chadwick ~]# /etc/rc.d/named stop
>>> Stopping named.
>>> [root at chadwick ~]# tail -12 /etc/namedb/named.conf
>>
>> I can't stop mine and then start it again (running in chrooted mode). I
>> do:
>>
>> # make rndc reload
> 
> 
> Isn't named's default behaviour to run chrooted? It appears so whn looking
> at the rc script.


Yep, it is. I got burnt a few times using stop and start in the past.
That is why I only use 'rndc reload'.


> Also, when something goes wrong, named won't reload but logs a complaint
>> into /var/log/messages. So it is a good idea to check logs every time a
>> change is made.
>>
>>
>>> zone "daemonbox.net" {
>>>         type master;
>>>         file "master/daemonbox.net";
>>> };
>>>
>>> /*
>>> zone "140.246.66.in-addr.arpa" {
>>>         type master;
>>>         file "master/140.246.66.in-addr.arpa";
>>> };
>>> */
>>> [root at chadwick ~]# cat /etc/namedb/master/daemonbox.net
>>> $TTL 3600        ; 1 hour
>>> daemonbox.net.  IN      SOA     chadwick.daemonbox.net.
>>> dstanford.daemonbox.net. (
>>>                                 2006072400      ; Serial
>>                                   ^^^^^^^^^^
>>                                   ^^^^^^^^^^
>> Make sure your serial increments with every change you make.
> 
> 
> I've been ignoring that to save time while troubleshooting as (from my
> understanding) it  is only used by  other name servers so they know to
> update their information:
> 
> "The serial number identifies this version of the zone configuration. Remote
> name servers
> first retreive the SOA record and check if the serial number has incremented
> before
> deciding whether to access the rest of the zone, which could be large. Make
> sure you
> increment this field every time you edit the file. If you don't, your
> updates will not
> propagate to other name servers."   -The Complete FreeBSD, Greg Lehey


Good point. I also got burnt with this one a few times in the past...
now incrementing is my habit. I guess its use depends on the weather.


>>                                 1d              ; Refresh
>>>                                 2h              ; Retry
>>>                                 100d            ; Expire
>>>                                 1h )            ; Minimum TTL
>>>
>>>
>>> ; DNS Servers
>>> @               IN      NS      chadwick.daemonbox.net.
>>> @               IN      NS      ns1.nac.net.
>>> @               IN      NS      ns2.nac.net.
>>
>> Remove/comment those nac.net servers just in case (just for now while
>> testing). Get yours cranking first.
> 
> 
> Good point.
> 
>> ; MX Records
>>>                 IN      MX 10   mail.daemonbox.net.
>>>
>>> ; Machine Names
>>> localhost       IN      A       127.0.0.1
>>> chadwick       IN      A       66.246.140.170
>>> mail              IN      A       66.246.246.58
>>> www             IN      A       66.246.140.170
>>> @                IN      A       66.246.140.170
>>>
>>> ; Aliases
>>> www             IN      CNAME   @
>>
>> I personally wouldn't use that line. Previous 2 lines are sufficient.
> 
> 
> Yea, I feel I may just use the A records as the additional query issue you
> mentioned previously leaves me thinking it's the better configuration...it
> still bothers me I can't figure it out though. :-/


Not sure what you mean.


>> [root at chadwick ~]# /etc/rc.d/named start
>>> Starting named.
>>
>> Check your logs.
> 
> 
> I've been checking /var/log/messages but see nothing after recieving that
> error. Are all named logs placed here by default?


This is the only place where I look. As far as I'm concerned, if a
reload was unsuccessful, then you'll get something in there. Otherwise
nothing gets logged.


>> [root at chadwick ~]# host -t a daemonbox.net localhost
>>> Using domain server:
>>> Name: localhost
>>> Address: 127.0.0.1#53
>>> Aliases:
>>>
>>> Host daemonbox.net not found: 2(SERVFAIL)
>>>
>>>
>>> Does anyone see anything wrong with this? Thanks for all your help!
>>
>> Can you resolve other domains (e.g.: freebsd.org)? Can't think of
>> anything else right now.
> 
> 
> Yes, as I noted, when  I remove the CNAME entry everything works fine. Very
> strange...


Not sure about that either. I guess you shouldn't use it then. Anyway,
at least your domain is responding now:


$ host -t a daemonbox.net chadwick.daemonbox.net
Using domain server:
Name: chadwick.daemonbox.net
Address: 66.246.140.170#53
Aliases:

daemonbox.net has address 66.246.140.170

$ host -t a www.daemonbox.net chadwick.daemonbox.net
Using domain server:
Name: chadwick.daemonbox.net
Address: 66.246.140.170#53
Aliases:

www.daemonbox.net has address 66.246.140.170


http://www.dnsreport.com/tools/dnsreport.ch?domain=daemonbox.net


www.dnsreport.com is a great tool for all your DNS needs.




Cheers,
Mikhail.


-- 
Mikhail Goriachev
Webanoide

Telephone: +61 (0)3 62252501
Mobile Phone: +61 (0)4 38255158
E-Mail: mikhailg at webanoide.org
Web: http://www.webanoide.org

PGP Key ID: 0x4E148A3B
PGP Key Fingerprint: D96B 7C14 79A5 8824 B99D 9562 F50E 2F5D 4E14 8A3B


More information about the freebsd-questions mailing list