On Fri, Sep 16, 2011 at 6:57 PM, babu dheen wrote:
> So when multiple DNS records are available, is it possible to direct all DNS
> queries to first (NS) record always? meaning,
>
> mail.myoffice.comINNS20.20.20.20
> mail.myoffice.comINNS30.30.30.30
>
> In the above, is i
So when multiple DNS records are available, is it possible to direct all DNS
queries to first (NS) record always? meaning,
mail.myoffice.comINNS20.20.20.20
mail.myoffice.comINNS30.30.30.30
In the above, is it possible to dirct all DNS queries only to 20.20.20.20 and
On 9/16/11 7:45 AM, "Ken Schweigert" wrote:
> Thinking maybe something happened to these devices, I listed them out
> and didn't see anything obviously wrong:
>
> [root@ns1 dev]# ls -l /dev/null
> crw-rw-rw- 1 root root 1, 3 Apr 8 14:46 /dev/null
> [root@ns1 dev]# ls -l /chroot/named/dev/null
>
Thanks everyone for showing me the null built-in. I will change it to
that and that will probably fix my problem.
-ken
On Fri, Sep 16, 2011 at 11:04 AM, Phil Mayers wrote:
> On 16/09/11 15:45, Ken Schweigert wrote:
>
>> logging {
>> ...
>> channel "dev_null_log" {
>> file "/dev/nul
On Fri, Sep 16, 2011 at 8:52 AM, Florian CROUZAT
wrote:
> babu dheen wrote on 2011-09-16:
>
>> Hi,
>> Can anyone let me know how i can resolve the below requirement.
>>
>> Requirement:
>>
>> We have two offices. One is main office and another one is remote
>> branch office. Now my company clie
babu dheen wrote on 2011-09-16:
> Hi,
> Can anyone let me know how i can resolve the below requirement.
>
> Requirement:
>
> We have two offices. One is main office and another one is remote
> branch office. Now my company client requirement is that if main office
> DNS server is not reachable
Hi,
Can anyone let me know how i can resolve the below requirement.
Requirement:
We have two offices. One is main office and another one is remote branch
office. Now my company client requirement is that if main office DNS server is
not reachable, all DNS query should be sent to branch
On 16/09/11 15:45, Ken Schweigert wrote:
logging {
...
channel "dev_null_log" {
file "/dev/null";
};
…
category lame-servers { dev_null_log; };
Why not just:
category lame-servers { null; };
...which is built-in?
___
Please vis
On Fri, 16 Sep 2011, Ken Schweigert wrote:
Looking through my named.conf the only reference I have to /dev/null is:
logging {
...
channel "dev_null_log" {
file "/dev/null";
};
…
category lame-servers { dev_null_log; };
…
I'd really like to not lose this channel because of how m
Ken Schweigert wrote:
>
> logging {
> ...
> channel "dev_null_log" {
> file "/dev/null";
> };
> …
> category lame-servers { dev_null_log; };
> …
Use the built-in "null" channel instead.
Tony.
--
f.anthony.n.finchhttp://dotat.at/
Irish Sea: South or southeast veering west o
I've been running a bind server for many years and have never had a
problem with upgrading until last night. My needs for the bind server
are pretty meager, just hosting a few hundred zones without DNSSEC.
It is set up in a chroot jail according to a linux howto I found years
ago.
When compiling,
michoski wrote:
>
> It's basically a risk analysis game. You should be able to think through
> common use cases for your service, and identify places where DNSSEC would
> add value. Your business values validity of its DNS data, or not.
Apart from protecting the DNS itself, there aren't yet man
Hi i implement a dns recursive server that only answer *a.b.c.myzone.fr* so
for this i do this:
*in named.conf:*
.
response-policy { zone "rpz.zone";};
..
*and this is the zone rpz.zone:*
;RPZ
$TTL 10
@ IN SOA rpz.zone. rpz.zone. (
48;
3600;
300;
86400;
In message <7737.1316035...@tristatelogic.com>, "Ronald F. Guilmette" writes:
>
> In message <7d9b265c-36bf-40c1-9012-ac0a96fb8...@sackheads.org>, you wrote:
>
> >On Sep 14, 2011, at 4:35 PM, Ronald F. Guilmette wrote:
> >
> >> Is there a rule that says how a resolver should behave in cases wher
14 matches
Mail list logo
