On 03/31/11 04:54, Mike Diggins wrote:
> The A records for the two nameservers exist in the sub.Domain.CA zone
> file. I can fix the error by adding the two nameserver A records to the
> Domain.CA zone file but I'm wondering why this is an error with 9.7, and
> not 9.2.1, and is this the correct wa
I have a "hidden" master name server for the domain domain.CA. The name
servers for this domain are in the subdomain sub.Domain.CA as ns1 and ns2.
Those are the name servers my clients query. The zone file starts off like
this:
$TTL 3600
Domain.CA. IN SOA ns1.sub.Domain.CA. dnsgrp.Domain
I'm wondering if the issue isn't because you've not told your ISP what
your name servers are. You have to do that for reverse delegations to
get to your servers. (This is in addition to telling your Registrar.)
-Original Message-
From: bind-users-bounces+jlightner=water@lists.isc.o
It's a little less novice-friendly than Men & Mice, but it has price
going for it. Take a look at GADMIN Tools for BIND
(http://gadmintools.flippedweb.com/index.php?option=com_content&task=view&id=14&Itemid=33).
Even better, take a look at Infoblox NIOS-based IPAM appliance; you
could easily set o
On 03/30/2011 04:45 AM, ben thielsen wrote:
both fail to do so. so - it would seem to me that at least somehow,
in some sense, the delegation is broken. however, if queried further
It does seem a bit broken - there's no SOA for 33.50.in-addr.arpa i.e.
no zone there.
for a /24 within that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Your questions seems more geared towards a list that deals with Microsoft
Perhaps try the NT System Admin list or the AD list:
http://www.sunbeltsoftware.com/communities/
On 03/30/2011 02:34 AM, babu dheen wrote:
> Hi,
>
> We are using Micros
On Wed, Mar 30, 2011 at 01:04:24PM +0530,
babu dheen wrote
a message of 43 lines which said:
> We are using Microsoft AD server as DNS server
This is a BIND list so if you use another software, you are in the
wrong place.
> firewall logs shows that internal AD servers is contacting root DN
Hi,
We are using Microsoft AD server as DNS server for our company and we have
configured FORWARDER to ISP DNS server for external domain queries. What we
noticed that our internal DNS server is able to use FORWARDERS all time but
firewall logs shows that internal AD servers is contacting roo
8 matches
Mail list logo