On Fri, Sep 12, 2014 at 09:11:08AM +1000, John Marshall wrote:
> I can't build BIND 9.10.1rc2 on recent FreeBSD 10-STABLE.
> I have tried on both i386 and amd64 variants of the operating system.
> BIND 9.10.1rc1 builds fine, as did the beta releases.
Based on the failure being in bin/python, I sup
I can't build BIND 9.10.1rc2 on recent FreeBSD 10-STABLE.
I have tried on both i386 and amd64 variants of the operating system.
BIND 9.10.1rc1 builds fine, as did the beta releases.
Failure looks like this:
making all in /build/bind/bind-9.10.1rc2/bin/python
make[3]: don't know how to make dn
> -Original Message-
> From: bind-users-boun...@lists.isc.org [mailto:bind-users-
> boun...@lists.isc.org] On Behalf Of Mark Andrews
> Sent: Friday, 12 September 2014 8:58 AM
> To: John Miller
> Cc: Bind Users Mailing List
> Subject: Re: Promoting slave to master DNS server with dynamic u
In message
, John
Miller writes:
>
> Hi Eric,
>
> Depends on how long you can live without dynamic updates, and how many
> dynamic updates it's acceptable to lose in the event of a master failure.
> Journal files are synced every 15 minutes, so in the event of a master
> failure (in a single-m
In message <5411bdd6.4010...@chrysler.com>, Kevin Darcy writes:
> (Yes, I'm aware that there was a proposal recently discussed on the
> DNSOP list for an MX-target convention to denote "no mail service
> offered here". That would presumably solve the problem I cited in the
> previous paragraph.
> On 9/11/2014 11:51 AM, Mark Elkins wrote:
>> On Thu, 2014-09-11 at 11:27 -0400, Kevin Darcy wrote:
>>> Mark,
>>> Depending on implementation, a PTR RRset with multiple
>>> records either
>>>
>>> -- only ever gets answered with the "first" record of the set (in
>>> which case the seco
On 9/11/2014 11:51 AM, Mark Elkins wrote:
On Thu, 2014-09-11 at 11:27 -0400, Kevin Darcy wrote:
Mark,
Depending on implementation, a PTR RRset with multiple
records either
-- only ever gets answered with the "first" record of the set (in
which case the second and subsequent records
In reference to the question of using a CNAME or A record for "
www.example.com", it seems to me that the best solution, if we could ever
get there, would be to create a new record type that means "redirect an A
or lookup to this other name". Like this:
example.com. IN SOA
example.co
On 9/11/2014 12:08 PM, Matus UHLAR - fantomas wrote:
we both also said it's personal preference.
On 11.09.14 12:53, Kevin Darcy wrote:
And I'm saying that's a cop-out. It should be a recommended practice
encouraging consistent
forward/reverse mappings is something that all DNS admins have a
On 9/11/2014 12:08 PM, Matus UHLAR - fantomas wrote:
On 9/11/2014 3:47 AM, Matus UHLAR - fantomas wrote:
On 10.09.14 18:13, Kevin Darcy wrote:
No, what I'm saying is that if
example.com owns an A record 203.0.113.48, and
www.example.com owns an A record 203.0.113.48, then
where does 48.113.0.
On 9/11/2014 3:47 AM, Matus UHLAR - fantomas wrote:
On 10.09.14 18:13, Kevin Darcy wrote:
No, what I'm saying is that if
example.com owns an A record 203.0.113.48, and
www.example.com owns an A record 203.0.113.48, then
where does 48.113.0.203.in-addr.arpa point?
Completely your decision.
So
Hello John,
Thanks for taking the time to respond.
For the journal files could i force the dump every time i do an update ?
nsupdate… rndc freeze/thaw boom everything in sync. I know that normaly you
wait 15 minutes and that bind does that for you but we do not have that much
load and it wo
On Thu, 2014-09-11 at 11:27 -0400, Kevin Darcy wrote:
> Mark,
> Depending on implementation, a PTR RRset with multiple
> records either
>
> -- only ever gets answered with the "first" record of the set (in
> which case the second and subsequent records of the set are just a
> waste of
Mark,
Depending on implementation, a PTR RRset with multiple
records either
-- only ever gets answered with the "first" record of the set (in which
case the second and subsequent records of the set are just a waste of
space), or
-- answers in a random, cyclic and/or round-robin fa
On 9/11/2014 3:47 AM, Matus UHLAR - fantomas wrote:
On 10.09.14 18:13, Kevin Darcy wrote:
No, what I'm saying is that if
example.com owns an A record 203.0.113.48, and
www.example.com owns an A record 203.0.113.48, then
where does 48.113.0.203.in-addr.arpa point?
Completely your decision.
So
Hi Eric,
Depends on how long you can live without dynamic updates, and how many
dynamic updates it's acceptable to lose in the event of a master failure.
Journal files are synced every 15 minutes, so in the event of a master
failure (in a single-master situation), you've lost at most 15 minutes'
w
In article ,
Antonio Querubin wrote:
> On Thu, 11 Sep 2014, Matus UHLAR - fantomas wrote:
>
> > If you point www CNAME @, the 'www' will have both MX and NS records same as
> > example.com. Which may e.g. cause rejectd on backup MX hosts, apparently
> > not designed to receive mail for www.exa
In article ,
Alan Clegg wrote:
> On 9/10/14, 8:42 AM, Sam Wilson wrote:
>
> > And you could reduce maintenance very slightly by replacing
> >
> > www in A 75.100.245.133
> >
> > with
> >
> > www in CNAME @
>
> And now you have an MX record, 3 NS re
Hello DNS gurus,
New on the list, I’ve been tasked by my manager to revamp our dns
infrastructure. I think this list is the best place to get answers.
Bind 9.3.6-16 running on RHEL5.7
Right now everything run’s on manually editing zone files but we have recently
integrated vmware orchestrator
On Thu, 11 Sep 2014, Matus UHLAR - fantomas wrote:
If you point www CNAME @, the 'www' will have both MX and NS records same as
example.com. Which may e.g. cause rejectd on backup MX hosts, apparently
not designed to receive mail for www.example.com.
Actually no. All other RRs are supposed t
On 10.09.14 18:13, Kevin Darcy wrote:
No, what I'm saying is that if
example.com owns an A record 203.0.113.48, and
www.example.com owns an A record 203.0.113.48, then
where does 48.113.0.203.in-addr.arpa point?
Completely your decision.
Some people will point it at example.com, some will poi
On Wed, 2014-09-10 at 18:13 -0400, Kevin Darcy wrote:
> No, what I'm saying is that if
>
> example.com owns an A record 203.0.113.48, and
> www.example.com owns an A record 203.0.113.48, then
>
> where does 48.113.0.203.in-addr.arpa point?
>
> Some people will point it at example.com, some will
22 matches
Mail list logo
