On Thu, Apr 02, 2015 at 09:46:16PM -0500, Grant Taylor wrote:
> I think I saw a tweet with a figure around $185,000 US Dollars.
>
> I wonder if that is on the low side.
I believe that's the fee to apply, per domain. Proof of ability to
provision and run a registry business to ICANN specification
It would be a nice feature, but in lieu of that, you could always
have a script manage your named.conf and incorporate the
variable-substitution logic into that. If you want to go Old School,
use cpp, make, sccs, some of those long-forgotten tools :-)
I've had wonderful success with Makefile(s)
On 04/01/2015 06:57 PM, /dev/rob0 wrote:
I'm sure it was not cheap.
I think I saw a tweet with a figure around $185,000 US Dollars.
I wonder if that is on the low side.
--
Grant. . . .
unix || die
___
Please visit https://lists.isc.org/mailman/lis
On 04/01/2015 08:51 PM, Steven Carr wrote
(The MMC tricks you as it shows folders for subdomains on the dotted
host names when they don't actually exist.)
They are indeed sub-domains. They just are not delegated. Thus they
are part of the same (parent) zone.
--
Grant. . . .
unix || die
_
On 02/02/2015 10:40 AM, LuKreme wrote:
That will not help if the FIRST connection is hitting a tar-pit.
I don't know if you found a satisfactory answer or not. Her's what I
would try with a pair of Bind ""servers (daemons).
Configure your first ""server to "forward first" to your second ""s
> On 1 Apr 2015, at 23:30, Jeff Sadowski wrote:
>
> Do I really need to have each zone with its own file?
You can omit the file option in a slave zone and named will keep the zone in
memory only. The disadvantage is it will have to retransfer all the zones in
full when it starts before it can
Jeff,
That only works on the master zone server, without dynamic updates. Any
slave zones or zones with dynamic updates will have problems because the
zone file will be overwritten with one zone each time it is updated.
--
Bob Harold
hostmaster, UMnet, ITcom
Information and Technology Servi
On Thu, Apr 2, 2015 at 4:05 PM, Jan-Piet Mens wrote:
> > 2001:67c:2e8:5::c100:c6#53: Transfer completed: 0 messages, 0 records, 0
> >
> > Is there any logic to this that I'm missing?
>
> s/completed/failed/ on error cannot be particularly difficult to
> implement.
>
> -JP
>
> +1 for makin
> 2001:67c:2e8:5::c100:c6#53: Transfer completed: 0 messages, 0 records, 0
>
> Is there any logic to this that I'm missing?
s/completed/failed/ on error cannot be particularly difficult to
implement.
-JP
___
Please visit https://lists.isc.org/m
On 04/02/2015 05:01 AM, Anand Buddhdev wrote:
> I'm parsing BIND logs to extract the XFR size in bytes of a zone, and
> was just bitten by this sequence:
>
> 02-Apr-2015 04:27:10.393 xfer-in: transfer of './IN' from
> 2001:67c:2e8:5::c100:c6#53: failed to connect: timed out
> 02-Apr-2015 04:27:10
It would be a nice feature, but in lieu of that, you could always have a script
manage your named.conf and incorporate the variable-substitution logic into
that. If you want to go Old School, use cpp, make, sccs, some of those
long-forgotten tools :-)
On Thu, Apr 2, 2015 at 11:09 AM, Jeff Sadowski wrote:
> On Wed, Apr 1, 2015 at 8:09 PM, Barry Margolin wrote:
>> In article ,
>> Jeff Sadowski wrote:
>>
>>> I have a number of slave domains that I would like a naming scheme and
>>> not have to go to each and change the filename.
>>>
>>> I have
On Wed, Apr 1, 2015 at 8:09 PM, Barry Margolin wrote:
> In article ,
> Jeff Sadowski wrote:
>
>> I have a number of slave domains that I would like a naming scheme and
>> not have to go to each and change the filename.
>>
>> I have the following zones
>>
>> zone "1.168.192.in-addr.arpa" {
>>
Thank you very much Simon. I will probably try the nsupdate route, the first
option you presented does seem to be the least attractive, or at least,
ungentle, way to proceed.
-Original Message-
From: dhcp-users-boun...@lists.isc.org
[mailto:dhcp-users-boun...@lists.isc.org] On Behalf Of
I'm sorry, not sure which list this belongs in...
I have a working (many thanks to list members) dhcp for my 10.57.36/22 network,
I have the forward table, and my 4 reverse tables.
It all works correctly with my dynamic dns.
Except-I set my available address range to 10.57.36.10 - 10.57.39.150,
Short answer: don't! Running a public recursive DNS server is an
incredibly bad idea unless you have the resources of Google or other
ISPs. It's easy for attackers to exploit it in several ways, and
you'd also need to solve some non-trivial load balancing and caching
challenges. There's way more
Hi
How to configure a DNS server as public DNS server like google's 8.8.8.8 server
Help me to clear out these problem
Thank you
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bi
Not all the new TLDs are company specific. Some are more generic but useful
to certain industries.
There are 2 or 3 TLDs that I assume will appear sooner or later and I really
wish I had the capital to make them as I know as soon as they are available
many companies will use them so they'd be
On 02.04.15 11:52, Teerapatr Kittiratanachai wrote:
Firstly, I have 2 nameserver, the first nameserver is the
authoritative nameserver and not allow the recursive. The second one
is the recursive nameserver, and also store zonefile as the same with
the first server.
I have remove zonefile from t
I'm parsing BIND logs to extract the XFR size in bytes of a zone, and
was just bitten by this sequence:
02-Apr-2015 04:27:10.393 xfer-in: transfer of './IN' from
2001:67c:2e8:5::c100:c6#53: failed to connect: timed out
02-Apr-2015 04:27:10.393 xfer-in: transfer of './IN' from
2001:67c:2e8:5::c100:
20 matches
Mail list logo
