RE: RE: [EXT] Fwd: Re: problems sending to prodigy.net hosted email

2018-03-21 Thread Keith Medcalf
to Heaven says a lot about anticipated traffic volume. >-Original Message- >From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Stephen >Satchell >Sent: Tuesday, 20 March, 2018 19:39 >To: nanog@nanog.org >Subject: Fwd: RE: [EXT] Fwd: Re: problems sending to prodigy

Fwd: RE: [EXT] Fwd: Re: problems sending to prodigy.net hosted email

2018-03-20 Thread Stephen Satchell
ver farm. We had some, er, "interesting" denial of service attacks that didn't do as much damage as they could have. Forwarded Message Subject: RE: [EXT] Fwd: Re: problems sending to prodigy.net hosted email Date: Tue, 20 Mar 2018 17:15:25 + From: Charles Bronson

Managing ARP traffic [ was Re: [EXT] Fwd: Re: problems sending to prodigy.net hosted email ]

2018-03-20 Thread Hugo Slabbert
On Tue 2018-Mar-20 17:15:25 +, Charles Bronson wrote: If this isn't pertinent to the list, feel free to answer privately. How did you implement the server that got rid of ARP storms? Perhaps something like an ARP sponge?

RE: [EXT] Fwd: Re: problems sending to prodigy.net hosted email

2018-03-20 Thread Charles Bronson
To: nanog@nanog.org Subject: [EXT] Fwd: Re: problems sending to prodigy.net hosted email Two DNS servers hosted on one box (or VM object), even with two addresses, is easily compromised by DDoS amplification attacks. That's the norm for a number of "web control panel" systems like Plesk

Fwd: Re: problems sending to prodigy.net hosted email

2018-03-19 Thread Stephen Satchell
ot rid of ARP storms in our network by putting up a little server called "ackbar", that was configured to respond to all otherwise unused IP address in our pool. (Edge routers were Cisco 7000 class, with DS3 uplinks.) Lessons learned well. Forwarded Message ---- Subject: Re: p

Re: problems sending to prodigy.net hosted email

2018-03-19 Thread Stephen Satchell
On 03/17/2018 02:04 PM, Chris wrote: Stephen Satchell wrote: (I know in my consulting practice I strongly discourage having ANY other significant services on DNS servers. RADIUS and DHCP, ok, but not mail or web. For CPanel and PLESK web boxes, have the NS records point to a pair of

Re: problems sending to prodigy.net hosted email

2018-03-19 Thread Chris
On Mon, 19 Mar 2018 11:56:16 -0400 (EDT) C. Jon Larsen wrote: > > Why not? Never had a problem with multiple services on linux, in > > contrast to windows where every service requires its own box (or at > > least vm). > > Go for it ! Failure is an awesome teacher :) Don't really see a

Re: problems sending to prodigy.net hosted email

2018-03-19 Thread C. Jon Larsen
On Sun, 11 Mar 2018 15:57:32 -0700 Stephen Satchell wrote: (I know in my consulting practice I strongly discourage having ANY other significant services on DNS servers. RADIUS and DHCP, ok, but not mail or web. For CPanel and PLESK web boxes, have the NS records point to a pair of

Re: problems sending to prodigy.net hosted email

2018-03-19 Thread Chris
On Sun, 11 Mar 2018 15:57:32 -0700 Stephen Satchell wrote: > (I know in my consulting practice I strongly discourage having ANY > other significant services on DNS servers. RADIUS and DHCP, ok, but > not mail or web. For CPanel and PLESK web boxes, have the NS records > point to a pair of

Re: problems sending to prodigy.net hosted email

2018-03-11 Thread Stephen Satchell
On 03/09/2018 01:23 PM, Trey Nolen wrote: We are having issues with domains hosted on prodigy.net email servers including att.net, bellsouth.net, and scbglobal.net. We are being rejected for bad reverse DNS, but DNS is setup correctly. The error we are receiving is: Remote host said: 550 5.7.1

problems sending to prodigy.net hosted email

2018-03-11 Thread Trey Nolen
We are having issues with domains hosted on prodigy.net email servers including att.net, bellsouth.net, and scbglobal.net. We are being rejected for bad reverse DNS, but DNS is setup correctly.  The error we are receiving is: Remote host said: 550 5.7.1 Connections not accepted from servers