I've been doing the suggestion below for many years using the IP
addresses that Cogent gives us. All I needed to do is get LOA from them
and submit it to my backup ISP. I've never had an issue with my Cogent
IP's *not* being advertised by my other ISP and I really don't think
there is very muc
Am 04.03.2014 05:19, schrieb William Herrin:
> Reasons why dynamic DNS fails to perform as expected include:
>
> * Web browser DNS pinning can result in a customer's web browser
> holding the old IP address indefinitely.
>
> * Host-level caching of looked up names which discards the TTL.
> Remembe
Have them look at radware linkproof which is designed for small shops that
don't want to do bgp and getting their own ASN and pi address space. Been
around since 1999.
http://www.radware.com/Products/LinkProof/
Hank
On Mar 4, 2014 3:11 AM, Eric A Louie wrote:
>
> This may sound like dumb que
On Mon, 3 Mar 2014, Justin M. Streiner wrote:
If they're not technically competent enough to handle BGP, they won't be
technically competent enough to deal with solutions that play the short DNS
TTL game.
As someone else mentioned in this thread - would colocating the servers be a
workable s
On 3/3/14, 7:20 PM, Randy Carpenter wrote:
> Is there some technical reason that BGP is not an option? You could allow
> them to announce their AT&T space via you as a secondary.
With the risk of starting holy war on how BGP works on dialup and that
providers should permit such, the OP has not s
On Mon, 3 Mar 2014, Eric A Louie wrote:
Honestly? Because the end-customers are not technically competent
enough to run dual-homed BGP, and we don't want to be their managed
service providers on the IT side. And announcing the AT&T space is fine
until something goes wrong, and I have to trou
"
> Sent: Monday, March 3, 2014 11:49:21 PM
> Subject: Re: ISP inbound failover without BGP
>
> Honestly? Because the end-customers are not technically competent enough to
> run dual-homed BGP, and we don't want to be their managed service providers
> on the IT side.
On Mon, 3 Mar 2014, Eric A Louie wrote:
Are there any other solutions, short of using BGP multihoming and
having them try to get their own ASN and IPv4 /24 block?
For what it sounds like the customer wants to do, this really is the right
solution. Most everything else has some level of 'ugly
> From: Randy Carpenter
>To: Eric A Louie
>Cc: NANOG
>Sent: Monday, March 3, 2014 7:20 PM
>Subject: Re: ISP inbound failover without BGP
>
>
>
>Is there some technical reason that BGP is not an option? You could allow them
>to announce their AT&T space vi
> Depending on their business=2C using dynamic DNS providers could be a reall=
> y bad idea. If they deal only with home users who won't even know=2C it'll =
> probably work. If their customers are security-aware businesses=2C they pro=
> bably block all sites hosted with dynamic DNS systems.
Whe
On Mon, Mar 3, 2014 at 7:20 PM, Randy Carpenter wrote:
> Is there some technical reason that BGP is not an option? You could allow
> them to announce their AT&T space via you as a secondary.
unless it is a /26, /25 or something shorter.
Even with a /24 things may get messy.
IPv4 is coming to a
On Mon, Mar 3, 2014 at 8:11 PM, Eric A Louie wrote:
> One thought I had was having them use Dynamic DNS service.
>
> Are there any other solutions, short of using BGP multihoming
> and having them try to get their own ASN and IPv4 /24 block?
Hi Eric,
I went through this a couple years ago with c
That's a good point Ray - thank you.
>
> From: Ray
>To: Matthew Crocker ; Eric A Louie
>
>Cc: NANOG
>Sent: Monday, March 3, 2014 6:31 PM
>Subject: RE: ISP inbound failover without BGP
>
>
>
>
>Depending on their bu
Is there some technical reason that BGP is not an option? You could allow them
to announce their AT&T space via you as a secondary.
-Randy
- Original Message -
> This may sound like dumb question, but... I'm used to asking those.
>
> Here's the scenario
>
> Another ISP, say AT&T, is t
; Subject: Re: ISP inbound failover without BGP
> From: matt...@corp.crocker.com
> Date: Mon, 3 Mar 2014 20:50:26 -0500
> To: elo...@yahoo.com
> CC: nanog@nanog.org
>
>
>
> Depends on the application,
>
> SIP, VPN, SMTP, etc just setup both IPs and let the en
Depends on the application,
SIP, VPN, SMTP, etc just setup both IPs and let the end-user application figure
it out (SIP-UA register to both IPs for example)
HTTP/HTTPS setup a proxy server in a colo that is multi-homed to frontend the
requests. Then it can load balance traffic over both IPs
> This may sound like dumb question, but... I'm used to asking those.=0A=0AHe=
> re's the scenario=0A=0AAnother ISP, say AT&T, is the primary ISP for a cust=
> omer.=0A=0ACustomer has publicly accessible servers in their office, using =
> the AT&T address space.=0A=0AI am the customer's secondary I
17 matches
Mail list logo
