it is highly recommended you cruise the DNS rfcs and/or read the dns
bible.. these are problems solved 20 years ago
On 8/28/07, reje [EMAIL PROTECTED] wrote:
In the sense of expanding DNS infrastructure, your
comments seem sane enough (you definitely read that
DNS BIND book :-)
On the other
In the sense of expanding DNS infrastructure, your
comments seem sane enough (you definitely read that
DNS BIND book :-)
On the other side, I really need to introduce
_additional_ availability of DNS servers/resolvers.
This is especially true for resolvers as they are the
first layer users are
On 8/27/07, reje [EMAIL PROTECTED] wrote:
I'm wondering is there a way to scale DNS service
using OpenBSD's CARP and loadbalancing/pool features
of pf ? How about hoststated(8) ? (as I know
hoststated(8) doesn't support UDP right now)
You can do it with a pf table and with a small program
On Tue, 28 Aug 2007, reje wrote:
On the other side, I really need to introduce
_additional_ availability of DNS servers/resolvers.
This is especially true for resolvers as they are the
first layer users are facing. Assume the situation
when ordinary Windows user tries to access a web page
not yet
Hi there,
I'm wondering is there a way to scale DNS service
using OpenBSD's CARP and loadbalancing/pool features
of pf ? How about hoststated(8) ? (as I know
hoststated(8) doesn't support UDP right now)
Here is the lab setup I tried but ran into problems:
1) setup two OpenBSD 4.1 servers with
On Mon, 27 Aug 2007 05:03:40 -0700 (PDT), reje [EMAIL PROTECTED] wrote:
Hi there,
I'm wondering is there a way to scale DNS service
using OpenBSD's CARP and loadbalancing/pool features
of pf ? How about hoststated(8) ? (as I know
hoststated(8) doesn't support UDP right now)
Is it really
reje wrote:
Hi there,
I'm wondering is there a way to scale DNS service
using OpenBSD's CARP and loadbalancing/pool features
Don't ever load balance DNS in anyway.
Read the DNS BIND book.
--
Craig Skinner [EMAIL
reje wrote:
Please take a look at this Cisco document regarding
Scaling DNS services and CSM:
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns377/c649/cdccont_0900aecd800eb95d.pdf
It a while since I had such a good laugh.
The cisco doc above requires more than one device, but as
Yes, we have that much DNS requests hiting our servers
(we are not experiencing any DoS but from legitimate
user requests :-)
Furthermore, the DNS infrastructure tiemouts are
unacceptable in our scenario. Registering additinal NS
records is also unacceptable.
FYI: our primary DNS experiences
Please take a look at this Cisco document regarding
Scaling DNS services and CSM:
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns377/c649/cdccont_0900aecd800eb95d.pdf
p.s.- long ago read DNS BIND but this book assumes
tolerance to DNS timeouts and availability of more
than two DNS IP
reje wrote:
Yes, we have that much DNS requests hiting our servers
(we are not experiencing any DoS but from legitimate
user requests :-)
Furthermore, the DNS infrastructure tiemouts are
unacceptable in our scenario. Registering additinal NS
records is also unacceptable.
FYI: our primary DNS
11 matches
Mail list logo
