[arm-allstar] Local DNS Server on Allstar R-Pi not answering 127.0.0.1

[Doug Crompton]

John,

 Not sure what is happening there but echolink seems to work fine elsewhere
and it does here without anything special. The 127.0.0.1 is defined as
localhost in the /etc/hosts file -

 cat /etc/hosts
#
# /etc/hosts: static lookup table for host names
#

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1    localhost.localdomain    localhost
::1        localhost.localdomain    localhost

and it is resolvable both ways -

nslookup localhost

Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    localhost
Address: 127.0.0.1

nslookup 127.0.0.1

Server:        127.0.0.1
Address:    127.0.0.1#53

1.0.0.127.in-addr.arpa    name = localhost.



*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



On Sun, Jul 9, 2017 at 2:46 PM, "John Huggins via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> All,
>
> I have made solid progress setting up the latest Allstar boot image for a
> R-Pi 2. The unit responds to Echolink connection requests, but the
> /var/log/asterisk/messages file throws this during the connect attempt...
>
>
>
>
> *[Jul  9 14:25:34] ERROR[407] chan_echolink.c: Cannot find DB entry for IP
> addr 192.168.1.1[Jul  9 14:25:34] ERROR[407] chan_echolink.c: Cannot find
> DB entry for IP addr 192.168.1.1[Jul  9 14:25:40] ERROR[407]
> chan_echolink.c: Cannot find DB entry for IP addr 192.168.1.1[Jul  9
> 14:25:40] ERROR[407] chan_echolink.c: Cannot find DB entry for IP addr
> 192.168.1.1*
>
> ...with the Echolink program eventually saying "*Cannot Connect to 'call' -
> UN-AUTHORIZED*."
>
> I assume the allstar program suite seeks to perform a reverse lookup on my
> local gateway.
>
> I see the boot image sets up the usual BIND server for use as a DNS lookup
> caching server and is setup to also answer reverse lookups for 127.0.0.1 ->
> localhost. as well - pretty routine stuff for a caching BIND instance.
> Resolve.conf is set to point to 127.0.0.1 for lookups. This works fine for
> external hostname resolving, but BIND won't answer for the 127.0.0.1
> lookup.  I later added a zone for 192.168.1.x (routine stuff) to this DNS,
> but it also doesn't answer requests for local IP address lookups.
>
> I do know the local named instance is using this file because I can
> certainly break it with a typo in /etc/named.conf.
>
> Can anyone else successfully resolve 127.0.0.1 on their local copy of the
> Allstar environment?
>
> Taking it back one more step, does echolink really need to know the
> hostname of my gateway?
>
> Thanks for any enlightenment.
>
> 73
> John, kx4o
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>