-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 20 November 2003 01:10, Tom Caudron wrote:
> Eric and Mike both requested this output: > > netstat -nlp | grep udp | grep 53 > > udp 0 0 68.15.153.133:53 0.0.0.0:* 936/dnscache > udp 0 0 68.15.153.133:53 0.0.0.0:* 932/tinydns > > Three things of note here. > > First, unlike the example Eric gave, I didn't need to do a ps on the pid. > It was in the output. That's the 'p' doing it's job :) > Second, I'm no Doctor of Portology, but I'm guessing two services listening > on the same port is a bad thing? Yus, bad thing. > Third, it says dnscache is listening. Well, I can't find dnscache > anywhere. All I seem to have is dnscachex, which perhaps just calls itself > plain ol' "dnscache" in the pid? dnscachex is just dnscache with a slightly different configuration (it only knows about specific domains) > Some more output requested by Eric and Mike: > If I add the @ sign to the command as you have it: You need the @ sign, it tells dig to go at that server (get the records from it) > > dig @1.2.3.4 www.foobar.com a > > ; <<>> DiG 9.2.2rc1 <<>> @1.2.3.4 www.foobar.com a > ;; global options: printcmd > ;; connection timed out; no servers could be reached > > > host www.foobar.com 1.2.3.4 > > ;; connection timed out; no servers could be reached This would be because you have both dnscache and tinydns listening on the same port. Stop dnscache, add your external IP to /var/tinydns/env/IP, and restart tiny. Then see how things go. > Mike said, "Dan isn't exactly forgiving with configuration errors, or > helpful with diagnosing." > > Yeah, I get that. But the app is great from what I hear...and I love > QMail, so I can't say much bad about the guy. :-) Steep learning curve, but an immense sense satisfaction when you are there :) - -- Mike Williams -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/vJ9aInuLMrk7bIwRAi0HAJ4xxpo7uMiD1sGYXSiwR28th3lWcgCcCWVf QZBnsL9xKfPX7EpEI6mGnko= =k04O -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
