Hello,
I have a two DNS servers, which our customers uses to "host" their domains.
Sometimes customers forgot to renew domain, or just don't want to
renew it, or they move domain to other name servers.
However i still have records for this domains in my configs.
Is there any way to determine whi
In message <2070cf420902060124ged41b99jf56a15306c9b2...@mail.gmail.com>, "Konst
antin N. Bezruchenko" writes:
> Hello,
>
> I have a two DNS servers, which our customers uses to "host" their domains.
>
> Sometimes customers forgot to renew domain, or just don't want to
> renew it, or they move do
In article ,
Mark Andrews wrote:
> In message , Chris
> Thompson writes:
> > On Feb 5 2009, I wrote:
> >
> > >DLV records for advocaat.pro & advocaten.pro are among the recent
> >additions to dlv.isc.org. Using validating recursive nameservers
> > >running BIND 9.5.1-P1 (configured to trust dl
On Thu, 2009-02-05 at 16:58 -0800, Chris Buxton wrote:
> Use a different key for each slave.
Definitely, if each of your slaves is under distinct
administration.
If some organization is managing more than one of your
slaves for you, I'ld suggest using a distinct ke
Thanks for the reply. My DMZ, or external lookups, are all performed via one
of six BIND-9 servers.
The product that we use is based on BIND-8, though they've recently come out
with a BIND-9 version.
If I "split" my lookups and have internal lookups pointed at the MS DNS
servers, and non-aut
We also run in a mixed MSDNS/BIND environment. All of our AD domain
controllers run MSDNS and are authoritative for the AD domain only. They
forward all non-authoritative requests (all non AD domain queries) to
caching BIND9/Linux servers which also contain slave zones for all of our
internal dom
In my case, we let AD/MSDNS do dynamic updates.. no dynamic updates are
necessary with BIND. Not sure I understand your "split" lookups - but your
external authoritative nameservers should NOT allow recursion.
Josh
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-us
Hello;
My site is presently using a product derived from BIND-8 for internal DNS only.
For years our Windows team has been arguing that they want to be non-dependent
on the non-MS DNS servers; which they say causes them much grief on firmwide
shutdown/bootups.
Well, their concerns have fall
I'm with Josh on this.
The only things that we have that would have both internal and external
addresses are servers. For the domain I'm speaking of those are hard
assigned addresses not DHCP so there is no dynamic update being done.
We simply send an email to the Windoze Admins asking them to ad
I don't see why it is either/or.
Here we have Windoze DNS servers for internal lookups and Linux/BIND 9
DNS servers for external lookups. The internal servers refer all
queries they aren't authoritative for to the external ones which in turn
refer all queries for domains we don't own to the root
Ah! Now I see. Thank you! That has narrowed my search area. I'll post
back when I find the file I need to change.
Thanks,
jwc
-Original Message-
From: mark_andr...@isc.org [mailto:mark_andr...@isc.org]
Sent: Thursday, February 05, 2009 4:11 PM
To: Cherney John-CJC030
Cc: bind-us...@isc
Hello Chris,
thank you for the "HOWTO"... now it is more clear.
OK, there are some stange things happen to my master DNS @home. Since I
it seems I had a "nsupdate" from my Laptop, an update from my work-
stations was working perfectly and now it comes:
I have never used:
Am 2009-02-05 16:
Point 1: The rndc.key file is referenced automatically if its contents
are not included, because you do not have a controls statement. This
is confusing, so please read the section of the ARM on the controls
statement.
__
Point 2: Your 'allow-update' statement is wrong. You have:
allow-upd
13 matches
Mail list logo