> On 13 Apr 2023, at 06:44, Mark Andrews wrote:
>
>
>
>> On 13 Apr 2023, at 03:19, Fred Morris wrote:
>>
>> TLDR: NS records occur above and below zone cuts.
>>
>> On Wed, 12 Apr 2023, John Thurston wrote:
>>>
>>> We have authority over state.ak.us, which we publish as a public zone. We
On 13/04/2023 5:58 am, Havard Eidnes via bind-users wrote:
I suspect you don't need the NS records in challenge.state.ak.us and
if you remove them then the records in challenge.state.ak.us are
simply part of the state.ak.us zone since they're served off of the
same server.
Unfortunately "not qui
> On 13 Apr 2023, at 03:19, Fred Morris wrote:
>
> TLDR: NS records occur above and below zone cuts.
>
> On Wed, 12 Apr 2023, John Thurston wrote:
>>
>> We have authority over state.ak.us, which we publish as a public zone. We
>> also publish challenge.state.ak.us as a public zone.
>>
>> Th
> I suspect you don't need the NS records in challenge.state.ak.us and
> if you remove them then the records in challenge.state.ak.us are
> simply part of the state.ak.us zone since they're served off of the
> same server.
Unfortunately "not quite".
While a publishing name server will respond wit
it'll matter when you decide to add DNSSEC to the zone, and it's also
good hygiene in the absence of DNSSEC so that any future maintainer
can be reminded that there is a subdomain at that name when looking at
the parent.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe fro
TLDR: NS records occur above and below zone cuts.
On Wed, 12 Apr 2023, John Thurston wrote:
We have authority over state.ak.us, which we publish as a public zone. We
also publish challenge.state.ak.us as a public zone.
The public NS records for state.ak.us are: ns4.state.ak.us and
ns3.state
On Thu, Jul 13, 2017 at 8:39 PM, wrote:
> Hi Bob:
>
> These examples help! Thank you.
>
> On Thu 7/13/17 15:53 -0400 Bob Harold wrote:
> > Let's illustrate one NS record, for each of the cases:
> > (I think your case is #2)
> >
> > 1. Name server name inside the domain itself
> >
> > example.com
-evans ] [
https://github.com/jakedevans ] [ https://keybase.io/jacobdevans ]
- Original Message -
From: "Niall O'Reilly"
To: "bind-users"
Sent: Friday, July 14, 2017 2:40:49 PM
Subject: Re: delegation NS records
On 14 Jul 2017, at 14:07, b...@zq3q.org wrote:
>
On 14 Jul 2017, at 14:07, b...@zq3q.org wrote:
> only a single **delegation** NS record
> needed
Actually, there should be two or more, and their IP addresses
should belong to different networks.
RFC1034, section 4.1:
A given zone will be available from several name servers to insure its
av
Yesterday, Niall corrected me off list. Hopefully what I write below is
now correct:
Assume our nameserver SOA and related authoritatve NS record are in
the zone w/$ORIGIN" "example.com.". Regardless of what the FQDN for
the nameserver itself is, only a single **delegation** NS recor
On 13.07.17 19:39, b...@zq3q.org wrote:
Interesting. I think the glue record make sense.
I'm not planning to do this. :->
I do not see any delegation NS record for otherdomain.com above.
Is this right?:
TLD com zone:
example.comIN NS ns.otherdomain.com
ns.example.com IN A
Hi Bob:
These examples help! Thank you.
On Thu 7/13/17 15:53 -0400 Bob Harold wrote:
> Let's illustrate one NS record, for each of the cases:
> (I think your case is #2)
>
> 1. Name server name inside the domain itself
>
> example.com zone:
> example.com IN NS ns.example.com
> ns.example.com I
On Thu, Jul 13, 2017 at 3:33 PM, wrote:
> Hi Niall:
>
> On Tue 7/11/17 22:56 +0100 "Niall O'Reilly" wrote:
> > On 11 Jul 2017, at 22:01, b...@zq3q.org wrote:
> >
> > > As I wrote to Niall (msg dated 11 Jul 2017 15:04:32 -0500) ,
> >
> > That hasn't reached me yet.
> >
> > > I **do not** have a NS
Hi Niall:
On Tue 7/11/17 22:56 +0100 "Niall O'Reilly" wrote:
> On 11 Jul 2017, at 22:01, b...@zq3q.org wrote:
>
> > As I wrote to Niall (msg dated 11 Jul 2017 15:04:32 -0500) ,
>
> That hasn't reached me yet.
>
> > I **do not** have a NS record for each of my two
> > nameservers, in the domain
14 matches
Mail list logo
