Unexpected behaviour from the B root servers? Am I setup wrong?
Stephen John Smoogen
smooge at gmail.com
Sun Feb 25 19:49:44 UTC 2007
I am only seeing this with the B systems at the moment.. and I am
trying to figure out how I should 'fix' my firewall or backbone DNS
server to deal with it.
Our campus DNS servers will 'proxy' a request to the backbone DNS
servers and when it talks to the B servers, we get requests back from
different IP address from what we sent to (thus our firewall drops it
as a bad session).
188.8.131.52.32768 > 184.108.40.206.domain
220.127.116.11.domain > 18.104.22.168.32768
22.214.171.124.domain > 126.96.36.199.32768
188.8.131.52.domain > 184.108.40.206.32768
This really picked up on Saturday when pretty much every send to the
220.127.116.11 server got 1 to 2 other returns from b1.ip4.int,
The only other servers that the firewall seems to be dropping are some
'questionable' ones in Romania that showed up over the weekend.
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"
More information about the bind-users