IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New That's interesting.
Some resolvers won't switch to TCP if the host in the DNS isn't answering UDP. My work proxy doesn't do that, for starters.

I've got some knob sending spoofed UDP "NS? ." queries (part of a DDoS attack on someone else, as far as I can tell) and although I'm throwing them away at the first point of filtering, he won't stop sending the,. So I wondered if he'd give up if I turned off DNS UDP forwarding. If my domain name appears to have "gone away" today, that's why.

Wade.


Q:Is it proper to eat cheeseburgers with your fingers?
A:No, the fingers should be eaten separately.
New out of spec?
dns via tcp is for addesses larger than udp packets so all conversations should start at udp then switch to tcp if too long
New Quite possibly.
Though I don't recall the RFC saying attempting DNS via UDP first is mandatory or recommended and couldn't be bothered to go look. :-) But I admit to being curious as to how accomodating resolvers might be on that point, which is why I changed it.

Wade.

Q:Is it proper to eat cheeseburgers with your fingers?
A:No, the fingers should be eaten separately.
New TCP is also for AXFR
Without it... even though AXFR *CAN* work over UDP, the initiation requires TCP.
     That's interesting. - (static) - (3)
         out of spec? - (boxley) - (2)
             Quite possibly. - (static)
             TCP is also for AXFR - (folkert)

Several ICLRPDs in there, but I'll let others pick out their favorites.
58 ms