Re: first axfr challenges

Tim: >> Both of those servers are accessed by name, not numerical IP >> address, and those names have to be in some public DNS records, so >> people can find the IP addresses for them to connect to them. Joe Zeff: > No. DNS servers are always accessed by IP address, never by name. > Trying to ac

Re: first axfr challenges

Tim: >> The internet, at large, will always use your primary server. If it >> can't, it'll try your secondary server. Ed Greshko: > I'm not certain what you mean by the use of "primary" in that > statement. But I don't think it is actually accurate in any event. It's probably an out-of-date con

Re: first axfr challenges

On 07/06/2021 21:49, Tim via users wrote: On Sun, 2021-06-06 at 11:54 -0700, Jack Craig wrote: something i dont get, if my registrar provides glue references for primary & secondary domain dns servers, what purpose is served by anything in my host's named.conf (et al) having any reference to my

Re: first axfr challenges

Thanks for all your advice; you are right! I'll let the registrar do what they are already being paid to do. I really appreciate your guidance, jackc... On Mon, Jun 7, 2021 at 2:28 PM Ed Greshko wrote: > On 08/06/2021 02:10, Mike Wright wrote: > > Perhaps a lot of the confusion comes from the

Re: first axfr challenges

Thanks Tim, If you aren't a teacher, you are missing an academic calling! Thanks again! On Mon, Jun 7, 2021 at 6:49 AM Tim via users wrote: > On Sun, 2021-06-06 at 11:54 -0700, Jack Craig wrote: > > something i dont get, if my registrar provides glue references for > > primary & secondary dom

Re: first axfr challenges

On 08/06/2021 02:10, Mike Wright wrote: Perhaps a lot of the confusion comes from the dual uses of the term:   primary in search order (which is random)   primary source for zone data (which is fixed by an SOA) To make matters more confusing there are more complex setups where the zone masters 

Re: first axfr challenges

On 07/06/2021 02:54, Jack Craig wrote: /[jackc@ws ~ $ host -t axfr linuxlighthouse.com ns22.worldnic.com Trying "linuxlighthouse.com " Using domain server: Name: ns22.worldnic.com Addre

Re: first axfr challenges

On 6/7/21 6:49 AM, Tim via users wrote: On Sun, 2021-06-06 at 11:54 -0700, Jack Craig wrote: something i dont get, if my registrar provides glue references for primary & secondary domain dns servers, what purpose is served by anything in my host's named.conf (et al) having any reference to my do

Re: first axfr challenges

On 6/7/21 7:49 AM, Tim via users wrote: The internet, at large, will always use your primary server. If it can't, it'll try your secondary server. Both of those servers are accessed by name, not numerical IP address, and those names have to be in some public DNS records, so people can find the

Re: first axfr challenges

On Sun, 2021-06-06 at 11:54 -0700, Jack Craig wrote: > something i dont get, if my registrar provides glue references for > primary & secondary domain dns servers, what purpose is served by > anything in my host's named.conf (et al) having any reference to my > domain if it's not accessible/useful?

Re: first axfr challenges

*whois linuxlighthouse.com | grep ^NameName Server: NS21.WORLDNIC.COM Name Server: NS22.WORLDNIC.COM [jackc@ws ~ $ whois linuxlighost -t axfr linuxlighthouse.com ns21.worldnic.com

Re: first axfr challenges

On 18/05/2021 03:50, Jack Craig wrote: *i am getting a notauth on my axfr attempt. what i am not seeing is an  A ip# for the secondary dns server.* Oh, FWIW, I have previously mentioned that since your system is quite "open" I configured a system here as a slave to your domain.  My named.conf

Re: first axfr challenges

On 18/05/2021 03:50, Jack Craig wrote: *i am getting a notauth on my axfr attempt. what i am not seeing is an  A ip# for the secondary dns server.* * * *is this missing A record a problem i need to fix for following host cli??? * * * *dig @ws.linuxlighthouse.com a