evilghost
Premium
join:2003-11-22
Springville, AL
1 edit | Update the rule?
If the issue is caused by DNS source-port randomization why not simply create a rule to allow egress UDP with SRC PORT 'any' to UDP dport 53, or is ZA so luser friendly that this cannot be done? |
|
DataDoc
My avatar looks like me, if I was 2D.
Premium
join:2000-05-14
Greenville, NC | 95% of users don't know what you just said. |
|
ebubman
join:2002-01-17
Enola, PA
 ·Comcast
 ·Vonage
| said by DataDoc  :95% of users don't know what you just said. LOL. agree. have been a computer user since way back in the days of the prototypical ibm pc xt & at & i don't have a clue what he/she said.......bub |
|
XBL2009
------
join:2001-01-03
Chicago, IL
 ·AT&T Midwest
| reply to evilghost
said by evilghost :If the issue is caused by DNS source-port randomization why not simply create a rule to allow egress UDP with SRC PORT 'any' to UDP dport 53, or is ZA so luser friendly that this cannot be done? That can be done quite easily. |
|
caffeinator
Coming soon to a cup near you..
Premium
join:2005-01-16
Spokane, WA
·WebBand
2 edits | reply to evilghost
Yup, I've had that nearly that same rule for my 8signs for a long time now. Both Windows (XPpro, win2k) boxes use it, and the rest are Linux and don't need it. 
I updated using the MS patch, and thanks to 8signs and some common sense..everything is just peachy.
I liked ZA back in v. 2.6 I think it was..then I learned how to use rules-based FW's and never looked back.
Simple is good. |
|
