> Subject:
> Re: [44net] Bad MX records in the ampr.org DNS
> From:
> Rob Janssen <pe1chl(a)amsat.org>
> Date:
> 05/25/2015 09:18 PM
>
> To:
> 44net(a)hamradio.ucsd.edu
>
Over the past few days, I have found and deleted about 2000 bad MX records and 935 bad CNAME records.
It appears that in the past some standard procedure has inserted many records like this:
callsign IN A 44.x.x.x
callsign IN MX 10 callsign
Later, apparently the IN A records have been deleted during some cleanup, but the IN MX records remained.
They of course serve no function, and bind9 complains when the zone is loaded.
Furthermore, a large number of records like this existed:
something IN CNAME callsign
Again, the corresponding callsign has been deleted in the past (its A records, and now also the dangling MX)
and that CNAME points to nothing. I have removed those as well.
There was a number of records like this:
callsign IN MX 10 44.x.x.x
This format is not allowed. A hostname should appear instead of the literal IP address. I have changed the
records to have the corresponding hostname from the ampr.org zone.
Errors that still remain are: records of the format:
callsign IN MX 10 111.222.333.444 (referring to a public IP)
Those are:
*.xe2mbq IN MX 5 200.23.120.6
*.xe2yun IN MX 10 200.23.120.6
grr.kc8lcp IN MX 10 204.227.124.61
ka9kim IN MX 30 207.74.35.36
kc5ghg IN MX 20 206.61.58.173
linux.n8ivx IN MX 10 209.4.74.218
n5dbx IN MX 20 206.61.57.1
n8ivx IN MX 10 208.231.146.247
pacgate.zl1udy IN MX 0 202.14.100.2
ur4wwe IN MX 20 194.44.138.1
us5we IN MX 20 194.44.138.1
va3hum IN MX 20 206.248.184.186
va3yh IN MX 20 206.248.184.186
ve3fub IN MX 20 206.248.184.186
wb5fro IN MX 20 206.61.58.173
yo3ru IN MX 10 141.85.43.57
Owners, please update them with a proper hostname instead of the literal IP address.
Also, these names are used in records like:
callsign IN MX 10 name
but the name refers to a CNAME, not to an IN A record. This is not allowed by the spec, although it usually
works. If possible, change the MX to have a hostname that points to an A record. The illegally used CNAMEs are:
alcoy
athnet
bbs.vk2czr
club.oh1rbi
ea4rct
edugraf
etxgate.nb5i
g0wfs
gateway.n8xja
gb7sol-10
gb7tvg
gw.ir3ip
haifa
hougw2
hougw
jh3qnh
ka7oei
kb7yw
kj7pf
mail.ncpa
mx2.ir3ip
poagw
pp5dq
pp5dq-gw
pp5mcb-gw-7
pp5uf
router.kl7eet
va3lug
ve3cgr
ve3mch
ve3uow
ve6lip
vk2pk
vk2yui
vk5lz
vk5tty
w7yg
wa7ipx
wa7slg
Of course there is still lots of other out-of-date info in the DNS, but now at least it is more standards compliant.
Rob
> Subject:
> [44net] hu.ampr.org DNS
> From:
> Norbert Varga <nonoo(a)nonoo.hu>
> Date:
> 05/25/2015 11:37 AM
>
> To:
> 44net(a)hamradio.ucsd.edu
>
>
> Dear 44net,
>
> First of all, hello to everybody on the list, I've just subscribed.
> We're currently building the hamnet network in Hungary, now we have some
> working links, tunnels and hosts which I've already added to the hamnetdb.
>
> I saw that some host names can be resolved using "regular" internet DNS
> servers, like router.db0ajw.ampr.org can be resolved to 44.225.36.129 using
> Google's 8.8.8.8 DNS server.
>
> My question is that how can this be accomplished? If we have a DNS server
> which can resolve our hosts to IPs and backwards, can one of the AMPR DNS
> servers be set up to transfer our zones?
>
> I saw that the portal has a DNS section but it's not live yet.
>
> Thanks for the help and 73s de HA2NON
Do you have a reason to use a subdomain .hu.ampr.org instead of putting the Hungarian
callsigns directly under .ampr.org as almost everyone else is doing?
You can easily submit your DNS records to the ampr.org DNS service.
This is accomplished using a mail robot where you can mail your zone changes and that
will put them in the flat .ampr.org zone.
You can also arrange that NS records for hu.ampr.org are put in the ampr.org DNS.
Then all requests for callsign.hu.ampr.org will be referred to your servers. Of course your
servers have to be available both on amprnet and on internet.
This is now done by Germany, Spain and Sweden.
(but I do not see a compelling reason to do that)
Rob
> Subject:
> Re: [44net] Bad MX records in the ampr.org DNS
> From:
> John Ronan <jpronans(a)gmail.com>
> Date:
> 05/25/2015 11:00 AM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> On 25/05/15 09:52, Rob Janssen wrote:
>> linux.ei2edb.ampr.org/MX 'ei2edb.ampr.org' has no address records (A or AAAA)
>> os2.ei2edb.ampr.org/MX 'ei2edb.ampr.org' has no address records (A or AAAA)
>> ei7gm.ampr.org/MX 'bbs.ei7gm.ampr.org' is a CNAME (illegal)
>> ei7gm.ampr.org/MX 'dubbbs.ei7gm.ampr.org' has no address records (A or AAAA)
>> 486.ei9fk.ampr.org/MX 'ei9fk.ampr.org' has no address records (A or AAAA)
> Delete them,
>
> They are all ancient DNA.
>
> Regards
> John
> EI7IG
After consulting Brian I have deleted all MX records that point to names for which no address
record exists, including 4 of the above. 867 records in total.
Looking at CNAME and dotted address in MX records will be the next step.
Note that an MX record must have a hostname that in turn has A and/or AAAA records.
So MX records that contain e.g. "44.0.0.1" are not allowed. Neither are MX records that have
a name that in turn is a CNAME pointer.
Most mail software will probably handle those bad MX records, so I have not yet deleted them.
I advise those that make use of their MX records to fix them (replace the IP address with a
hostname that resolves to that address, and replace a name that refers to a CNAME with the
name that the CNAME points to).
Then I can check things again in some time.
Rob
Dear 44net,
First of all, hello to everybody on the list, I've just subscribed.
We're currently building the hamnet network in Hungary, now we have some
working links, tunnels and hosts which I've already added to the hamnetdb.
I saw that some host names can be resolved using "regular" internet DNS
servers, like router.db0ajw.ampr.org can be resolved to 44.225.36.129 using
Google's 8.8.8.8 DNS server.
My question is that how can this be accomplished? If we have a DNS server
which can resolve our hosts to IPs and backwards, can one of the AMPR DNS
servers be set up to transfer our zones?
I saw that the portal has a DNS section but it's not live yet.
Thanks for the help and 73s de HA2NON
--
Norbert Varga
http://www.nonoo.hu/
> Subject:
> Re: [44net] ampr-gateways.org
> From:
> Steve L <kb9mwr(a)gmail.com>
> Date:
> 05/23/2015 08:09 PM
>
> To:
> "44net(a)hamradio.ucsd.edu" <44net(a)hamradio.ucsd.edu>
>
>
> I had to look at it via the wayback machine. For a minute I though
> this was the site that the nice map of gateways.
It looks like that is just another standalone site that you need to enter your data on, and that
almost nobody knows it exists. IMHO such a site is only worth doing when it is linked to the
actual data, not when it is yet another place to enter data.
Check http://hamnetdb.net/ when you are looking for a site that brings some real value. In
fact it offers much more than the portal and I think it should be considered to merge the portal
function into it. Its ways of handling subnets and addresses are much more usable than those
of the portal, and it can do so much more. It only needs a section to enter data for IPIP gateways.
Rob
I had to look at it via the wayback machine. For a minute I though
this was the site that the nice map of gateways.
Turns out that is:
http://www.ampr-gates.net/frame_e.htm
It would be really nice to have gateways portion of the portal list
some geographic info. For those looking for connectivity to area
XXX. I think this is our main selling point and we need to advertise
it a bit.
Right now if you lookup each gateway subnet you can derive the
geographic area from the networks portion of the portal.
Thanks again for your work Chris.
Hi all,
I'm new to amprnet and linux and try to get my RaspberryPi connected
with the 44net. I have setup the Pi and configured IPIP tunl0. I can
ping to 44.137.0.0/16. The problem is that I do not receive any RIPv2
packets with ampr-ripd or rip44d. The situation is that the Pi is
behind the DMZ of my ISP router and I think that's causing the
problem. Have try ed the cron as a 1 minute ping as suggested at
http://n1uro.ampr.org/linuxconf/amprnat.txt but without result.
Do you have any suggestions or advise on what to do to get this running?
73, Fred/PA8F
>
> > On 13.5.2015. 04:55, Andrew Ragone (RIT Alumni) wrote:
> >
> >> With that said, I am not sure what the advantage of this is (aside from
> >> perhaps the dynamic IP issue you mention), though, since you could
> always
> >> write a script to login to the AMPRNet portal and tweak the IPIP tunnels
> >> with any WAN IP address updates. When you have the free gateway over in
> >> California already, it seems like that would be the way to go aside from
> >> directly advertising your own BGP CIDR block.
> >>
> >
> > I guess this would allow anyone with any decent router with VPN client
> > capability) to be able to connect to 44net without requirements for
> > struggling with dedicated computer and very specific installation to make
> > it run.
> >
> > Yes, exactly and well said! that's exactly the point I've been pushing
> for a long time. the single dedicated IP is taken care of by the cloud
> based hub and a relitively simple setup on your client router at your
> network edge simply makes 44net show up on your lan. no dedicated machine,
> no dedicated or special software, no having to write custom config files,
> just easy and instantly deployable using standard protocols used everyday
> that real people use often and understand.
>
> Eric
>
Hi Eric,
Are you doing the BGP announce or would the hosting provider you are
proposing we share doing the announce?
Are you familiar with what the HamWAN group is doing with their Open
Peering Policy (http://www.hamwan.org/t/Open+Peering+Policy)?
Rial F Sloan II
N0OTZ
