Luke Parrish wrote:
Not quite looking for tips to manage my network and ACL's or if should
or should not be blocking, more looking for actual ports that other
ISP's are blocking and why.
For example:
port 5 worm 2.5
port 67 virus 8.2
www.dshield.org, www.mynetwatchman.org ?
/mjt
Noticied today. All Verisign's GTLD servers broke
EDNS0 (RFC2671). Here's how it looks like:
query:
$ dnsget -t mx -vv microsoft.net. -n 192.5.6.30
;; trying microsoft.net.
;; sending 42 bytes query to 192.5.6.30 port 53
;; -HEADER- opcode: QUERY, status: NOERROR, id: 64471, size: 42
;;
Mark Andrews wrote:
In article [EMAIL PROTECTED] you write:
Noticied today. All Verisign's GTLD servers broke
EDNS0 (RFC2671). Here's how it looks like:
[]
;; received 12 bytes response from 192.5.6.30 port 53
;; unexpected number of entries in QUERY section: 0
;; -HEADER- opcode: QUERY,
Florian Weimer wrote:
* Michael Tokarev:
Well ok, I know it's kinda expected -- i don't understand what you're
asking for, can't even repeat your question. But the next question
is -- *why*?
EDNS0 can be easily abused for traffic amplication purposes. 8-(
Root and TLD nameservers rarely
Just noticied a weird behaviour of dns?.name-services.com nameservers.
Here it goes (there are several problems, pls read the whole this
message):
$ host -t a -v name-services.com. dns1.name-services.com.
this gives normal answer (details skipped):
name-services.com. 7200IN A
Michael Tokarev wrote:
Just noticied a weird behaviour of dns?.name-services.com nameservers.
Here it goes (there are several problems, pls read the whole this
message):
name-services.com. 3600IN SOA dns1.name-services.com.
info.name-services.com. 2002050701 10001 1801 604801
Big Wave Dave wrote:
I have seen a coupld different domains using their services be
similarly affected. Sending them an email would result in a bounce
marked domain not found. It has been periodically occurring since
The bounce/domain not found is exactly due to this problem with
returning
This may be somewhat off-topic here, but still..
Today at about 00:00 UTC, one of SORBS official
nameservers somehow got a corrupt datafile, and
started spreading incorrect information. The
problem had gone at next reload or next data
transfer (which was after about 20 minutes),
but some caches
Haesu wrote:
[]
Before I figure out this BIND thing, for now..
box02jp5-cr01.twdx.net# set routing-options static route 64.94.110.11/32 discard;
Please do no do that. You, or your users, will end up having
TONS of undeliverable bounces for forged/bogus domains sitting
in mail spools...
/mjt
Adam 'Starblazer' Romberg wrote:
Looks like they pulled it now.
[EMAIL PROTECTED]:/var/log$ host rarrarrarrarblah.com
rarrarrarrarblah.com does not exist (Authoritative answer)
Nah, just zone propagation issues. Some gtld servers still
have old zone data.
/mjt
10 matches
Mail list logo
