[Samba] howto test ddns
steve at steve-ss.com
Sat Aug 2 09:58:42 MDT 2014
On Sat, 2014-08-02 at 15:37 +0100, Rowland Penny wrote:
> On 02/08/14 15:14, steve wrote:
> > On Sat, 2014-08-02 at 14:47 +0100, shadrock uhuru wrote:
> >> hi Steve
> >>> On Sat, 2014-08-02 at 06:02 +0100, shadrock uhuru wrote:
> >>>> / hi
> >>> />/
> >>> />/ please could we start all over again,
> >>> /Yes. No problem.
> >>>> / ashanti is the AD DC with a static address of 10.2.1.6.
> >>> />/ testserver.tissisat.co.uk is a ficticous server to test the ddns update
> >>> />/ with.
> >>> />/ i have assumed that the server line in the nsupdate command is for the
> >>> />/ dns server i.e. the AD DC
> >>> /
> >>> OK, nearly there. _Where_ are you performing the nsupdate command?
> >>> Cheers,
> >>> Steve
> >> i have performed the nsupdate on ashanti (AD DC),
> > Hi
> > Please have a think about this. You have quite rightly assigned a static
> > IP to your DC. You must _not_ perform the ddns update there! It does not
> > and should not move from that IP. Ever. The reason for having ddns
> > updates is so that DNS can keep track of the client machines you have
> > joined to the domain. These machines (usually for convenience) receive
> > their IP via dhcp.
> I think that what you mean is:
> The DC must have a fixed ipaddress and as such, you should not use
> nsupdate or anything else to reset the DC's ipaddress. You can run
> nsupdate on the DC, but never to update the DC itself.
Yes, thanks for the translation. That's it. What we don't understand is
what the OP is trying to update as he doesn't have any clients that need
updating. Maybe he has dhcp on the DC too and will update in situ? But
wait, this originated as a sssd ddns update problem. Anyway, it's far
too hot over here for surmising. Everyone else has gone to the bar:(
> >> i have no client configured yet.
> > OK. Time to configure one, install sssd with the ad backend and test
> > ddns and nsupdate from there.
> > HTH
> > Steve
> >> shadrock
More information about the samba