Ladies and Gentlemen:
I have been conducting research looking for the economic
justification for MPLS. I have some feedback, but sound rationale from
the industry has eluded me thus far. I am looking for a paper, website,
etc that explains the benefits of implementing MPLS (other than
Ok -- I'm a dumbass. Sorry about this posting.
Next time I'll drink my coffee before trying to read web pages. *sigh*
--
Michael L. Barrow
E: [EMAIL PROTECTED]P: 805-566-0885
hi
I might be totally off the mark here, but has slapper now changed to port
1812? This'll make it really difficult to filter, if you're using this
port for RADIUS.
I'm seing huge volumes of traffic, to what seem to be slapper infected
hosts.
I see 2 infected hosts, with 2343 and 2384 unique
On Tue, 1 Oct 2002, fingers wrote:
hi
I might be totally off the mark here, but has slapper now changed to port
1812? This'll make it really difficult to filter, if you're using this
port for RADIUS.
We saw this yesterday, directed at a previously infected slapper.a
(2002/udp
Hi, NANOGers.
A range of ASNs have been allocated to ARIN as of September 2002. The
range is 26624 - 27647. You may wish to adjust your filters. The
definitive list can be found here:
http://www.iana.org/assignments/as-numbers
I have updated my bogus ASN monitoring to reflect these
Just to summarize the private replies I got about this feature.
One network showed moderate use. All of the rest showed very
limited use (count the customers using it on one hand or two). It
was suggested by a few people that only the largest customers tend
to use it, which may weigh in the
Hi, John.
] We seem to be getting name resolution errors when we query any
] of the root servers, and this just started a hour or so ago.
Everything looks OK here. I tried a few DNS traces and queries without
any errors.
http://www.cymru.com/DNS/dns.html
http://www.cymru.com/DNS/dnstext.html
On Tue, 1 Oct 2002, John Neiberger wrote:
We seem to be getting name resolution errors when we query any
of the root servers, and this just started a hour or so ago.
Anyone else noticing a problem?
http://f.root-servers.org/
The web status pages for the F root server shows traffic dropping
never mind, I didn't read the notes at the bottom of the page. The MRTG
graphs are no longer being updated.
Here is for L, F also seems to reply. Tested from 8 different
places on the net. OTW Transit splay on the test was 8 different
providers.
Can you give a sample of the errors you are seeing?
Got a sample DIG line ??
John Brown
Le Geek
%dig l.root-servers.net com ns
; DiG 8.3
Forgive me for being a DNS clunkhead. g I honestly don't
know much about it, but I thought I'd post this to the list
because it did appear to be a problem with the root servers,
which would be A Bad Thing (tm).
Probable dumb question: if I do an nslookup from a desktop
directed at a root
On Tue, 1 Oct 2002, Adam McKenna ([EMAIL PROTECTED])
wrote:
On Tue, Oct 01, 2002 at 07:46:00PM -0400, John Neiberger
wrote:
We're getting responses from the root servers, the names
just
aren't resolving. From a windows NT machine the error
is Non-
existent Domain.
John M. Brown wrote:
Root servers don't resolve names other than the TLD's.
Except when they do ;-)
[rjoffe@layer9 rjoffe]$ dig a.gtld-servers.net www.tombannenchev.com
; DiG 9.2.1 a.gtld-servers.net www.tombannenchev.com
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode:
On Tue, 01 Oct 2002 17:11:00 PDT, Rodney Joffe [EMAIL PROTECTED] said:
[rjoffe@layer9 rjoffe]$ dig @a.gtld-servers.net www.tombannenchev.com
Well... a.gtld-servers.net isn't a root server (got bit by that myself a
while ago ;) and even then...
tombannenchev.com. 172800 IN NS
Thanks to everyone who helped me out and I hope you don't mind
me making a fool of myself. :-) I (and others that I work
with) learned quite a lot from your responses to this little
incident. If I have to be a little bit foolish to learn
something valuable, then so be it! g
Thanks
We seem to be getting name resolution errors when we query any
of the root servers, and this just started a hour or so ago.
Anyone else noticing a problem?
John
On Tue, 2002-10-01 at 17:46, John Neiberger wrote:
We're getting responses from the root servers, the names just
aren't resolving. From a windows NT machine the error is Non-
existent Domain.
Ah, I just noticed something. The packet length for the DNS
response is supposed to be 510
Don't worry about being a DNS clunkhead. Though some on this list
will banish you for trying to learn.
The root servers are non-recursive. Otherwords they only
answer for what they know.
WHat you are asking for is a server to be recursive in its
answer to your query. This is what a ISPs
18 matches
Mail list logo
