Re: [vox-tech] some people can't send to list

2015-03-21 Thread Alex Mandel
If you're seeing this on the list then I think it's fixed.

-Alex

On 03/21/2015 05:29 PM, Brian E. Lavender wrote:
> Echo!
> 
> On Sat, Mar 21, 2015 at 04:58:33PM -0700, Bill Kendrick wrote:
>>
>> Brian came over, I did the song & dance to gain access to the
>> account at domaindiscover aka tierra.net, and we fiddled with things.
>>
>> How's it looking now?  (5:07pm pacific today will be approx 1hr after
>> the settings were chaged, FYI)
>>
>> -bill!
>>
>> On Mon, Mar 16, 2015 at 11:56:21PM -0700, Wes Hardaker wrote:
>>> Bill Kendrick  writes:
>>>
 On Mon, Feb 23, 2015 at 11:24:10AM -0800, Rod Roark wrote:
> On 02/23/2015 11:20 AM, Brian E. Lavender wrote:
>> Hey, so word is that some can't send email to the lugod lists because the
>> mailserver the MX record is a CNAME rather than an A record?
>>
>> brian
>
> Dunno who's administering the lugod.org domain, but whoever that is
> should be able to fix it.

 That'd be me.  Thx for looking into it folks, I'll try to figure
 it out next time I'm on my home laptop (which has all the creds
 to get into things).
>>>
>>> Hiya.  DNS geek here.  Things are still technically incorrect as
>>> currently deployed.  You aren't supposed to have a name after a service
>>> referral (in this case an MX) that is itself a CNAME referral.
>>>
>>> This is fine:
>>>
>>>   # dig lugod.org mx
>>>
>>>   ;; ANSWER SECTION:
>>>   lugod.org.  3600IN  MX  10 www.lugod.org.
>>>
>>> This is not:
>>>
>>>   # dig www.lugod.org.
>>>
>>>   ;; ANSWER SECTION:
>>>   www.lugod.org.  3600IN  CNAME   lugod.org.
>>>   lugod.org.  3600IN  A   173.13.165.50
>>>
>>> *some* (most) DNS resolution software lets you get away with that, but
>>> it's not legal according to the DNS RFCs and shouldn't be done.
>>>
>>>
>>> The right thing to do would be to replace the MX record so it looked
>>> like this:
>>>
>>>   lugod.org.  3600IN  MX  10 lugod.org.
>>>
>>> Which would then work.  Though, the best thing to do is actually create
>>> a new host record:
>>>
>>>   lugod.org.  3600IN  MX  10 mail.lugod.org.
>>>   mail.lugod.org. 3600IN  A   173.13.165.50
>>>
>>> :-)
>>> -- 
>>> Wes Hardaker 
>>> My Pictures:   http://capturedonearth.com/
>>> My Thoughts:   http://pontifications.hardakers.net/
>>> ___
>>> vox-tech mailing list
>>> vox-tech@lists.lugod.org
>>> http://lists.lugod.org/mailman/listinfo/vox-tech
>>
>> -- 
>> -bill!
>> Sent from my computer
>> ___
>> vox-tech mailing list
>> vox-tech@lists.lugod.org
>> http://lists.lugod.org/mailman/listinfo/vox-tech
> 

___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] some people can't send to list

2015-03-21 Thread Rick Moen
Quoting Bill Kendrick (n...@sonic.net):

> Brian came over, I did the song & dance to gain access to the
> account at domaindiscover aka tierra.net, and we fiddled with things.
> 
> How's it looking now?

Would you consider posting the new zonefile so it can be seen in its
entirety?  Understandably, the authoritative nameservers don't permit
random members of the public to pull those down.

$ dig -t axfr lugod.org @NS1.TIERRA.NET
; Transfer failed.
$ dig -t axfr lugod.org @NS2.TIERRA.NET
; Transfer failed.
$

One fine point:  RFC 2182's recommendation is minimum three, maximum
seven authoritative nameservers.  Two is disrecommended as too thin.

The choice of two only might be dictated by your chosen hosting
provider, which doesn't make this error any smarter, but does make it
more difficult to overcome.  (Shortchanging redundancy is sadly common
among ISPs.)

Personally, I use mutual nameservice with other technical people -- and
I do follow my own advice, too:

$ whois linuxmafia.com | grep '^Name Server: ' | wc -l
5
$


___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] some people can't send to list

2015-03-21 Thread Brian E. Lavender
Echo!

