Kent Busbee wrote:
> See response WithIn; Dan McAllister wrote:
>> I'm a little johnny-come-lately on this discussion, but here's my
>> 2-cents worth:
>>
>> First, let's be clear on something -- with the exception of your own
>> LAN, you do not control, nor does your server answer for a reverse-DNS
>> lookup. DJBDNS, Bind, or even windoze DNS servers answer for NAME
>> lookups for your configured domains, but the REVERSE DNS lookup will be
>> resolved by your ISP. (Amazing how many admins get this wrong!) Based on
>> your question, you may or may not have already known that, but I wanted
>> to get it out of the way anyways. (Again, your LAN is the exception).
>>
> Ok here we are obviously talking about my LAN
>
>> Now typically, djbdns is setup as a "caching" nameserver -- which means
>> it doesn't resolve LAN names or addresses -- just Internet ones. So that
>> is probably where your first problem is. To learn how to install "local"
>> domains, go to http://cr.yp.to/djbdns/run-server-bind.html This is
>> where Daniel (Bernstein, not me) explains how to import and/or create
>> the database for his djbdns system. (Personally, I use bind).
>>
>
> Ouch --- my head hurts for reading the above link. I have messed with
> bind a little and actually think it is a little less involved. Maybe
> not...
> <personal grip> You think they could come up with something a little less
> complicated like a list of names and their addresses, and then another
> file for the reverse... but, I guess the days of hosts file and such are
> over.</personal grip>
>
>> Finally, remember that the REVERSE DNS zone has to be NAMED something
>> like (using your apparent LAN address below): "1.168.192.in-addr.arpa"
>> and should contain an SOA and PTR records only (certain optional records
>> -- like LOC are OK, but there is no need for the likes of NS or MX
>> records in a reverse-DNS zone file). This seems counter-intuitive, but
>> has to do with the database hierarchy that the Internet DNS system uses.
>> (Basically, it is your network address with the bytes reversed -- so,
>> your network address being 192.168.1[.0] (assuming a 24-bit netmask of
>> 255.255.255.0), you reverse that to 1.168.192. Then, tell the system
>> that this is a REVERSE zone by ending the name with "in-addr.arpa").
>>
>> I hope this helps.... someone!
>
> Yeah, thanks for helping me.... I just needed to pound on it long enough.
>
> SOLUTION (for now)
>
> I reversed the order of 127.0.0.1 and 192.168.1.5 in my resolve.conf file.
> It seems to be working for now. Somehow I knew it could not have been
> that complicated.
>
> [EMAIL PROTECTED] etc]# cat /etc/resolv.conf
> search ncs-ad.northlakechristian.org
> nameserver 192.168.1.5
> nameserver 127.0.0.1
> nameserver 192.168.1.254
> nameserver 207.29.223.56
> nameserver 207.29.223.58
>
>
> THANKS for all the help.
>
That appears to indicate there's a problem of some sort with the caching
nameserver on your toaster (aka localhost).
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
