-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 19 November 2003 17:50, Tom Caudron wrote:
> Well, a month later and I'm back to working on this dns problem.
>
> I tried to follow Mike's advice (found below), but I ran in to a
> problem. When I emerged djbdns, it never created anything called
> dnscache. It only created dnscachex, tinydns, and axfrdns. And unlike
> every other reference I've seen/read about, including Mike's below, it
> was put in the /var directory, not the /etc directory. I doubt the
> directory change is an issue, and since I don't really care about acting
> as a proxy dns to my internal network, I'm not sure I need dnscache, but
> I could be wrong on both counts.
I don't believe there is actually any difference between dnscache and
dnscachex, really. It's just a naming convention.
The /var vs /etc thing, that's weird. But so long as the links into /service
are right, and the ...{tinydns,dnscache(x)}/env/ROOT are correct, it doesn't
matter.
If you are only serving your own DNS out to the world, you don't actually need
dnscache.
I've never had a need to do zone transfer with djbdns so can't help with
axfrdns.
> Anyway, it still won't work. :(
Is listening on the network properly?
'netstat -nlp'
> I've added the domain and its aliases to the system using tinydns's
> "add-host" and "add-alias". For simplicity's sake, let's say my IP is
> 1.2.3.4 and my domain is foobar.com. Here is the output I get when I
[snip]
> And that continues for a while, trying different permutations, like
> localhost.foobar.com or www.foobar.com.localdomain, etc....
try 'dig @127.0.0.1 www.foobar.com', or 'host www.foobar.com 127.0.0.1'
Replace 127.0.0.1 with the IP tiny is listening on.
> I've registered my machine/ip as a valid dns (and I get dns requests all
> the time, but the above mentioned udp error suggests to me that they
> aren't be fulfilled) and I've got apache set up to give me a domain back
> (it works on another hosted domain that uses an external authoritative
> dns server for discovery).
>
> Does anyone have a clue as to what could be the problem? Any help would
> be appreciated. :)
Not really :)
Dan isn't exactly forgiving with configuration errors, or helpful with
diagnosing.
- --
Mike Williams
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/u75YInuLMrk7bIwRAs6aAKCQidX0gNKWNWkzngHmbHfj+MbTBQCdGbT3
MZv282nxMl98sW7owoivobg=
=GzSv
-----END PGP SIGNATURE-----
--
[EMAIL PROTECTED] mailing list
