Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: DDNS updates for zone having multiple primary servers
      (Simon Hobson)
   2. Re: DDNS updates for zone having multiple primary servers
      (kraishak)
   3. Re: DDNS updates for zone having multiple primary servers
      (Simon Hobson)
   4. Re: DDNS updates for zone having multiple primary servers
      (kraishak)


----------------------------------------------------------------------

Message: 1
Date: Thu, 1 Apr 2021 20:17:24 +0100
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: DDNS updates for zone having multiple primary servers
Message-ID: <99e27de9-cfd3-41f1-ba58-4bb040523...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii

glenn.satch...@uniq.com.au wrote:

> My understanding from a long time ago (as in >5 years) was that that dynamic 
> dns updates are only sent to the primary DNS server. The primary is expected 
> to forward to all the secondaries.

I've not seen anything to suggest that has changed.

In the absence of a zone declaration, the primary DNS server is determined by 
looking at the SOA record for the zone - so without keys setup, a correctly 
configured DNS setup will automagically get updates as long as updates are 
allowed (e.g. by IP address). If a zone declaration is present, then the server 
specified in that is used.

Simon



------------------------------

Message: 2
Date: Thu, 1 Apr 2021 23:25:00 -0500 (CDT)
From: kraishak <kraishak....@gmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: DDNS updates for zone having multiple primary servers
Message-ID: <1617337500022-0.p...@n4.nabble.com>
Content-Type: text/plain; charset=us-ascii


Hi Glenn,

Thanks for your explanation about the "option domain-name" and
"ddns-domainname", So based on my network-level setup we configure this
values, these values can be same or can be different

And want to confirm one more point that the zone section will be added only
for the "ddns-domainname" value am i right ?

Thanks
Kraishak






--
Sent from: http://isc-dhcp-users.2343191.n4.nabble.com/


------------------------------

Message: 3
Date: Fri, 2 Apr 2021 10:12:46 +0100
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: DDNS updates for zone having multiple primary servers
Message-ID: <2fc63942-cc7e-4a96-b762-19ea3ab5e...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii

kraishak <kraishak....@gmail.com> wrote:

> Thanks for your explanation about the "option domain-name" and
> "ddns-domainname", So based on my network-level setup we configure this
> values, these values can be same or can be different

Correct

> And want to confirm one more point that the zone section will be added only
> for the "ddns-domainname" value am i right ?

I don't quite understand the question here, however ...

The process the server will take is roughly :

Client gets a lease, the server will take it's hostname (whether provided by 
the client, or provided by the config (e.g. in a host declaration)) and join it 
with ddns-domainname to form a FQDN for the client.

IFF an existing lease record indicates that DNS updates have already been done 
for this client&FQDN (and the server hasn't been told to always do updates), 
then that's it. Otherwise ...

It will then lookup the primary server for the client's domain. If there is a 
matching zone statement, then it will use the primary server specification 
given there, if not then it will do a DNS lookup for the SOA record of the zone 
and use the primary server specified in that.

The server will then attempt to do the DNS updates, which may fail if there are 
clashes or stale data in the zone.


Simon



------------------------------

Message: 4
Date: Fri, 2 Apr 2021 05:26:05 -0500 (CDT)
From: kraishak <kraishak....@gmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: DDNS updates for zone having multiple primary servers
Message-ID: <1617359165426-0.p...@n4.nabble.com>
Content-Type: text/plain; charset=us-ascii


Hi Simon 
Thanks for reply,
>>I don't quite understand the question here, however ...
--->I am clear with zone section now, but have a doubt with domain-name
fields

> Thanks for your explanation about the "option domain-name" and
> "ddns-domainname", So based on my network-level setup we configure this
> values, these values can be same or can be different

>>>>Correct
Regarding this, I am sorry I didn't complete my question, Actually my doubt
was can we configure like below
subnet 192.168.0.0 netmask 255.255.255.0 {
        pool {
                range 192.168.0.50 192.168.0.150;
               
        }
               ddns-domainname "example.com";
                option domain-name "test.com";
                option routers 192.168.0.1;
                option subnet-mask 255.255.255.0;
        }

        zone example.com.
        {
            primary 192.168.0.45;
            secondary 192.168.0.47,192.168.0.48;
        }
 i.e  option domain-name is different and ddns-domainname is totally
different not like domain and sub-domain concept
I checked the dhcpd syntax it is not giving any error but want to cross
check is this can be a valid configuration?

Thanks 
Kraishak




--
Sent from: http://isc-dhcp-users.2343191.n4.nabble.com/


------------------------------

Subject: Digest Footer

_______________________________________________
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 150, Issue 2
******************************************

Reply via email to