Joshua said, "when you did your "dig", did you do this locally on the same LAN or outside, because mine fails."
I did the dig from within the same LAN, but not on the same machine. It's odd, since t looks like packets are finding their way to the dns to get the info (according to tcpdump on the dns), but they never get it (according to the results of the ping command on the client). I am at a loss as to what I should be looking at next. One question. When I registered the dns with go-daddy.com I just gave it a name (mordor.kungfugamers.com) and told it the ip address. The only reason I gave it a name was because go-daddy insisted. Frankly, an IP was good enough for me. Should I be doing something with that name on the server itself? I mean, it's internal name isn't mordor.kungfugamers.com. If so, what do I do about the fact that I had to register it with 2 names (mordor.kungfugamers.com and shire.kungfugamers.com) because go-daddy demanded multiple authoritative dns's. -Tom Caudron -- [EMAIL PROTECTED] mailing list
