Hi Shamus,
After more investigating, there is a simple, more obvious solution.
If you delete the default "192.168.101.1" entry for the 1st LAN Interface ...
IPv4: , { Save Settings }, then Restart DNS & DHCP, your local hostname will be
obtained from your upstream DNS server, as you desire for your single interface
configuration.
For the record, for a Single Interface (only External Interface: defined)
configuration:
1) In the Network tab, make the Hostname: and Domain: match that of the
upstream DNS server.
2) Uncheck the "Local Domain" box.
3) Make sure no IPv4 (or IPv6/nn) addresses are defined in any of the "Internal
Interfaces:" section fields.
Hope that is more clear. Let me know if that does not solve it for you.
Lonnie
On Jun 20, 2012, at 8:53 PM, Lonnie Abelbeck wrote:
> Shamus,
>
> I understand. If your box is named "pbx", then asterisk would resolve pbx to
> 192.168.101.1, which is not what you want.
>
> I'm assuming your Network -> Domain: ... __ Local Domain is not-checked to
> use the upstream DNS server, the Domain: would be your ASUS router's domain.
> Even so, "pbx" will still resolve to what is defined in IPv4 for the 1st
> Interface since /etc/hosts has priority. Not what you want.
>
> It may seem like a hack, but in the Network tab, defining the 1st LAN
> Interface - IPv4: to "192.168.2.4" should solve your issue, since the
> interface is "none" the INTIP value is basically ignored everywhere else.
>
> We could consider not defining the INTIP HOSTNAME /etc/hosts entry if no
> internal interfaces are defined, Hmmm this has been this way since the very
> beginning of AstLinux, that will take some thinking. Funny this has not come
> up before.
>
> Lonnie
>
>
> On Jun 20, 2012, at 7:31 PM, Shamus Rask wrote:
>
>> Lonnie,
>>
>> After poking through the different tabs, I see the 192.168.101.1 is taken
>> from Network --> 1st LAN interface, a section I have not touched.
>>
>> My current set-up uses a single Ethernet port that is statically assigned
>> 192.168.2.4. I'm using a single, flat subnet 192.168.2.x for all of my
>> devices, both VoIP and non-VoIP related. The LAN is sitting behind an ASUS
>> router flashed with Tomato; I've port forwarded 5060/5061 and the RTP range
>> to my AstLinux box.
>>
>> cheers,
>> Shamus
>>>
>>> Hi Shamus,
>>>
>>> The 192.168.101.1 address is the first defined INTIP value. This is
>>> automatically assigned in /etc/hosts .
>>>
>>> Describe your network layout, number of internal interfaces, etc. so we can
>>> better help.
>>>
>>> Possibly do you not have any interface defined to the 1st internal
>>> interface but 192.168.101.1 is defined in IPv4 ?
>>>
>>> Lonnie
>>>
>>>
>>> On Jun 19, 2012, at 11:12 AM, Shamus Rask wrote:
>>>
>>>> I've recently activated/established an ISN. To test it, I was trying to
>>>> call myself, but was unable to do so. I have confirmed it is working with
>>>> other friends, so there is some sort of internal routing problem on my end.
>>>>
>>>> I took a quick look in the /etc/hosts file and found the following entries:
>>>>> pbx / # cat /etc/hosts
>>>>> # Automatically generated from internal state.
>>>>> 127.0.0.1 localhost
>>>>> 192.168.101.1 pbx.astlinux pbx
>>>> What is odd is that I'm actually using the 192.168.2.x subnet, and my pbx
>>>> has an IPv4 address of 192.168.2.4. Can anyone explain where the x.x.101.1
>>>> comes from? Is this something I should change?
>>>>
>>>> cheers,
>>>> Shamus
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats.
>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
>> Astlinux-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>
>> Donations to support AstLinux are graciously accepted via PayPal to
>> [email protected].
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Astlinux-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> [email protected].
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
