On 9/27/2010 8:48 PM, donovan jeffrey j wrote:
I run a number of internal clients on 10 address space. what i did was break up
each Zone into Class B's 10.1.x.x , 10.2.x.x then my forward and reverse files
into class C's. Each record 10.1.1.x . 10.1.2.x, 10.1.3.x, . then scale ass
needed.
Hi all.
I am setting up a new appliance-based DNS solution that will contain a fair
number of separately managed Windows DNS slave servers (in addition to the
DNS appliances that will handle the .
Currently there are just over 8000 host records that resolve to IP's in the
10.x.x.x space. I am
On Sep 27, 2010, at 1:03 PM, Christopher Cain wrote:
Hi all.
I am setting up a new appliance-based DNS solution that will contain a fair
number of separately managed Windows DNS slave servers (in addition to the
DNS appliances that will handle the .
Currently there are just over 8000
While a single zone is perfectly fine from a standards point of view,
some clients might be served addresses they don't like 10.x.x.0 and
10.x.x.255.
Just a reminder that this could be a reason if something appears weird.
On 27/09/10 23:07, Chris Buxton wrote:
On Sep 27, 2010, at 1:03 PM,
On Sep 27, 2010, at 6:55 PM, Sten Carlsen wrote:
While a single zone is perfectly fine from a standards point of view, some
clients might be served addresses they don't like 10.x.x.0 and 10.x.x.255.
But that would be DHCP config, no?
Just a reminder that this could be a reason if
On Sep 27, 2010, at 3:55 PM, Sten Carlsen wrote:
While a single zone is perfectly fine from a standards point of view, some
clients might be served addresses they don't like 10.x.x.0 and 10.x.x.255.
Just a reminder that this could be a reason if something appears weird.
Don't confuse
On Sep 27, 2010, at 4:43 PM, Sten Carlsen wrote:
Well, it depends on your clients. If they don't like .0 or .255, you would
have to have a rather large amount of ranges.
E.g. range 10.1.1.1 10.1.1.254; range 10.1.2.1 10.1.2.254; ..
If OTOH you don't have any of those clients, other
On Sep 27, 2010, at 4:03 PM, Christopher Cain wrote:
Hi all.
I am setting up a new appliance-based DNS solution that will contain a fair
number of separately managed Windows DNS slave servers (in addition to the
DNS appliances that will handle the .
Currently there are just over 8000
On 28/09/10 2:08, Chris Buxton wrote:
On Sep 27, 2010, at 4:43 PM, Sten Carlsen wrote:
Well, it depends on your clients. If they don't like .0 or .255, you
would have to have a rather large amount of ranges.
E.g. range 10.1.1.1 10.1.1.254; range 10.1.2.1 10.1.2.254; ..
If OTOH you
9 matches
Mail list logo
