Re: DNS and Registrar

2019-06-29 Thread Peter Coghlan via cctalk
Seth Morabito wrote:
> On Fri, Jun 28, 2019, at 2:07 AM, Peter Coghlan via cctalk wrote:
> > [...] so my response is to filter out anything to do with Linode from
> > here.
>
> This is something of a touchy subject for me because I have been a Linode
> customer for over a decade, and have always been extraordinarily happy with
> their service.
>

It's going to get interesting for me too because the DNS registrar that is
looking after my domain name seems to be using them too and I am now having
difficulty reaching their website since I started filtering Linode.  This
is all going to come to a crunch when it is time to renew my domain name
registration in November.  I have tried to alert the registrar to the issues
I am having with Linode but I have received no response from them.  I only
changed to the current registrar last year after the previous one kept sending
me spam and ignored my complaints about it...

>
> THAT SAID: I had to stop running my own mail server about two years ago,
> after the failure rate of delivery became too high. Part of that was
> because of Google, but I'm sure another good part was due to Linode IP
> addresses ending up on blacklists.
>

Speaking of which, I have noticed a correlation between a provider's use of
Google email infrastructure instead of their own email infrastructure to
accepts or reply to abuse reports (such as Linode does for example) and
said provider's attempts to avoid the consequences of dubious practices on
their part.

>
> It has been a very long time since I looked at the competition, but I'm
> very open to switching. Do you (or anyone else for that matter) have
> providers you would recommend?
>

Sorry, I don't have any ideas.  I expect the market is completely different
where you are to where I am, nearly a third of the world away.

>
> -Seth
> -- 
>   Seth Morabito
>   Poulsbo, WA
>   w...@loomcom.com
>

Regards,
Peter Coghlan.


Re: DNS and Registrar

2019-06-28 Thread Grant Taylor via cctalk

On 6/28/19 4:59 PM, Seth Morabito via cctalk wrote:
This is something of a touchy subject for me because I have been a Linode 
customer for over a decade, and have always been extraordinarily happy 
with their service.


I'm not sure how long I've been a Linode customer.  I think it's 
something like six to eight years.


I've also almost always been quite happy with their service (VPS and 
connectivity) and their customer service (hand holding when desired).  I 
say almost because I have had a couple of things that I was not happy 
with initially.  I say initially because they did realize they were 
dropping the ball and stepped up their game and made me happy.


THAT SAID: I had to stop running my own mail server about two years ago, 
after the failure rate of delivery became too high. Part of that was 
because of Google, but I'm sure another good part was due to Linode IP 
addresses ending up on blacklists.


I've heard less noise about Linode's IP space than I have other VPS 
providers.


I'm successfully delivering to Google from Linode daily.  Running an 
email server today is non-trivially more difficult than it was ten years 
ago.


It has been a very long time since I looked at the competition, but 
I'm very open to switching. Do you (or anyone else for that matter) 
have providers you would recommend?


I'm not aware of any /better/ options, just /other/ options.

Honestly, if I ever need to switch, I'll likely go back to a company 
that I do work with that has a Co-Lo facility and host something with them.




--
Grant. . . .
unix || die


Re: DNS and Registrar

2019-06-28 Thread Seth Morabito via cctalk
On Fri, Jun 28, 2019, at 2:07 AM, Peter Coghlan via cctalk wrote:
> [...] so my response is to filter out anything to do with Linode from
> here.

This is something of a touchy subject for me because I have been a Linode 
customer for over a decade, and have always been extraordinarily happy with 
their service.

THAT SAID: I had to stop running my own mail server about two years ago, after 
the failure rate of delivery became too high. Part of that was because of 
Google, but I'm sure another good part was due to Linode IP addresses ending up 
on blacklists.

It has been a very long time since I looked at the competition, but I'm very 
open to switching. Do you (or anyone else for that matter) have providers you 
would recommend?

> Regards,
> Peter Coghlan.

-Seth
-- 
  Seth Morabito
  Poulsbo, WA
  w...@loomcom.com


Re: DNS and Registrar

2019-06-28 Thread Grant Taylor via cctalk

On 6/28/19 2:46 AM, Peter Coghlan via cctalk wrote:
I have issues with customers of (or possibly "customers" of) Linode 
regularly probing my network.  On complaining to Linode, the response I 
get is more or less "oh they're entitled to do that".  Linode distributes 
the ip addresses responsible for this activity across various netblocks 
and moves them from time to time so my response is to filter out anything 
to do with Linode from here.


I think that all bargain VPS providers are subject to the same type of 
misuse ~> abuse.


It is of course your option to filter them.

