Hi,
I have installed djbdns on a red hat 8.0. Everything works fine for a day then it will stop answering queries. I run the command svstat /service/tinydns and it tells me that the service is still up. Any idea?
Thanks you.
Did you restart it? What did the log say?
My run file looks like so:
Code:
#!/bin/sh
exec 2>&1
exec envuidgid tinydns envdir ./env softlimit -d300000 /usr/local/bin/tinydns
How about yours?
Was this answer helpful ?
Yes No
Hi,
>Did you restart it?
Yes, I did restart yesterday.
>What did the log say?
I ran svstat /service/tinydns/log and it tells that it has been up 0
seconds.
My run look the same as yours.
#!/bin/sh
exec 2>&1
exec envuidgid tinydns envdir ./env softlimit -d300000 /usr/local/bin/tinydns
Thanks again.
Was this answer helpful ?
Yes No
>> I ran svstat /service/tinydns/log and it tells that it has been up 0 seconds.
I want to see what the log says, not what you think it's happening.
Was this answer helpful ?
Yes No
Hi,
I'm sorry. Here is my log file.
Thank you.
Was this answer helpful ?
Yes No
The log indicates that you have misconfigured your data file (zone records), nothing more than that and that can't cause tinydns to stop answering queries.
When you say it will stop answering queries:
1) What kind of queries exactly?
2) How do you know? What did you do exactly?
As far as the misconfiguration, it's merely a misconception to most people regarding to reverse DNS. 99% of the time you are not authoritative for your own reverse (122.67.166.219.in-addr.arpa). If tinydns stops responding to a reverse lookup of 219.166.67.122, that's normal, just because your tinydns is NOT authoritative for 219.166.67.122 IP.
Currently you have a lame server as well -> ns-kg021.ocn.ne.jp
Your MX should only be ns1.solarenet.com, not mail.solarent.com.
Post your data file so I can fix all possible misconfiguration for you.
Was this answer helpful ?
Yes No
Hi freebsd,
Here is my tinydns data.
Thank you.
Was this answer helpful ?
Yes No
Code:
Zsolarenet.com:ns1.solarenet.com:hostmaster.solarenet.com
&solarenet.com:219.166.67.122:ns1.solarenet.com
&solarenet.com::ns-kg021.ocn.ad.jp
@solarenet.com::ns1.solarenet.com.:0
+www.solarenet.com:219.166.67.122
+solarenet.com:219.166.67.122
Zcahier.net:ns1.solarenet.com:hostmaster.cahier.net
&cahier.net::ns1.solarenet.com
&cahier.net::ns-kg021.ocn.ad.jp
@cahier.net::ns1.solarenet.com.:0
+cahier.net:219.166.67.122
+www.cahier.net:219.166.67.122
Use
Z line, the
. line is somewhat useless to most setup. Anything you don't understand the changes I have made, just ask.
You should also see that you have a typo error in ns-kg021.ocn.
ad.jp as ns-kg021.ocn.
ne.jp (non-existence).
My two questions remain unanswered please response.
Was this answer helpful ?
Yes No
Hi freebsd,
>>1) What kind of queries exactly?
Actually i mean when i use ping command and it tells "Time out".
I'm very sorry for my terrible english.
>>You should also see that you have a typo error in ns-kg021.ocn.ad.jp as ns-kg021.ocn.ne.jp (non-existence).
I'm sorry.
When I go to work I'll fix it right away.
By the way, could you tell me what lame server mean?
Thank you so much!
Akira
Was this answer helpful ?
Yes No
>> Actually i mean when i use ping command and it tells "Time out".
ping is not a tool to debug DNS problem. Dropping incoming icmp packets at firewall level so people can't ping you, doesn't mean your DNS isn't working properly.
>> could you tell me what lame server mean?
The server is not authoritative for your domain. Say you blindly entered ns1.google.com as your slave nameserver. Of course, ns1.google.com is not authoritative for your domain, because they haven't been told to.
Was this answer helpful ?
Yes No
