"Mike Kercher" <mike at vesol.com> wrote in message news:6115482898C59848B35DB9D491C9A28E08BFA1 at srv1.home.middlefinger.net... > > Thanks for the pointer. Indeed, I was missing the trailing > . after my > > FQDN in my revers file. I have updated my reverse files, > and nslookup > > is resolving better, but still not further ahead. > > > > My reverse file: 3.168.192.in-addr.arpa now contains the > following line: > > 103 IN PTR eric.test.com. > > > > > > If I try nslookups now, my results are as follows: > > > > # nslookup 192.168.3.103 > > Server: 192.168.1.67 > > Address: 192.168.1.67#53 > > > > 103.103.168.192.in-addr.arpa name = eric.test.com. > > > > # nslookup eric.test.com > > Server: 192.168.1.67 > > Address: 192.168.1.67#53 > > > > Name: eric.test.com > > Address: 192.168.3.103 > > > > > > So from that, it seems as though the DNS / rDNS are properly > > configured, does it not? Similarly, I have both the forward and > > reverse domain name on the DNS server as the nslookups > show. However, > > I still get the same error > > msg: > > Jan 14 17:46:50 apollo atftpd[15905]: Connection refused from > > 192.168.103.103 > AAA > Correct? -----||| >Additionally, the connection was refused from 192.168.103.103 (NOT >192.168.3.103) Sorry - in my haste (and frustration), I copied the wrong line from my log file. It actually reads: Jan 14 17:49:50 apollo atftpd[15905]: Connection refused from 192.168.3.103