Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Pubstro rash |
|---|---|
| Date: | Fri, 18 Mar 2005 09:30:51 -0600 |
I have never had a DNS query that had a response that was over 512 bytes. For that reason I disable all inbound DNS over 53/tcp. I have been using this configuration for years and even run my own DNS servers and have see absolutely no problems. -----Original Message----- From: Jeff Kell [mailto:jeff-kell@utc.edu] Sent: Thursday, March 17, 2005 6:07 PM To: alexandre.skyrme@ciphersec.com.br Cc: incidents@securityfocus.com; gillettdavid@fhda.edu Subject: Re: Pubstro rash Alexandre Skyrme wrote:
Greetings David, Just a thought about your third comment... As far as I'm concerned DNS just uses 53/TCP to do zone transfers. In
case
your workstations are on a different network than your DNS servers it
should
probably be safe to block incoming TCP connections to that network on
such
port. Tipically zone transfers would only be used by secondary servers to
update
their own zones from its primary server.
RFC1035 allows 512 bytes for a DNS response (53) but they may now be longer, according to RFC2671 and others. If the DNS query fails or is "truncated", the query may be repeated over TCP. So, 53/tcp is NOT just for zone transfers. Jeff
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Pubstro rash, David LeBlanc |
|---|---|
| Next by Date: | Netscreen 5XT SSH Traffic, Ben Blakely |
| Previous by Thread: | Re: Pubstro rash, Brian Eckman |
| Next by Thread: | Re: Pubstro rash, Jeff Kell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |