Hi,
Thanks for the response. But i read a article in sans.org website that internal
DNS server should not respond to ROOT NS query.
Please find the below URL for more information.
http://isc1.sans.org/dnstest.html
http://isc.sans.edu/diary.html?storyid=5713
Kindly help me.
--- On Thu,
Hi,
I work for a small ISP in Sweden and we recently starting to provide IPv6 for
customers. I have a problem thou with the reverse DNS lookups for IPv6. I don't
have a good way of doing this, maybe someone can help.
When we deliver IPv6 service to a customer they get at least a /64, which you
Hi,
On Mon, Mar 14, 2011 at 09:16:13PM -0400, Kevin Darcy wrote:
> Stub zones: only available as a single level beyond one's "authoritative
> core", i.e. the stub server must be able to talk directly to one or more
> authoritative servers for the zone.
> Forward zones: can be daisy-chained an
On Mon, Mar 14, 2011 at 01:36:10PM +0100, Jan-Piet Mens wrote:
> A stub zone tells BIND to load SOA and NS records from its masters {}.
> (forwarders {} is, I belive, both useless and incorrect here.) From that
> point onwards, your BIND will use the data in the stub to recursively
> find answers t
In message <8423.3972...@web137314.mail.in.yahoo.com>, babu dheen writes:
> Hi,
>
> Thanks for the response. But i read a article in sans.org website that inte=
> rnal DNS server should not respond to ROOT NS query.
>
> Please find the below URL for more information.
>
> http://isc1.sans.or
On 18.03.2011 10:17, Marc Haber wrote:
> Which it doesn't in the "forward" setup, it just immediately returns NXDOMAIN.
Do you include zones.rfc1918 in your configuration? What SOA RR does the
NXDOMAIN return?
| zone "0.10.in-addr.arpa" {
| type forward;
| forwarders { 10.0.0.2; };
| };
Den 18. mars 2011 kl. 10.07 skrev
:
> Are there any good information, maybe RFC, how reverse DNS should be done in
> IPv6. Then I don’t mean how to register a ip6.arpa and edit your zone-file in
> bind. I mean how you solve the problem with generate 2^64 unique PTR records
> for a single cust
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I conducted a DNSSEC tests with Bind 9.8 (also 9.7.3) and Thales nShield
HSM.
Everything compiled fine, I was able to generate keys and list keys on HSM:
# pkcs11-list -p xxx
object[0]: handle 1120 class 3 label[6] 'example-KSK' id[0]
object[1]: han
On Mar 18, 2011, at 5:07 AM, mattias.o.anders...@gavle.se wrote:
Hi,
I work for a small ISP in Sweden and we recently starting to provide
IPv6 for customers. I have a problem thou with the reverse DNS
lookups for IPv6. I don’t have a good way of doing this, maybe
someone can help.
When
> On Mon, Mar 14, 2011 at 09:16:13PM -0400, Kevin Darcy wrote:
> > As a general rule, use "type forward" zones only if you have some
> > connectivity issue you need to work around, e.g. trying to resolve
> > Internet names from behind a restrictive firewall.
On 18.03.11 10:15, Marc Haber wrote
Hello,
This was shared at RIPE61 and is pertinent to this discussion. It presents
different approaches toward managing IPv6 PTR records for large subnets:
http://ripe61.ripe.net/presentations/139-Ripe-61-rDNS-kzorba-freedman.pdf
Thanks,
Mark
-Original Message-
From: bind-users-boun
You could just put the customer zones on a separate nameserver
and let the clients dynamically update the zones.
Windows will do this automatically.
Named has 6to4-self and tcp-self which use TCP as the authenticator.
6to4-self lets any machine in the /48 update records for any other
machine in
hi bind network
hi guru of bind
is there a special key DNSKEY for areas zone .eu
or should we be satisfied keys included in the tarball of bind
thanks for your return
--
gpg --keyserver pgp.mit.edu --recv-key 092164A7
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7
signature.as
On Sat, 19 Mar 2011, fakessh @ wrote:
Subject: key DNSKEY for areas zone .eu
hi bind network
hi guru of bind
is there a special key DNSKEY for areas zone .eu
or should we be satisfied keys included in the tarball of bind
There already is a DS record delagation in the root zone, so no
speci
14 matches
Mail list logo