Re: high volume from outside our networks question

On 1 February 2013 18:42, John Wobus wrote: > On a secondary, the zone files in different views, even if identical, need > to be > distinct. > > Also, if you're allowing dynamical updating and the views need to serve > identical > versions of the zone, then you need to arrange things so the zone i

Re: high volume from outside our networks question

You can create 2 views "authorised" and "everyone else" which both reference the same domain zone files so you dont need to duplicate the zones. On a secondary, the zone files in different views, even if identical, need to be distinct. Also, if you're allowing dynamical updating and the view

Re: high volume from outside our networks question

As we've already pointed out it is something in the way your system is configured (you're doing everything in global options instead of using views to separate the different "classes" of users) and that you are running both authoritative and caching functions on the same server. You can create 2 v

Re: high volume from outside our networks question

The spoofed ip's are coming from the outside world as real legitimate IP's. They are not coming internally and then heading outwards. We have to allow port 53 traffic from the internet because we publish a dozen domains or so, and also cache for our customers. The question is why does the server re

Re: high volume from outside our networks question

You should be complying with BCP 38 [http://tools.ietf.org/html/bcp38] for Inbound Network Filtering which will reduce a lot of unwanted packets getting into your network. Our inbound (Cisco) ACL looks like the following and I check up on the bogon addresses [http://www.team-cymru.org/Services/Bog