Subject: Re: [44net] Bad MX records in the ampr.org DNS From: Don Fanning don@00100100.net Date: 05/28/2015 02:45 AM
To: AMPRNet working group 44net@hamradio.ucsd.edu
On Wed, May 27, 2015 at 5:36 PM, Bryan FieldsBryan@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.
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
On Thu, 28 May 2015, Rob Janssen wrote:
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.
To be specific, a CNAME RR points to another name which could be an MX RR. Apart from associated DNSSEC RRs, a CNAME basically overrides anything else defined for that name.
Antonio Querubin e-mail: tony@lavanauts.org xmpp: antonioquerubin@gmail.com
On 2015-05-28 23:06, Antonio Querubin wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Thu, 28 May 2015, Rob Janssen wrote:
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.
To be specific, a CNAME RR points to another name which could be an MX RR. Apart from associated DNSSEC RRs, a CNAME basically overrides anything else defined for that name.
And to add to the that. MX -> CNAME is 'allowed' in DNS, it will just break as Sendmail for instance will then rewrite the To: address.
Eg in the above example it will rewrite mail to @name to some.mail.server.
And that is why you don't want to do CNAMEs with MXs.
Or as described at https://www.sixxs.net/faq/account/?faq=email : 8<----- Using a CNAME in your domain breaks your email because sendmail (and possibly other SMTP software) will rewrite the domain portion of the destination email address to that of the label in the CNAME. See also CNAME records in mail by D. J. Bernstein[1]. Note that having a CNAME for example.tld is of course impossible unless you get the tld to have the same record. Having an MX point to a CNAME record causes additional DNS lookups, which might cross a threshold, and thus cause your mail to be dropped. Additionally "Mail loops back to me" errors might be caused by this. Also see RFC1034[2] - DOMAIN NAMES - CONCEPTS AND FACILITIES for more details. In short: Don't use CNAMEs in relation to SMTP.
[1] http://cr.yp.to/im/cname.html [2] http://www.ietf.org/rfc/rfc1034.txt ----->8
See also https://www.ietf.org/rfc/rfc1912.txt for common mistakes.
Greets, Jeroen
It all originates in requirement that all 44net DNS record must be in the same DNS.
It would be better to let people simply set NS records for their domain and handle DNS on their own name servers. That is how DNS is designed and it is natural and logical way to do.
If someone sets it wrong it is his problem.
Pedja YT9TP
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
The problem is that it's only one domain, ampr.org. So unless it is splitted so that each uses subdomains it makes no sense to resolve each individual name throug its own NS.
Marius, YO2LOJ
-----Original Message----- It would be better to let people simply set NS records for their domain and handle DNS on their own name servers. That is how DNS is designed and it is natural and logical way to do.
On 29.05.15. 12:51, Marius Petrescu wrote:
The problem is that it's only one domain, ampr.org. So unless it is splitted so that each uses subdomains it makes no sense to resolve each individual name throug its own NS.
I thought everyone use subdomains?!?!?!
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
N0.
I'm very happy with G8BPQ.ampr.org.
73, John
-----Original Message----- From: 44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of YT9TP - Pedja Sent: 29 May 2015 17:33 To: AMPRNet working group Subject: Re: [44net] Bad MX records in the ampr.org DNS
(Please trim inclusions from previous messages) _______________________________________________ On 29.05.15. 12:51, Marius Petrescu wrote:
The problem is that it's only one domain, ampr.org. So unless it is splitted so that each uses subdomains it makes no sense to resolve each individual name throug its own NS.
I thought everyone use subdomains?!?!?!
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On 5/29/15 9:33 AM, YT9TP - Pedja wrote:
(Please trim inclusions from previous messages) _______________________________________________ On 29.05.15. 12:51, Marius Petrescu wrote:
The problem is that it's only one domain, ampr.org. So unless it is splitted so that each uses subdomains it makes no sense to resolve each individual name throug its own NS.
I thought everyone use subdomains?!?!?!
No, most ampr.org entries are not subdomained (at least to the callsign level), when I've looked up names. I believe this is to make name resolution more reliable, so that names can be resolved even when connectivity is poor.
I'd suggest that subdomains should be an option for those that want to take the responsibility of maintaining stable name service (could offer stable DNS both on- and off- the 44 net).
Not everyone is up to doing that, though.
- Richard, VE7CVS
On 29.5.2015. 20:16, Richard Chycoski wrote:
I thought everyone use subdomains?!?!?!
No, most ampr.org entries are not subdomained (at least to the callsign level), when I've looked up names.
I am not quite clear what you mean as subdomain.
Can you point out of some sample of domain usage which is not subdomain?
Pedja YT9TP
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
On 5/29/15 12:42 PM, Pedja YT9TP wrote:
I am not quite clear what you mean as subdomain.
Can you point out of some sample of domain usage which is not subdomain?
Pedja YT9TP
Here is a non-subdomained address:
*aa6hf.ampr.org*
Name: aa6hf.ampr.org Address: 44.17.0.128 aa6hf.ampr.org mail exchanger = 10 aa6hf.ampr.org. aa6hf.ampr.org mail exchanger = 20 linux.aa6hf.ampr.org.
Authoritative answers can be found from: *ampr.org nameserver = hamradio.ucsd.edu.* ampr.org nameserver = munnari.OZ.AU. ampr.org nameserver = ns1.defaultroute.net. ampr.org nameserver = ns0.comgw.net. ampr.org nameserver = ns2.threshinc.com. ampr.org nameserver = ampr.org. ampr.org nameserver = ampr-dns.in-berlin.de.
ampr.org internet address = 44.0.0.1
It is not a subdomain, it's address is served by the ampr.org nameservers.
Here is a delegated subdomain (some lines removed for more clarity and less clutter):
*de.ampr.org*
de.ampr.org text = "de.ampr.org - Seit 2012-03-17 im Testbetrieb. hamradio.ucsd.edu *delegated*" de.ampr.org mail exchanger = 20 kle.nw.schule.de. de.ampr.org origin = de.ampr.org mail addr = ipkoord.de.ampr.org
Name: de.ampr.org Address: 134.91.19.148 *de.ampr.org nameserver = db0res.ampr.org.* de.ampr.org nameserver = db0fhn.efi.fh-nuernberg.de. de.ampr.org nameserver = ns.db0fhn.ampr.org. de.ampr.org nameserver = db0res.de.
It is a subdomain because it is being served by de.ampr.org name servers, not ampr.org. No x.de.ampr.org addresses are served by ampr.org. This can be further subdomained, as many times as needed.
Subdomaining hands off (delegates) the responsibility for a namespace (e.g., de.amp.org) or a range of IP addresses (e.g., 44.130/16, meaning 44.130.0.0 through 44.130.255.255) to another entity and nameserver(s).
The advantage of a delegated subdomain is that you can update your subdomain's DNS records without having to get someone else to do it.
The disadvantage is that someone must install, maintain, and operate a DNS server. I do this for my own (non-ham) domains, but I've had decades of experience with DNS servers (I have been working with the Internet since before DNS was created, ALL of the hosts that were public were listed in a single file and installed on every host! :-), not everyone wants to go to that effort.
I'm just getting back into Packet Radio and the 44 net after a decade and a half dedicated to work and family, and I'm still learning how things have been put together in the intervening years.
- Richard, VE7CVS
On 29.05.15. 22:49, Richard Chycoski wrote:
Here is a non-subdomained address:
*aa6hf.ampr.org*
Name: aa6hf.ampr.org Address: 44.17.0.128 aa6hf.ampr.org mail exchanger = 10 aa6hf.ampr.org. aa6hf.ampr.org mail exchanger = 20 linux.aa6hf.ampr.org.
As I thought it is just matter of term definition. I use subdomain as broad definiton of domain which is under some other domain.
By that definition this is subdomain. It is just hosted in the same DNS as top level domain.
*de.ampr.org nameserver = db0res.ampr.org.* de.ampr.org nameserver = db0fhn.efi.fh-nuernberg.de. de.ampr.org nameserver = ns.db0fhn.ampr.org. de.ampr.org nameserver = db0res.de.
I agree this is also subdomain.
The advantage of a delegated subdomain is that you can update your subdomain's DNS records without having to get someone else to do it.
The disadvantage is that someone must install, maintain, and operate a DNS server.
Atually, there are few quite nice online DNS service that provide DNS hosting for free.
http://afraid.org offers very simple user interface that allows anyone with any knowledge of what domain is to set what he needs.
http://xname.org/ is full powered DNS server, also free. It does require some advanced knowledge to set it up.
Thing is, when I asked to set ampr.org subdomain on my own DNS server, it was refused. It was said that it is not allowed, and all subdomains must be set on ampr portal.
My point is that prohibition should be removed. If one wants to set his own DNS for subdomain he should be let to.
Pedja YT9TP
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
It is normal for you to be refused. Allowing you to provide name services for ampr.org would mean you need to provide ALL name services for *.ampr.org, which is obviously not the case. And that restriction is valid and correctly applied and should NOT be removed (which is actually not possible btw).
The correct name servers are registered at the proper TLD, and seting an arbitrary other server would mean that anyone could alter the DNS for the domain, without asking anybody, potentially with malicious intent.
So the only option is to serve a subdomain, which means that e.g *.yt9tp.ampr.org, for which you need to provide a DNS and be proper delegated by ampr.org, without the possibility for you to alter the parent DNS..
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of YT9TP - Pedja Sent: Monday, June 01, 2015 19:53 To: AMPRNet working group Subject: Re: [44net] Bad MX records in the ampr.org DNS
...
Thing is, when I asked to set ampr.org subdomain on my own DNS server, it was refused. It was said that it is not allowed, and all subdomains must be set on ampr portal.
My point is that prohibition should be removed. If one wants to set his own DNS for subdomain he should be let to.
Pedja YT9TP
On 01.06.15. 20:25, Marius Petrescu wrote:
Allowing you to provide name services for ampr.org would mean you need to provide ALL name services for *.ampr.org, which is obviously not the case. And that restriction is valid and correctly applied and should NOT be removed (which is actually not possible btw).
The correct name servers are registered at the proper TLD, and seting an arbitrary other server would mean that anyone could alter the DNS for the domain, without asking anybody, potentially with malicious intent.
So the only option is to serve a subdomain, which means that e.g *.yt9tp.ampr.org, for which you need to provide a DNS and be proper delegated by ampr.org, without the possibility for you to alter the parent DNS..
Maybe we do not understand. I think it is perfectly valid to have for example
yt9tp.ampr.org. NS ns1.mydns.org. yt9tp.ampr.org. NS ns2.mydns.org.
That would allow me to adjust domain yt9tp.ampr.org and subdomains like
www.yt9tp.ampr.org ftp.yt9tp.ampr.org mail.yt9tp.ampr.org aprs1.yt9tp.ampr.org aprs5.yt9tp.ampr.org cluster.yt9tp.ampr.org sdr.yt9tp.ampr.org echolink1.yt9tp.ampr.org wifi.yt9tp.ampr.org
or other domains without further need to deal with ampr.org DNS server directly, but use my own.
Pedja YT9TP
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
Yes of course, what you say is perfectly valid. But that will allow you to set up the subdomain yt9tp.ampr.org on the DNS, not ampr.org as you described it:
Thing is, when I asked to set ampr.org subdomain on my own DNS server, it was refused. It was said that it is not allowed, and all subdomains must be set on ampr portal.
You should have asked for yt9tp.ampr.org, not ampr.org.
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of YT9TP - Pedja Sent: Monday, June 01, 2015 23:31 To: AMPRNet working group Subject: Re: [44net] Bad MX records in the ampr.org DNS
Maybe we do not understand. I think it is perfectly valid to have for example
yt9tp.ampr.org. NS ns1.mydns.org. yt9tp.ampr.org. NS ns2.mydns.org.
That would allow me to adjust domain yt9tp.ampr.org and subdomains like
www.yt9tp.ampr.org ftp.yt9tp.ampr.org mail.yt9tp.ampr.org aprs1.yt9tp.ampr.org aprs5.yt9tp.ampr.org cluster.yt9tp.ampr.org sdr.yt9tp.ampr.org echolink1.yt9tp.ampr.org wifi.yt9tp.ampr.org
or other domains without further need to deal with ampr.org DNS server directly, but use my own.
Pedja YT9TP
www.yt9tp.ampr.org ftp.yt9tp.ampr.org mail.yt9tp.ampr.org aprs1.yt9tp.ampr.org aprs5.yt9tp.ampr.org cluster.yt9tp.ampr.org sdr.yt9tp.ampr.org echolink1.yt9tp.ampr.org wifi.yt9tp.ampr.org
or other domains without further need to deal with ampr.org DNS server directly, but use my own. Pedja YT9TP
We allow complex hostnames in the left hand side of the master AMPR.ORG DNS servers, so it's quite possible to have names like those above as the LHS of A or CNAME or MX records. Because you can do this and because callsigns are unique worldwide, we usually don't need subdomains and delegated name service.
One reason we don't allow arbitrary NS records is the issue of reverse lookups - the corresponding PTR records. When you register a name such as 'yt9tp' as an 'A' record in the AMPR.ORG domain, we automatically generate the corresponding PTR record in the 44.in-addr reverse domain.
If we delegated e.g., yt9tp to another nameserver, we would not be able to generate the proper PTR record, and neither would they. I don't like the idea of there not being a corresponding PTR record for each A record; I believe that is poor networking practice and strongly discourage it.
It would require delegating arbitrary parts of the 44.in-addr domain, which is a whole bag of worms I don't like to do without a really good reason. Depending on delegation width, it can be a painful process requiring significant manual intervention in the DNS database so I do it only for exceptional cases involving directly-routed subnets.
There are seven AMPR.ORG and 44.in-addr DNS servers located around the world. The chance that all of them will be down at once is close to zero. We allow people to AXFR their content so it is perfectly possible to have a redundant DNS server on your local net which can answer queries regarding those zones even if you are partitioned from the Internet somehow. (Although if you really need your DNS resolution to work in the face of disconnection from the rest of the Internet, you'll possibly need to supply your own cache of the root and .ORG servers as well - depends on how your DNS server does its lookups.) - Brian
On 2.6.2015. 02:55, Marius Petrescu wrote:
Yes of course, what you say is perfectly valid. But that will allow you to set up the subdomain yt9tp.ampr.org on the DNS, not ampr.org as you described it:
Thing is, when I asked to set ampr.org subdomain on my own DNS server, it was refused. It was said that it is not allowed, and all subdomains must be set on ampr portal.
You should have asked for yt9tp.ampr.org, not ampr.org.
I never asked for ampr.org. I always talked about subdomains of ampr.org.
Pedja YT9TP
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
O.k.Pedja,
I seems it was my misunderstanding. But you gor Brian Kantors explanation.
73s, Marius YO2LOJ
Pedja;
On Mon, 2015-06-01 at 18:52 +0200, YT9TP - Pedja wrote:
Thing is, when I asked to set ampr.org subdomain on my own DNS server, it was refused. It was said that it is not allowed, and all subdomains must be set on ampr portal.
My point is that prohibition should be removed. If one wants to set his own DNS for subdomain he should be let to.
You can run a robot script and import the two zonefiles into a local DNS server if you wish. These are updated periodically every so-many-hours and are available via FTP from ucsd. One needs not be a registered slave DNS. Just import the two zonefiles into your local nameserver and reload it.
Years ago I was one of the secondary slave servers but now with the excessive volume of DNS exploiter robots hammering away at the internet, I'm almost glad I don't anymore.
On 01.06.15. 20:37, Brian wrote:
You can run a robot script and import the two zonefiles into a local DNS server if you wish. These are updated periodically every so-many-hours and are available via FTP from ucsd. One needs not be a registered slave DNS. Just import the two zonefiles into your local nameserver and reload it.
Why would I need that?
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
Pedja;
On Mon, 2015-06-01 at 22:33 +0200, YT9TP - Pedja wrote:
Why would I need that?
If you're looking to be able to serve ampr.org dns resolutions for your local region you may want to do that.
However, for wanting to host just your portion of it and remap it to another nameserver just go as far as the whois servers. ampr.org is listed but yt9tp.ampr.org is not: n1uro@n1uro:~$ whois ampr.org Domain Name:AMPR.ORG Domain ID: D32507-LROR Creation Date: 1988-04-27T04:00:00Z Updated Date: 2013-03-13T17:24:24Z Registry Expiry Date: 2022-04-28T04:00:00Z Sponsoring Registrar:Network Solutions, LLC (R63-LROR) Sponsoring Registrar IANA ID: 2 WHOIS Server: Referral URL: Domain Status: clientTransferProhibited -- http://www.icann.org/epp#clientTransferProhibited Registrant ID:25462948-NSI Registrant Name:AmateurRadioDigital Communications Registrant Organization:AmateurRadioDigital Communications Registrant Street: c/o Brian Kantor Registrant Street: M/S 0124 Registrant City:San Diego Registrant State/Province:CA Registrant Postal Code:92093-0124 Registrant Country:US Registrant Phone:+1.9999999999 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email:bdale@GAG.COM Admin ID:15486645-NSI Admin Name:Bdale Garbee Admin Organization:Garbee and Garbee Admin Street: 4390 Darr Circle Admin City:Black Forest Admin State/Province:CO Admin Postal Code:80908-3207 Admin Country:US Admin Phone:+1.7194941874 Admin Phone Ext: Admin Fax: +1.7194952061 Admin Fax Ext: Admin Email:bdale@GAG.COM Tech ID:5523676-NSI Tech Name:Brian Kantor Tech Organization:Univ Calif San Diego Tech Street: 9500 Gilman Dr m/s 0404 Tech City:La Jolla Tech State/Province:CA Tech Postal Code:92093-0404 Tech Country:US Tech Phone:+1.8585340000 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email:bkantor@UCSD.EDU Name Server:MUNNARI.OZ.AU Name Server:HAMRADIO.UCSD.EDU Name Server:NS.NONANET.NET.UK Name Server:NS1.DEFAULTROUTE.NET Name Server:AMPR-DNS.IN-BERLIN.DE Name Server:NS2.THRESHINC.COM Name Server:AMPR.ORG
------------------------- n1uro@n1uro:~$ whois yt9tp.ampr.org NOT FOUND n1uro@n1uro:~$
Hi Gang
May I suggest our solution to the same issue
Was to register our own domain ampr.org.au (Australia). I have had it for many years from when packet was at an all-time high, and due to differences to get things done and ip space was hard to get done. So a few people back in the day got me into packet on a subnet and until I got access to the AMPR ORG dns my solution was to do what I did.
I can see what he wants to do here and use his own dns - Maybe consider getting your own domain name that sits within your countries dns naming structure and use it as well as the ampr.org portal I can see why people don't want to allow sub domains in the ampr zone file. Starters it is populated with stations that no longer exist.
I still use the ampr.org.au zone file today as there is entries that can't be entered into the ampr.org zone
Finally in regards to ampr.org zone It may not work to everyone's need, but it works the majority!
My 5c worth
Samantha Scafe VK4AA
-----Original Message----- From: 44net-bounces+vk4aa=vk4aa.com.au@hamradio.ucsd.edu [mailto:44net-bounces+vk4aa=vk4aa.com.au@hamradio.ucsd.edu] On Behalf Of Brian Sent: Tuesday, 2 June 2015 6:49 AM To: AMPRNet working group Subject: Re: [44net] Bad MX records in the ampr.org DNS
(Please trim inclusions from previous messages) _______________________________________________ Pedja;
On Mon, 2015-06-01 at 22:33 +0200, YT9TP - Pedja wrote:
Why would I need that?
If you're looking to be able to serve ampr.org dns resolutions for your local region you may want to do that.
However, for wanting to host just your portion of it and remap it to another nameserver just go as far as the whois servers. ampr.org is listed but yt9tp.ampr.org is not: n1uro@n1uro:~$ whois ampr.org Domain Name:AMPR.ORG Domain ID: D32507-LROR Creation Date: 1988-04-27T04:00:00Z Updated Date: 2013-03-13T17:24:24Z Registry Expiry Date: 2022-04-28T04:00:00Z Sponsoring Registrar:Network Solutions, LLC (R63-LROR) Sponsoring Registrar IANA ID: 2 WHOIS Server: Referral URL: Domain Status: clientTransferProhibited -- http://www.icann.org/epp#clientTransferProhibited Registrant ID:25462948-NSI Registrant Name:AmateurRadioDigital Communications Registrant Organization:AmateurRadioDigital Communications Registrant Street: c/o Brian Kantor Registrant Street: M/S 0124 Registrant City:San Diego Registrant State/Province:CA Registrant Postal Code:92093-0124 Registrant Country:US Registrant Phone:+1.9999999999 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email:bdale@GAG.COM Admin ID:15486645-NSI Admin Name:Bdale Garbee Admin Organization:Garbee and Garbee Admin Street: 4390 Darr Circle Admin City:Black Forest Admin State/Province:CO Admin Postal Code:80908-3207 Admin Country:US Admin Phone:+1.7194941874 Admin Phone Ext: Admin Fax: +1.7194952061 Admin Fax Ext: Admin Email:bdale@GAG.COM Tech ID:5523676-NSI Tech Name:Brian Kantor Tech Organization:Univ Calif San Diego Tech Street: 9500 Gilman Dr m/s 0404 Tech City:La Jolla Tech State/Province:CA Tech Postal Code:92093-0404 Tech Country:US Tech Phone:+1.8585340000 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email:bkantor@UCSD.EDU Name Server:MUNNARI.OZ.AU Name Server:HAMRADIO.UCSD.EDU Name Server:NS.NONANET.NET.UK Name Server:NS1.DEFAULTROUTE.NET Name Server:AMPR-DNS.IN-BERLIN.DE Name Server:NS2.THRESHINC.COM Name Server:AMPR.ORG
------------------------- n1uro@n1uro:~$ whois yt9tp.ampr.org NOT FOUND n1uro@n1uro:~$
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
On 2.6.2015. 00:55, Sam VK4AA wrote:
May I suggest our solution to the same issue
Was to register our own domain ampr.org.au (Australia).
Sure. I gave up using subdomain of ampr.org and decided to use my own domain.
I just thought that idea is that we all use subdomans of ampr.org.
Pedja YT9TP
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
In the DNS hierarhy you have Top Level Domanis (TLD) in the root zone (like .com, .net and in our case .org). Then you have 'ampr' as single domain.
All entries resolvable directly to an host IP in 'ampr' are in this domain and are not delegated. e.g. yo2loj.ampr.org (44.182.20.36).
If I would set up a subdomain, I would have different machines with different IPS under yo2loj.ampr.org, an that would be a subdomain. e.g. mail.yo2loj.ampr.org, www.yo2loj.ampr.org, ftp.yo2loj.ampr.org, ns.yo2loj.ampr.org and so on. In that case, name resolutions could be delegated for all *.yo2loj.ampr.org names to lets say ns.yo2loj.ampr.org and I would need to maintain my own DNS server(s).
That means that in a DNS resolution there would be 2 lookups, first one to the ampr.org NS to get my NS as defined there, and a second lookup to my local NS to resolve that name. And it also means that if my NS is down, resolution will not be possible.
Now if one uses a single <callsign>.ampr.org with one IP, this is resolved directly at ampr.org level, avoiding both issues, but keeping the name resolution out of his hands.
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Pedja YT9TP Sent: Friday, May 29, 2015 22:43 To: AMPRNet working group Subject: Re: [44net] Bad MX records in the ampr.org DNS
...
Can you point out of some sample of domain usage which is not subdomain?
Pedja YT9TP
While we're on the topic of DNS, I've noticed some of the newer MX records aren't properly functioning for some reason. gmx/gmail/yahoo and some of the other more local ISPs ie: Optonline, Comcast, Cox mail systems can't resolve some of the newer entries.
I have seen cases where a point within a domain has their own MX records, and others also exist but one contains an error, the rest of the MX records may get ignored. As it stands now, n1rcw.ampr.org is resolvable as a point within ampr.org but it's MX record (which does properly exist) is showing unresovable by some of the above mentioned mail servers.
It's always good to keep DNS records as error free as possible as funky things can (and most likely will) happen because of such.
-
Antonio Querubin -
Brian -
Brian Kantor -
Jeroen Massar -
John Wiseman -
Marius Petrescu -
Pedja YT9TP -
Richard Chycoski -
Rob Janssen -
Sam VK4AA -
YT9TP - Pedja