I know a couple of groups now have proper reverse delegation of DNS for their subnets… Wondering who to drop a line to so I can get 44.103.0.0/19 delegated to a.ns.mi6wan.net and b.ns.mi6wan.net ?
Didn’t see it in the portal or wiki and my notes from a few months ago are foggy...
--
Fredric Moses - W8FSM - WQOG498
fred(a)moses.bz
All,
I've added a new tool that I'd like you to test. This web application
should provide the registration code required by APRS software suites.
In order to use it, you must browse to:
http://kb3vwg-010.ampr.org/tools/aprscode
or
http://44.60.44.10/tools/aprscode
If you're on AMPRNet, you should be able to enter the callsign and look
up the registration code. If you access it from outside of AMPRNet, you
will be prompted for an access code (1234).
Please let me know how it works
73,
KB3VWG
> Subject:
> Re: [44net] Bad MX records in the ampr.org DNS
> From:
> Don Fanning <don(a)00100100.net>
> Date:
> 05/28/2015 02:45 AM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> On Wed, May 27, 2015 at 5:36 PM, Bryan Fields<Bryan(a)bryanfields.net> wrote:
>
>>
>>> > >That is not true at all. The previous paragraph states that it must
>>> > >process the entire FQDN and not many any inferences as to the domain's
>>> > >relationship with the FQDN.
>> >
>> >I'd like to try it out then, as I'm certain this doesn't work that way in
>> >most
>> >resolvers for MX's. I've run into it before even.
>> >
>> >
> I can tell you that GMail's MX RR's work in this fashion. I don't need to
> know their A record for my DNS. I just add their CNAME'ed MX records to my
> domain files and my mail shows up. And my domain isn't hosted by them.
> Just my mail hosting.
>
> https://support.google.com/a/answer/33915?hl=en
Indeed, it is allowed to have some record like:
sub.domain IN CNAME another.domain
with
another.domain IN MX 10 hostname
But that is not what I mean. What is NOT allowed (by the spec) is to have:
name IN MX 10 mail
mail IN CNAME some.mail.server
So you can have a CNAME pointing to MX, but not MX pointing to CNAME.
Also, I don't understand the relation to the Google example. The support page you mention gives a
list of MX records with names that are all A and AAAA records, no CNAME involved at all.
In practice, it appears that the CNAME works with some mail transfer agents. But bind9 is complaining.
The literal IP address in an MX record results in 2 warnings, one that there is an address in the MX record
and another that the 111.222.333.444.ampr.org is not defined. This of course is because an address is not
expected there, and it is treated as a domain name relative to the $origin of the zone.
When your server has no associated name, of course you can assign one within ampr.org.
Also, when you want your server to SEND mail in addition to RECEIVING it, you need to have a name and a
matching reverse, or many spamfilters will just drop your mail on the floor.
Rob
Don't get me wrong. I'm not saying people should ignore the RFC1035
standards. I'm just saying its possible. The one's I'm aware of are all
companies using 'In-House' mail systems designed to either keep the mail
staying in-house, and/or prevent outside mail from getting in.
But, as pointed out, this group should be following the RFC1035 standard.
----------
Wm Lewis (KG6BAJ)
AMPR Net IP Address Coordinator - Northern and Central California Regions
(A 100% Volunteer Group)
(530) 263-1595 (Home/Office)
______________________________________________
----------
This message is for the designated recipient only and MAY CONTAIN
PRIVILEGED OR CONFIDENTIAL INFORMATION.
If you have received it in error, please notify the sender immediately and
delete the original. Any other use of this E-mail is prohibited.
At 03:48 PM 5/27/2015, you wrote:
>(Please trim inclusions from previous messages)
>_______________________________________________
>On Wed, May 27, 2015 at 3:41 PM, William Lewis <kg6baj(a)n1oes.org> wrote:
> > Where you say "Owners, please update them with a proper hostname instead of
> > the literal IP address." I would like to point out that it is entirely
> > possible to have an IP address that has no HOSTNAME assigned to it at all.
> > The most common are used for mail. I use 2 that are setup this way for
> > security reasons.
>
>MX records must point to a hostname. Here's a good description of why:
>http://serverfault.com/a/663122
>
>But the bottom line is: it's the spec.
>
>Tom KD7LXL
>_________________________________________
>44Net mailing list
>44Net(a)hamradio.ucsd.edu
>http://hamradio.ucsd.edu/mailman/listinfo/44net
> 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/