I might not like it.  But it's your choice.



--
Grant. . . .
unix || die


Re: DNS and Registrar

2019-06-28 Thread Peter Coghlan via cctalk

Grant Taylor wrote:


That's why I have my master that I can do anything and everything I want 
to, and outsource to slave secondaries.  Linode, my VPS provider, has 
five different DNS servers that (I belie) are geographically diverse. 
It will be quite a bit harder to take out all five of their DNS servers. 
  Plus, I don't have to pay for connectivity in five different 
locations.  ;-)




I have issues with customers of (or possibly "customers" of) Linode regularly
probing my network.  On complaining to Linode, the response I get is more or
less "oh they're entitled to do that".  Linode distributes the ip addresses
responsible for this activity across various netblocks and moves them from
time to time so my response is to filter out anything to do with Linode from
here.

Regards,
Peter Coghlan.


Re: DNS and Registrar

2019-06-27 Thread Grant Taylor via cctalk

On 6/27/19 12:53 PM, jim stephens wrote:

They don't have to be combined.


Agreed.

I've been running DNS servers for about 20 years.  I /always/ prefer to 
run my own DNS servers if I can.


I have never run across a situation where I was unable to do so for 
/technical/ reasons.  I have had clients that /chose/ to /not/ host 
their own DNS for a /business/ reason.


I have a friend running his and my DNS on a server at his house with two 
DSL feeds for good measure, one is primary DNS for our domains, second 
one is published as the secondary.


*nod*

I'd worry about DSL circuits and stability for DNS.  But it will 
probably work > 98% of the time.  If you're comfortable with it, more 
power to you.


I would likely do something more like I'm doing now, run the master name 
server (MNAME field in the SOA record) on the DSL and have somebody else 
with a more robust connection (DSL had issues where I'm from) do a slave 
zone transfer and be the listed Name Servers (NS records) that the world 
talks to.


I actually do that now with my VPS being the MNAME server and my VPS 
provider doing slave zone transfers off of me.


Note how the registrar is not part of that mix.  ;-)

The biggest thing to watch for is the lax rules for transfering 
domains.  There was a problem with that, but most registrars allow locks 
now that impede the movement of domains w/o a bit of work.


That sounds like you're talking about moving domains between registrars, 
which is decidedly different than and independent of where DNS is hosted.


Admittedly the registrar has to point (delegate) to the DNS hosting 
provider.  But it's fairly easy to move domains between registrars 
without even logging into a portal at the DNS host.


Used to take a couple of emails to highjack a domain, as there wasn't 
even a notification to verify that the transfer process email was 
requested by the owner.


Ya.  Registrars have had some deficiencies over the years.  I think they 
are getting better.


You are strongly encouraged to use a third party "professional" DNS 
service, but it only really need to be up reliably.


~whistling~ … ~quiet~ … I'm sorry, did you say something?  No.  Never 
mind.  I'll go back to what I was doing.  …  ~whistling~


I mean that as a joke.  I let a LOT of what companies that are trying to 
sell to me go in one ear, sanity check it, and then go out the other ear.


I'm of the opinion that a static IP is the biggest requirement for 
/most/ DNS service.  I.e. somewhere to have the registrar delegate the 
DNS to.


Beyond that, I'm happy to delegate sub-domains to people on dynamic IPs 
if they want them.


It's possible to put DNS a LOT of places that don't qualify as "Best 
Practice".  Most of them will work most of the time.


We have the dual providers for the node my friend runs, as we know from 
the phone companies and providers that though the DNS is over the same 
12 pair wire into his house (another trick), the CO actually has the 
DNS switches on different racks and UPS's.  Which isn't a bad precaution.


That's probably okay for most things.  But it's still subject to Backhoe 
Bob and the fade that he can induce.


That's why I have my master that I can do anything and everything I want 
to, and outsource to slave secondaries.  Linode, my VPS provider, has 
five different DNS servers that (I belie) are geographically diverse. 
It will be quite a bit harder to take out all five of their DNS servers. 
 Plus, I don't have to pay for connectivity in five different 
locations.  ;-)


I'm curious, you said DSL.  But that could be anything from 1.5 Mbps 
ADSL to SDSL to VDSL.  Each of which have different capabilities and 
SLAs.  Other than the backhoe fade taking out both connections at the 
same time, higher quality DSL with SLAs is probably okay to do.


I think the official recommendation for big (think root level) DNS 
servers is to have each server in a different network, where network is 
defined as /24 (or larger), preferably under different ASNs.


But that's not a /requirement/, especially for smaller DNS operators.


thanks


You're welcome.



--
Grant. . . .
unix || die