The Shed is going Social! Join us on FaceBook and Twitter and chime in on the conversation.
|
 |
|
Dev Shed Forums
> System Administration
> DNS
|
tinydns runs for a day then stops answering queries
Discuss tinydns runs for a day then stops answering queries in the DNS forum on Dev Shed. tinydns runs for a day then stops answering queries DNS forum discussing issues, servers, and configurations. The Domain Name System (DNS) is what the Internet uses to translate website names into IP addresses.
|
|
 |
|
|
|
|

Dev Shed Forums Sponsor:
|
|
|

February 24th, 2003, 12:04 AM
|
|
Junior Member
|
|
Join Date: Oct 2001
Posts: 20
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
tinydns runs for a day then stops answering queries
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.
|

February 24th, 2003, 02:18 AM
|
|
Contributing User
|
|
Join Date: Jan 2001
Posts: 5
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
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?
|

February 24th, 2003, 05:50 AM
|
|
Junior Member
|
|
Join Date: Oct 2001
Posts: 20
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
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.
|

February 24th, 2003, 12:40 PM
|
|
Contributing User
|
|
Join Date: Jan 2001
Posts: 5
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
>> 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.
|

February 24th, 2003, 06:13 PM
|
|
Junior Member
|
|
Join Date: Oct 2001
Posts: 20
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
Hi,
I'm sorry. Here is my log file.
Thank you.
|

February 24th, 2003, 08:03 PM
|
|
Contributing User
|
|
Join Date: Jan 2001
Posts: 5
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
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.
|

February 24th, 2003, 08:22 PM
|
|
Junior Member
|
|
Join Date: Oct 2001
Posts: 20
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
Hi freebsd,
Here is my tinydns data.
Thank you.
|

February 24th, 2003, 08:40 PM
|
|
Contributing User
|
|
Join Date: Jan 2001
Posts: 5
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
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.
|

February 24th, 2003, 09:01 PM
|
|
Junior Member
|
|
Join Date: Oct 2001
Posts: 20
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
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
|

February 24th, 2003, 09:16 PM
|
|
Contributing User
|
|
Join Date: Jan 2001
Posts: 5
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
>> 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.
|

February 24th, 2003, 09:46 PM
|
|
Junior Member
|
|
Join Date: Oct 2001
Posts: 20
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
Thank you.
|

February 24th, 2003, 10:57 PM
|
|
Junior Member
|
|
Join Date: Oct 2001
Posts: 20
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
One more question please.
Hi freebsd,
Should I put the secondary DNS ip in resolv.conf?
Thank you.
Akira
|

February 25th, 2003, 04:47 AM
|
|
Contributing User
|
|
Join Date: Jan 2001
Posts: 5
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
>> Should I put the secondary DNS ip in resolv.conf?
tinydns is to provide answers to DNS queries requested from others. All the answers are static and come from a flat db file at /service/tinydns/root/data.cdb. It answers what it knows about in the zone records (known), nothing more.
dnscache is to ask tinydns or other content DNS nameservers for answer and caches the answer accordingly. There's no data.cdb to hold zone records, whatsoever.
What you put in resolv.conf is the IP of dnscache, not tinydns. Just because tinydns is to provider answer, whereas dnscache is to request for the answer. They are totally different.
BTW, they both listen to UDP 53, so you can't bind both of them to the same IP.
|
Developer Shed Advertisers and Affiliates
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Rate This Thread |
Linear Mode
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|