On Fri, 3 Apr 2009, Charles Wyble wrote:
This is probably a good time to remind the uninitiated to have some
secondary DNS with a totally separate company if your DNS is that
important to you.
Preferably with a provider that announces out of multiple ASN :)
ATT and Akami both provide good
On Sat, Apr 4, 2009 at 2:05 PM, Peter Beckman beck...@angryox.com wrote:
On Fri, 3 Apr 2009, Charles Wyble wrote:
This is probably a good time to remind the uninitiated to have some
secondary DNS with a totally separate company if your DNS is that
important to you.
Preferably with a
* Peter Beckman:
I can highly recommend DNSmadeEasy.com. Inexpensive, Anycasted, always
fast and reliable. Good for primary and/or secondary, IMO, though it is
sage advice to use two different providers if you are super ultra serious
about never being down.
Or put some of your DNS
IMHO, fate-sharing as a strategy for increasing availability is
somewhat underrated.
from rfc 2182
3.3. A Myth Exploded
An argument is occasionally made that there is no need for the domain
name servers for a domain to be accessible if the hosts in the domain
are unreachable. This
* Randy Bush:
IMHO, fate-sharing as a strategy for increasing availability is
somewhat underrated.
from rfc 2182
Randy, I didn't write, don't keep off-site name servers. I wrote,
keep on-site name servers, even if you pay for off-site name
service.
3.3. A Myth Exploded
+ While
But looking back at incidents such as the Zonelabs/Abovenet issue,
your advice is correct for the network we have today.
as that rfc is over a decade old, i am not optimistic that change is
neigh sigh.
and it is amusing to see
;; ANSWER SECTION:
harvard.edu.10794 IN NS
* Randy Bush:
But looking back at incidents such as the Zonelabs/Abovenet issue,
your advice is correct for the network we have today.
as that rfc is over a decade old, i am not optimistic that change is
neigh sigh.
DNSSEC obscures quite a few failures which can hit secondaries. I
think it
For anyone trying to troubleshoot any strange resolution or page loading
issues, Register.com is apparently having a massive DNS hosting outage
that has been going on since 2 days ago, and is still continuing. I
only found out because our monitoring was complaining about one single
domain on and
Yep, we're seeing issues with mail delivery to any domain that has
their zone hosted by register.com. You can follow the action on
twitter:
http://search.twitter.com/search?q=register.com
Various reports that some of the register.com support staff is denying
issues, while others aren't, while
mailto:jeichm...@billtrust.com
From: Dennis Burgess - LTI [mailto:dmburg...@linktechs.net]
Sent: Friday, April 03, 2009 3:39 PM
To: Jeffrey Negro
Subject: Re: Register.com DNS hosting issues
Thanks for the update :) Guess they did not get a ETA time
-Original Message-
From: Jeffrey Negro [mailto:jne...@billtrust.com]
Sent: Friday, April 03, 2009 3:42 PM
To: Dennis Burgess - LTI
Cc: nanog@nanog.org
Subject: RE: Register.com DNS hosting issues
No ETA given to me, just the stock line of We apologize.. blah blah...
as soon as possible
Communications
-Original Message-
From: Jeffrey Negro [mailto:jne...@billtrust.com]
Sent: Friday, April 03, 2009 3:42 PM
To: Dennis Burgess - LTI
Cc: nanog@nanog.org
Subject: RE: Register.com DNS hosting issues
No ETA given to me, just the stock line of We apologize.. blah blah...
as soon
Jeffrey Negro wrote:
No ETA given to me, just the stock line of We apologize.. blah blah...
as soon as possible.. blah blah.
Do you normally give an ETA concerning DOS issues?
Jack
-Original Message-
From: Jack Bates [mailto:jba...@brightok.net]
Sent: Friday, April 03, 2009 3:52 PM
To: Jeffrey Negro
Cc: Dennis Burgess - LTI; nanog@nanog.org
Subject: Re: Register.com DNS hosting issues
Jeffrey Negro wrote:
No ETA given to me, just the stock line of We apologize.. blah
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 3, 2009 at 12:52 PM, Clinton Popovich crpop...@nauticom.net
wrote:
Looks like a routing issue to their DNS servers from here.
traceroute to DNS020.C.REGISTER.COM (216.21.235.20), 64 hops max, 40 byte
packets
1 c28.134.nauticom.net
Jeffrey Negro wrote:
No ETA given to me, just the stock line of We apologize.. blah blah...
as soon as possible.. blah blah.
This is probably a good time to remind the uninitiated to have some
secondary DNS with a totally separate company if your DNS is that
important to you.
~Seth
Subject: Re: Register.com DNS hosting issues
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 3, 2009 at 12:52 PM, Clinton Popovich crpop...@nauticom.net
wrote:
Looks like a routing issue to their DNS servers from here.
traceroute to DNS020.C.REGISTER.COM (216.21.235.20), 64 hops max, 40
Looks like we're seeing DNS queries succeeding again. Hopefully this
time they'll stay up. :)
-matt
On Fri, Apr 3, 2009 at 1:10 PM, Paul Ferguson fergdawgs...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 3, 2009 at 12:52 PM, Clinton Popovich
Seth Mattinen wrote:
Jeffrey Negro wrote:
No ETA given to me, just the stock line of We apologize.. blah blah...
as soon as possible.. blah blah.
This is probably a good time to remind the uninitiated to have some
secondary DNS with a totally separate company if your DNS is that
important
On Fri, Apr 03, 2009 at 01:31:33PM -0700, Charles Wyble wrote:
Seth Mattinen wrote:
Jeffrey Negro wrote:
No ETA given to me, just the stock line of We apologize.. blah blah...
as soon as possible.. blah blah.
This is probably a good time to remind the uninitiated to have some
secondary
This is probably a good time to remind the uninitiated to have some
secondary DNS with a totally separate company if your DNS is that
important to you.
someone should write an rfc on that
randy
someone should write an rfc on that
why not read the one you wrote, it's just 12 years old
cheers
jorge
On Fri, 3 Apr 2009 17:38:43 -0500
Jorge Amodio jmamo...@gmail.com wrote:
someone should write an rfc on that
why not read the one you wrote, it's just 12 years old
We don't read. Very few system developers are familiar with
work done outside of their own project.
23 matches
Mail list logo
