Think we have it working now
Some difficulty troubleshooting because of my ISP caching things
Thanks for all your help
JN
Lonnie Abelbeck wrote:
John,
OK, then give this a try for DNS Service Type: [ User Defined >>> ]
--
dyn...@dyndns.org --dyndns_server_name ddns.ckts.info --dyndns_server_
John,
OK, then give this a try for DNS Service Type: [ User Defined >>> ]
--
dyn...@dyndns.org --dyndns_server_name ddns.ckts.info --dyndns_server_url
/nic/update?
--
Lonnie
On Aug 5, 2013, at 9:57 AM, John Novack wrote:
> That does eliminate the inadyn error message, but it seems it isn't se
That does eliminate the inadyn error message, but it seems it isn't sending the
ip address in correct format.
here is the response from the manager of the ddns server
ddclient works to his server, but from my understanding ddclient is a perl
script which doesn't run in AstLinux
Is inadyn using
Hi John,
Give this a try...
DNS Service Type: [ User Defined >>> ]
with the string...
--
custom@http_svr_basic_auth --dyndns_server_name ddns.ckts.info
--dyndns_server_url /nic/update?
--
It is a bit of a hack, but may work.
Lonnie
On Aug 4, 2013, at 8:12 PM, John Novack wrote:
> I have an
I have an older AstLinux system ( 0.7.10 ) that I have been attempting to get
inadyn working on a dynamic dns server other than dyndns, with no joy.
Using the GUI interface, I have set up what appears to be the correct values, (
A similar setup with ddclient on Linux works ) but inadyn throws a
On Nov 28, 2012, at 2:29 PM, Michael Knill wrote:
> Thanks Lonnie. Yes you are right.
> I tried setting a public address with Dyn DDNS and it worked fine actually.
> I don't need any routes as devices on the data VLAN only need to access
> Astlinux and nothing else.
> I thought about using the
Thanks Lonnie. Yes you are right.
I tried setting a public address with Dyn DDNS and it worked fine actually.
I don't need any routes as devices on the data VLAN only need to access
Astlinux and nothing else.
I thought about using the external interface but I don't want to open up ports
and don'
Michael,
Ahhh, you are doing a scenario #1, but only for phones, in parallel with the
existing data network.
But, you want connectivity from the existing data network to your AstLinux
network for admin purposes ?
Your solution seems fine (manually adding LAN gateway to DNS), not that using
Dy
You can run two instances of inadyn... manually adding the second one to
rc.local and providing a separate config file. You would have to look at
the docs for inadyn to determine how to tell it to monitor a different
interface than the default external IF that the default astlinux inadyn
will moni
Thanks Lonnie but you missed a scenario. As we still only have DSL broadband
here and/or if I am installing a separate system with broadband connection for
a customer, the data network needs connectivity to the internal data VLAN
interface on Astlinux but it is not the default gateway so only co
Hi MIchael,
No, Dynamic DNS is only for the EXT interface.
I don't see how this is a problem, the phone's VLAN's are under your control,
correct ?
Network -> Network Services: { Configure DNS Hosts }
can define a DNS entry for your LAN1 gateway address, who's scope would only be
local to AstL
Hi group
Just out of interest. Is it possible to advertise more than one interface with
inadyn. I want to advertise EXT and LAN1 interface to Dyn (different
subdomains).
This is so I can distribute a full plug and play system where the phones are on
a dedicated VLAN and the data VLAN obtains it
Hi John,
When thinking about Dynamic DNS, be aware of a cool free service by the OpenDNS
folks...
(supported in AstLinux since 0.7.5)
DNS-O-Matic
https://www.dnsomatic.com/
Services supported by DNS-O-Matic
http://www.dnsomatic.com/wiki/supportedservices
I use DNS-O-Matic mostly for testing,
I just changed one errant machine to go to a different site to check the ip
Not sure if that will do the trick or not.
Glad to know the default is in place and working for many
I understand why dyn has that requirement, but if things don't work it
can be a PITA!
Someone mentioned another such ser
David,
According to my /tmp/etc/inadyn.conf file:
forced_update_period 2419200
which is 28 days, is the default in astlinux. So that should be
sufficient for meeting DynDNS's requirements.
-James
On 04/26/2012 10:27 AM, David Kerr wrote:
There is a flag on inadyn (--forced_update_period) th
By default AstLinux sets:
--
forced_update_period 2419200
--
(28 Days) for all Service Types.
John, my guess the "forced update" failed because of connectivity issues or
such.
Lonnie
On Apr 26, 2012, at 9:27 AM, David Kerr wrote:
> There is a flag on inadyn (--forced_update_period) that will
There is a flag on inadyn (--forced_update_period) that will force an
update to the dyndns service even if the IP has not changed. Time is in
seconds, see inadyn man page. I do not know if there is a default but
adding --forced_update_period=2592000 should do it every 30 days.
David
On Wed, Apr
Interesting, I had no idea about the requirement. I definitely have the
free account with them. Like I mentioned earlier, I have had my box go
six plus months without a reboot or IP change, and I know that my DynDNS
account is still working and I've never gotten an
email/alert/warning/etc. And
When one has a dyndns free account, one has to log in every 28-30 days
to confirm that the account is still needed, even if the IP address
hasn't changed
On my large asterisk box I use ddclient, which does this automatically,
but it seems, at least on some AstLinux boxes with inadyn this doesn't
John,
I've used inadyn with DynDNS at home for almost three years now, and
have never experienced a single issue. Granted my dynamic IP has only
changed once in that time (outside of when we moved, which would have
caused it to re-authenticate anyway when I powered it back on), but even
in the
I have several units with inadyn enabled, and it seems to do the job
with ip updating, but the dyndns requirement to be "touched" once a
month doesn't seem to perform that function. Any suggestions or has
anyone else had a similar experience.
Several different versions of AstLinux seem to exper
This is normal when there is a problem communication with the server.
It will probably fix itself with time.
Lonnie
On Mar 6, 2011, at 2:01 PM, John Novack wrote:
> Any clue what this means?
>
> Mar 6 14:00:30 NCTM user.warn INADYN[1641]: INADYN:IP: Error 0x68 in recv()
> Mar 6 14:00:30 NCTM
Any clue what this means?
Mar 6 14:00:30 NCTM user.warn INADYN[1641]: INADYN:IP: Error 0x68 in recv()
Mar 6 14:00:30 NCTM user.warn INADYN[1641]: W: DYNDNS: Error
'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 6 14:00:30 NCTM user.warn INADYN[1641]: W:'RC_IP_RECV_ERROR' (0x15)
updating th
Lonnie Abelbeck wrote:
> John,
>
> The latest AstLinux uses inadyn 1.96.2 that we have patched to fix issues and
> add features. Unfortunately inadyn has not been officially supported for
> some time. Though it still works well.
>
In the link I posted, there was mention of 1.97 as well.
W
John,
The latest AstLinux uses inadyn 1.96.2 that we have patched to fix issues and
add features. Unfortunately inadyn has not been officially supported for some
time. Though it still works well.
In older AstLinux (pre 0.7.0 ?), the site "getip.krisk.org" was used to
determine the public IP
with further investigation, it seems the source of the problem is dyndns
and their checkip servers. the secondary problem is inadyn, which, once
it fails on a specific server, continues to hit that ip rather than
trying one of the others.
Dyndns needs to fix their checkip servers to resolve thi
Michael Keuter wrote:
> On Sat, 18 Dec 2010 07:59:05 -0600, Darrick Hartman
> wrote:
>
>> John,
>>
>> I believe this has been mentioned before. You can manually mount the
>> runnix partion. Also, current versions of AstLinux include the
>> dosfslabel command which will allow you to label
I'm pretty sure there were several changes and fixes related to InaDyn
since that release.
Darrick
On 12/18/2010 08:17 AM, John Novack wrote:
> I probably will not attempt this remotely, as this chap is some 6 hours away
> IF his unit has a removable CF card, I may simply mail him another newer
I probably will not attempt this remotely, as this chap is some 6 hours away
IF his unit has a removable CF card, I may simply mail him another newer one
I have several of these out and working, so am hesitant to mess with
working units!
I may give it a try on a test bed here though, some day whe
On Sat, 18 Dec 2010 07:59:05 -0600, Darrick Hartman
wrote:
> John,
>
> I believe this has been mentioned before. You can manually mount the
> runnix partion. Also, current versions of AstLinux include the
> dosfslabel command which will allow you to label the RUNNIX partition.
>
> mount -t v
John,
I believe this has been mentioned before. You can manually mount the
runnix partion. Also, current versions of AstLinux include the
dosfslabel command which will allow you to label the RUNNIX partition.
mount -t vfat /dev/hda1 /oldroot/cdrom
Then either manually place the new .run file
I have an AstLinux 0.5 install that has been receiving error messages
and failing to update the address.
A reboot ( after 250 days ) seemed to fix it, but then this morning the
error reappears.
Any INADYN expert have a suggestion?
Given this is a 0.5 install, remote upgrade is not possible due t
32 matches
Mail list logo
