[OZAPRS] Problem with rotate.aprs.net.au address?
Damien Gardner Jnr
vk2tdg at gmail.com
Mon Jan 7 15:29:11 EST 2013
On 5/01/2013 5:26 PM, Liz wrote:
> yes, you need to update your server config.
That really won't make any difference... :)
rotate.aprs.net.au. 60 IN A 220.127.116.11
rotate.aprs.net.au. 60 IN A 18.104.22.168
Ok, both .au servers. That's second.aprs and third.aprs
the aprs2 address:
aunz.aprs2.net. 3600 IN A 22.214.171.124
aunz.aprs2.net. 3600 IN A 126.96.36.199
aunz.aprs2.net. 3600 IN A 188.8.131.52
aunz.aprs2.net. 3600 IN A 184.108.40.206
aunz.aprs2.net. 3600 IN A 220.127.116.11
That's second.aprs, third.aprs. some unknown AU server, and two unknown
NZ servers (one of which used to be third.aprs.net.au).
So any problem with one of those servers will still exist, just that
you'll hit the issue one in five connects, rather than one in two connects..
Grant: try manually specifying third.aprs.net.au and see how you go - it
may be that there's an issue on that server?
If third.aprs.net.au plays up, try that 18.104.22.168 address - That
runs the same software as third - That'll pin down an issue with the
Also, try 22.214.171.124 - that runs the same software as second..
I have a theory that it's an issue with APRSC? Will be interesting to
BTW, for 'reliable' packet tracing, ignore aprs.fi, use the dump from
In your case Grant, you want
More information about the OZAPRS