From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <6479851c.32.mr2ice.fgrirsq@earthlink.net>
Date: Thu, 01 Jun 2023 22:58:52 -0700
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-7216684@2rosenthals.com>
Subject: Re: [eCS-ISP] Setting up BIND

In <list-7216684@2rosenthals.com>, on 06/02/23
   at 01:43 PM, "Peter Moylan" <ecs-isp@2rosenthals.com> said:

>Now that my BIND installation appears to be handling internal queries 
>correctly, it's time to bite the bullet and open it up to the external 
>world.

>lookups for your domains." Now, I understand about port 53, but  I don't
>understand the part about "delegate your domains". What do I  need to do
>here?

You ask your registrar to do it.  Search for:

  how to delegate a domain to your nameserver

and you will get numerous explanations.

This is what delegation makes happen.  A search for

  how does the tld know about my domain

will provide numerous explanations of the magic that is the nameservers
talking to each other.

Here's an example:

[d:\tmp]dig @192.5.6.30 barney.dnacih.com

; <<>> DiG 9.11.28 <<>> @192.5.6.30 barney.dnacih.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24560
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 4 ;;
WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;barney.dnacih.com.             IN      A

;; AUTHORITY SECTION:
dnacih.com.             172800  IN      NS      warf.dnacih.com.
dnacih.com.             172800  IN      NS      ns1.dnacih.com.
dnacih.com.             172800  IN      NS      ns2.dnacih.com.

;; ADDITIONAL SECTION:
warf.dnacih.com.        172800  IN      A       64.60.60.126
ns1.dnacih.com.         172800  IN      A       47.180.217.134
ns2.dnacih.com.         172800  IN      A       50.209.190.117

192.5.6.30 is one of the TLD name servers for the .com domain.  It does
not have any specific information about barney, but it knows the
nameservers that do and these are what is provides in he authoriy section
of the response to the DNS request.

This is also where caching and time to live come into play.  Let's say my
local nameserver is google at 8.8.8.8.  If I ask it to resolve
barney.dnacih.com, it may or may not have the requested items cached. 
Let's say it knows nothing about dnacih.com, it will send the request to a
nameserver that is known to be authoritative for the .com domain. This
process recurses until an authoritative nameserver for barney.dnacih.com
is located.

>Also, I'm guessing that I need to leave my previous nameserver hosting 
>in place for a day or two to allow for propagation delays. Is that right?

That will work.  You can actually leave the settings at that nameserver in
place until your IP address changes.


Steven

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------