Re: problems sending to prodigy.net hosted email

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: TWC/Charter/Spectrum contact off-list ? (Reverse DNS issue)

On Thu, Oct 19, 2017 at 08:04:12AM -0400, Brandon Applegate wrote: > I had success with this issue about 2 years ago when some TWC folks > contacted me. I don’t know if those folks are still with TWC/Charter > here in the end of 2017 - hence posting on NANOG. The tl;dr is IPv6 > reverse DNS

Re: problems sending to prodigy.net hosted email

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: Spiffy Netflow tools?

+1 for Plixer Scrutinizer 2018-03-17 19:42 GMT-03:00 Michael Krygeris : > Disclaimer: Am Plixer engineer. > If you want to take it for a spin, you can download a fully functional > OVA/QCOW2 30 day eval from the plixer website. I can also get you access to > an AWS AMI as

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 and CPanel. It depends on the scale of your operations. Last time I was in that situation, I

Re: problems sending to prodigy.net hosted email

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: Juniper MX - Routed pseudowire using LDP - VPWS or VPLS

I want to thank everyone who contacted me on and off list on this request. I now have two methods to land a layer 3 endpoint on a layer 2 circuit to a remote PE. I very much appreciate the input, feedback, and assistance. I hope I personally get to meet all of you that reached out to me at a

Re: Juniper MX - Routed pseudowire using LDP - VPWS or VPLS

The other solution is a stitched LT configuration. One LT is the L3 endpoint, the other is the PW endpoint. You use VPWS with this one. I suppose you might be able to do VPLS instead if you wanted to. I am running eBGP on this circuit too. It's a bit more complicated for troubleshooting. I'm

Re: Juniper MX - Routed pseudowire using LDP - VPWS or VPLS

Absolutely! I'm running a eBGP session over this ATM. We are going to try to backhaul our customers through a Dell whitebox running IPI OcNOS configured with an 'LDP fabric' to a core MX. To use an IRB as a L3 endpoint you have to use VPLS on the MX (Junos version 15.1R6.7). I was missing a

Re: Juniper MX - Routed pseudowire using LDP - VPWS or VPLS

Would you mind sharing the solution(s)? I've stiched a L2 PW using lt-interfaces. Thanks. On Mon, Mar 19, 2018 at 11:51:36AM -0500, Ben Bartsch wrote: > I want to thank everyone who contacted me on and off list on this request. > I now have two methods to land a layer 3 endpoint on a layer 2

Re: problems sending to prodigy.net hosted email

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