On 13/08/10 08:49, Matus UHLAR - fantomas wrote:
On 12.08.10 17:07, Phil Mayers wrote:
Thanks, but perhaps I should be more specific about what I'm asking:
Is it still the case that *Bind* will not follow a delegation where an
NS record points at a CNAME?
In any event, as has been pointed out
hi ,
i want to know what's the differences between bind 9 version (especially
between 9.4 and 9.5/6/7) ,
where can i find a table that can describe it?
i tried to google it but i didn't anything useful , .
can someone assist me here?
thanks in advance ,
Ram
On 8/13/2010 8:01 AM, Ram Akuka wrote:
hi ,
i want to know what's the differences between bind 9 version (especially
between 9.4 and 9.5/6/7) ,
where can i find a table that can describe it?
i tried to google it but i didn't anything useful , .
In the source directory, you will find the
On Aug 13, 2010, at 8:01 AM, Ram Akuka wrote:
hi ,
i want to know what's the differences between bind 9 version (especially
between 9.4 and 9.5/6/7) ,
where can i find a table that can describe it?
i tried to google it but i didn't anything useful , .
click on the release notes for each
On 8/13/2010 6:08 AM, Phil Mayers wrote:
Still puzzled that bind didn't seem to log anything. I will have a trawl
through the source I think; I'm sure it must be my logging config.
I don't know if I'm on the right path, but were you logging lame
delegations?
--
Dave
On 13/08/10 14:14, Dave Sparro wrote:
On 8/13/2010 6:08 AM, Phil Mayers wrote:
Still puzzled that bind didn't seem to log anything. I will have a trawl
through the source I think; I'm sure it must be my logging config.
I don't know if I'm on the right path, but were you logging lame
Hi All,
I recently set up a new web server for a group of hosts, and mirrored
the setup of bind off a working system. For some reason, the DNS is
not resolving off public dns server when the nameservers for these
domains are directed to this server, and i cannot resolve any of the
zones
On 8/13/2010 1:53 PM, Mike Mackintosh wrote:
How will the registrar be able to resolve the host name
dns.angryserver.net if dns is not propagating? I understand that when
you register a domain, the registrar will send the nameserver
information to the root servers, which are then queried for
Am 13.08.2010 19:53, schrieb Mike Mackintosh:
Hi All,
I recently set up a new web server for a group of hosts, and mirrored
the setup of bind off a working system. For some reason, the DNS is
not resolving off public dns server when the nameservers for these
domains are directed to this
Thanks,
That was the answer i was looking for. Now it is making sense.
Thanks again,
Mike
On Aug 13, 2010, at 4:19 PM, Dave Sparro wrote:
On 8/13/2010 1:53 PM, Mike Mackintosh wrote:
How will the registrar be able to resolve the host name
dns.angryserver.net if dns is not propagating? I
That is correct. I made the change like that to get it working
temporarily. The registrar is pointing to the angrystatic.com
nameservers, which the zone file is referencing the
dns.angryserver.net host. I then had dns.angrystatic.com point to the
same IP address as dns.angryserver.net, so
I am working on getting my DS record added to the DOT-US zone with
Neustar. In doing so, I found out they have a limitation of only
supporting algorithm 3, which is DSA/SHA1, or algorithm 5, which is
RSA/SHA1:
http://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xhtml
They do
In article mailman.334.1281737169.15649.bind-us...@lists.isc.org,
Mike Mackintosh mike.mackint...@angrystatic.com wrote:
That is correct. I made the change like that to get it working
temporarily. The registrar is pointing to the angrystatic.com
nameservers, which the zone file is
13 matches
Mail list logo
