Le mardi 8 novembre 2011 10:34, rams a écrit :
Hi ,
I have signed zone and already i have resigned two times. Now again i am
resigning zone but after resign zone , RRSIG values are not changed. the
same old values displaying. Any wrong in me. Could you please guide me how
to change RRSIG
On 10.11.2011 02:57, 风河 wrote:
I have two server IPs, the A records for them are:
mail.dnsbed.com.300 IN A 74.117.233.4
mail.dnsbed.com.300 IN A 74.117.232.204
The corresponding PTR records are:
4.233.117.74.in-addr.arpa. 36466 IN PTR
On 11/09/11 15:59, trm asn wrote:
On Wed, Nov 9, 2011 at 3:15 PM, Matus UHLAR - fantomas
uh...@fantomas.sk mailto:uh...@fantomas.sk wrote:
Now I have only one question:
On 08.11.11 20:27, trm asn wrote:
The moment I have done the rndc reload example.com
Thanks everybody for the answers.
I have one more question - how can I block every update for every zone in
options section using update-policy?
logging { ... };
options {
directory /var/named;
dnssec-enable yes;
recursion yes;
allow-recursion { 127.0.0.1; };
I have one more question - how can I block every update for every zone
in options section using update-policy?
Are you actually *reading* the documentation: the ARM actually defines
`allow-update':
Specifies which hosts are allowed to submit Dynamic DNS updates
for master
On Thu, Nov 10, 2011 at 8:28 PM, Lyle Giese l...@lcrcomputer.net wrote:
On 11/09/11 15:59, trm asn wrote:
On Wed, Nov 9, 2011 at 3:15 PM, Matus UHLAR - fantomas
uh...@fantomas.sk mailto:uh...@fantomas.sk wrote:
Now I have only one question:
On 08.11.11 20:27, trm asn wrote:
On 11/10/11 12:24, trm asn wrote:
On Thu, Nov 10, 2011 at 8:28 PM, Lyle Giese l...@lcrcomputer.net
mailto:l...@lcrcomputer.net wrote:
On 11/09/11 15:59, trm asn wrote:
On Wed, Nov 9, 2011 at 3:15 PM, Matus UHLAR - fantomas
uh...@fantomas.sk mailto:uh...@fantomas.sk
I know that this isn't the forum for betas, which is why I put off-topic on the
subject line. We are trying to implement DNSSEC for our static zones. While
the dynamic signing has been automated, static inline-signing isn't available
until Bind 9.9
We have been testing with the alphas and now
Do you see that each time named starts or just on the first load of the zone?
What happens if you send a query to the server with dig +dnssec?
On Nov 10, 2011, at 14:23, McConville, Kevin kmcconvi...@albany.edu wrote:
I know that this isn’t the forum for betas, which is why I put off-topic
I know that this isn't the forum for betas
Sure it is. :)
We have been testing with the alphas and now with the beta. What we are
seeing is that whenever named starts, it initially creates the signed
static zone file, but never really finishes.
What do you mean by never really finishes?
In message 4b476ffb.2625d518.4ebbf979.d1...@o2.pl, =?UTF-8?Q?Aleksander_Kurczy
k?= writes:
Thanks everybody for the answers.
I have one more question - how can I block every update for every zone in opti
ons section using update-policy?
Updates are blocked by default and will always be
Thanks for the responses.
Can a DNS server (the machine, not BIND) be a tunnel endpoint
for 6to4?
Thanks,
Hansen
On Thu, Nov 10, 2011 at 3:05 PM, Hansen Candrawinata
hansen.candrawin...@gmail.com wrote:
This is not strictly a BIND related question, but thought someone here
probably knew the
In message ca+ofh68z4wuagabxsjnvfyhyhjlkksyljmutrqycgbphmdv...@mail.gmail.com,
Hansen Candrawinata writes:
Thanks for the responses.
Can a DNS server (the machine, not BIND) be a tunnel endpoint
for 6to4?
Yes, provided it meets all the criteria for being a 6to4 tunnel end
point. You need
Dear All,
Somewhere I read that number of ROOT DNS servers is limited to 13 because of
protocol limitation of DNS and UDP.
Exact writing was A combination of limits in the DNS and certain
protocols, namely the practical size of unfragmented User Datagram Protocol
(UDP) packets, resulted in a
14 matches
Mail list logo