On Sat, Mar 21, 2015 at 04:58:33PM -0700, Bill Kendrick wrote:
> 
> Brian came over, I did the song & dance to gain access to the
> account at domaindiscover aka tierra.net, and we fiddled with things.
> 
> How's it looking now?  (5:07pm pacific today will be approx 1hr after
> the settings were chaged, FYI)
> 
> -bill!
> 
> On Mon, Mar 16, 2015 at 11:56:21PM -0700, Wes Hardaker wrote:
> > Bill Kendrick  writes:
> > 
> > > On Mon, Feb 23, 2015 at 11:24:10AM -0800, Rod Roark wrote:
> > >> On 02/23/2015 11:20 AM, Brian E. Lavender wrote:
> > >> > Hey, so word is that some can't send email to the lugod lists because 
> > >> > the
> > >> > mailserver the MX record is a CNAME rather than an A record?
> > >> >
> > >> > brian
> > >>
> > >> Dunno who's administering the lugod.org domain, but whoever that is
> > >> should be able to fix it.
> > >
> > > That'd be me.  Thx for looking into it folks, I'll try to figure
> > > it out next time I'm on my home laptop (which has all the creds
> > > to get into things).
> > 
> > Hiya.  DNS geek here.  Things are still technically incorrect as
> > currently deployed.  You aren't supposed to have a name after a service
> > referral (in this case an MX) that is itself a CNAME referral.
> > 
> > This is fine:
> > 
> >   # dig lugod.org mx
> > 
> >   ;; ANSWER SECTION:
> >   lugod.org.  3600IN  MX  10 www.lugod.org.
> > 
> > This is not:
> > 
> >   # dig www.lugod.org.
> > 
> >   ;; ANSWER SECTION:
> >   www.lugod.org.  3600IN  CNAME   lugod.org.
> >   lugod.org.  3600IN  A   173.13.165.50
> > 
> > *some* (most) DNS resolution software lets you get away with that, but
> > it's not legal according to the DNS RFCs and shouldn't be done.
> > 
> > 
> > The right thing to do would be to replace the MX record so it looked
> > like this:
> > 
> >   lugod.org.  3600IN  MX  10 lugod.org.
> > 
> > Which would then work.  Though, the best thing to do is actually create
> > a new host record:
> > 
> >   lugod.org.  3600IN  MX  10 mail.lugod.org.
> >   mail.lugod.org. 3600IN  A   173.13.165.50
> > 
> > :-)
> > -- 
> > Wes Hardaker 
> > My Pictures:   http://capturedonearth.com/
> > My Thoughts:   http://pontifications.hardakers.net/
> > ___
> > vox-tech mailing list
> > vox-tech@lists.lugod.org
> > http://lists.lugod.org/mailman/listinfo/vox-tech
> 
> -- 
> -bill!
> Sent from my computer
> ___
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech

-- 
Brian Lavender
http://www.brie.com/brian/

"There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the other
way is to make it so complicated that there are no obvious deficiencies."

Professor C. A. R. Hoare
The 1980 Turing award lecture
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] some people can't send to list

2015-03-21 Thread Bill Kendrick

Brian came over, I did the song & dance to gain access to the
account at domaindiscover aka tierra.net, and we fiddled with things.

How's it looking now?  (5:07pm pacific today will be approx 1hr after
the settings were chaged, FYI)

-bill!

On Mon, Mar 16, 2015 at 11:56:21PM -0700, Wes Hardaker wrote:
> Bill Kendrick  writes:
> 
> > On Mon, Feb 23, 2015 at 11:24:10AM -0800, Rod Roark wrote:
> >> On 02/23/2015 11:20 AM, Brian E. Lavender wrote:
> >> > Hey, so word is that some can't send email to the lugod lists because the
> >> > mailserver the MX record is a CNAME rather than an A record?
> >> >
> >> > brian
> >>
> >> Dunno who's administering the lugod.org domain, but whoever that is
> >> should be able to fix it.
> >
> > That'd be me.  Thx for looking into it folks, I'll try to figure
> > it out next time I'm on my home laptop (which has all the creds
> > to get into things).
> 
> Hiya.  DNS geek here.  Things are still technically incorrect as
> currently deployed.  You aren't supposed to have a name after a service
> referral (in this case an MX) that is itself a CNAME referral.
> 
> This is fine:
> 
>   # dig lugod.org mx
> 
>   ;; ANSWER SECTION:
>   lugod.org.  3600IN  MX  10 www.lugod.org.
> 
> This is not:
> 
>   # dig www.lugod.org.
> 
>   ;; ANSWER SECTION:
>   www.lugod.org.  3600IN  CNAME   lugod.org.
>   lugod.org.  3600IN  A   173.13.165.50
> 
> *some* (most) DNS resolution software lets you get away with that, but
> it's not legal according to the DNS RFCs and shouldn't be done.
> 
> 
> The right thing to do would be to replace the MX record so it looked
> like this:
> 
>   lugod.org.  3600IN  MX  10 lugod.org.
> 
> Which would then work.  Though, the best thing to do is actually create
> a new host record:
> 
>   lugod.org.  3600IN  MX  10 mail.lugod.org.
>   mail.lugod.org. 3600IN  A   173.13.165.50
> 
> :-)
> -- 
> Wes Hardaker 
> My Pictures:   http://capturedonearth.com/
> My Thoughts:   http://pontifications.hardakers.net/
> ___
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech

-- 
-bill!
Sent from my computer
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech