search for: ntp2

Hello everyone, I have problem with time delaying on my CentOS powered server. I have tried to set time in BIOS and in OS (with saving time to BIOS), but time still delaying, so after month is about five minutes delayed. In past I was using this box with Windows and there wasn?t this time problem, but I cant warrant, that there are no hardware issues. So I was decided, that easiest way to fix

...Settings ======================== Some of the settings, such as which log server to use, can be specified by the user. Below is a sample hiera file containing all the current configurable settings: cis::logserver: ''syslog.localdomain'' cis::ntpserver: - ntp1 - ntp2 - ntp3 cis::aide_cron_check: hour: 6 minute: 30 Author ====== Written by Arild Jensen <ajensen@counter-attack.com> with source code repository at https://github.com/arildjensen/cis-puppet. Release History =============== - 0.2.0 - Added comments and implemented hiera...

Hi, I''m not a total newbie with puppet, but I only use it for a few things and I''m not even using modules yet, mostly because I only deploy configuration files for now. I have a configuration for NTP that looks like this: class ntpd { package { "ntp": ensure => installed, } file { "/etc/ntp.conf": owner => root,

...eed/want. ( example 192.168.1.11 ) > PTR : 11.0.168.192.in-addr.arpa > CNAME : dc1 ns1 ldap1 ntp1 > > Hostname : sam-dc2.internal.domain.tld > IP : what you need/want. ( example 192.168.1.12 ) > PTR : 12.0.168.192.in-addr.arpa > CNAME : dc1 ns2 ldap2 ntp2 > > For a MEMBER. > Hostname.FQDN.TLD : max 254chars, incl the .'s allowed chars: a-Z 0-9 - > Hostname : sam-mem1.internal.domain.tld > IP : what you need/want. ( example 192.168.1.21 ) > PTR : 21.0.168.192.in-addr.arpa > CNAME : fs1 (fileserver1) > Bu...

We are not much off. But you have mixed "samba/window" and "windows/windows" settings. Samba/windows \\%logonserver%\home\%username%\desktop Windows/windows \\hostname.fqdn.tld\users\%username%\desktop Guess, which one i use. ;-) Now, do get where this is coming from. So use this (add CNAME for you member server ), Note, you MUST setup PTR records.

...rver it a must imo. You might need to sync a hardware clock also, because if the hardware clock gets more then 5 min out of sync. You might end up en some strang problem. And do note, NTP Server is only needed on the DC,s members, just point them to the DC. Better imo, add CNAME ntp1 to dc1 and ntp2 to dc2 and use the ntp1/2 .domain.tld names in the configs. Now, if you want another ntp, just change the cname endpoint. sudo dpkg-reconfigure tzdata If you setup correct, the base install would have handled that and a dpkg-reconfigure should not be needed. being picky here, since you wanted t...

...1.11 ) >> PTR : 11.0.168.192.in-addr.arpa >> CNAME : dc1 ns1 ldap1 ntp1 >> >> Hostname : sam-dc2.internal.domain.tld >> IP : what you need/want. ( example 192.168.1.12 ) >> PTR : 12.0.168.192.in-addr.arpa >> CNAME : dc1 ns2 ldap2 ntp2 >> >> For a MEMBER. >> Hostname.FQDN.TLD : max 254chars, incl the .'s allowed chars: a-Z 0-9 - >> Hostname : sam-mem1.internal.domain.tld >> IP : what you need/want. ( example 192.168.1.21 ) >> PTR : 21.0.168.192.in-addr.arpa >> CNAME...

...ll my setups. As example. REALM : INTERNAL.EXAMPLE.COM FQDN : test-dc1.internal.example.com Hostname: test-dc1 SPN HOST/TEST-DC1 SPN HOST/test-dc1.internal.example.com A test-dc1 PTR 192.168.1.1 ZONE internal.example.com What works. ZONE internal.example.com CNAME ntp1 => test-dc1 CNAME ntp2 => test-dc2 CNAME PDC => test-dc1 ! NOTE, NOT PDC from Primary Domain Controller in NT4.0 domains, Just primary ( the one with FSMO ) CNAME BDC1 => test-dc2 ! NOTE, NOT BDC from BACKUP Domain Controller in NT4.0 domains, Just an extra DC CNAME BDC2 => test-dc2 ! NOTE, NOT BDC fro...

...ch backend that is, there can even be several of them. To enable add the backend `puppetdb`to the backends list in `hiera.yaml`. So instead of writing something like this in for example your `hiera-data/common.yaml`: ntp::servers: - ''ntp1.example.com'' - ''ntp2.example.com'' You can now instead write: ntp::servers::_nodequery: ''Class[Ntp::Server]'' It will then find all nodes with the class ntp::server and return an array containing their certname. If you instead want to return the value of a fact, for example the `ipaddres...

...c1.internal.domain.tld IP : what you need/want. ( example 192.168.1.11 ) PTR : 11.0.168.192.in-addr.arpa CNAME : dc1 ns1 ldap1 ntp1 Hostname : sam-dc2.internal.domain.tld IP : what you need/want. ( example 192.168.1.12 ) PTR : 12.0.168.192.in-addr.arpa CNAME : dc1 ns2 ldap2 ntp2 For a MEMBER. Hostname.FQDN.TLD : max 254chars, incl the .'s allowed chars: a-Z 0-9 - Hostname : sam-mem1.internal.domain.tld IP : what you need/want. ( example 192.168.1.21 ) PTR : 21.0.168.192.in-addr.arpa CNAME : fs1 (fileserver1) But also and this is just how may servers yo...

...: 11.0.168.192.in-addr.arpa >>> CNAME : dc1 ns1 ldap1 ntp1 >>> >>> Hostname : sam-dc2.internal.domain.tld >>> IP : what you need/want. ( example 192.168.1.12 ) >>> PTR : 12.0.168.192.in-addr.arpa >>> CNAME : dc1 ns2 ldap2 ntp2 >>> >>> For a MEMBER. >>> Hostname.FQDN.TLD : max 254chars, incl the .'s allowed chars: a-Z 0-9 - >>> Hostname : sam-mem1.internal.domain.tld >>> IP : what you need/want. ( example 192.168.1.21 ) >>> PTR : 21.0.168.192.in-add...

Does anyone have any suggestions about how to deal with multiple environments/tiers? For instance, we have several environments ( production, dev, qa, etc.. ) and within each environment, different tiers ( web, data, app, etc ). Each tier is a different IP network segment, so all the hosts in each tier have different configurations for certain things like resolv.conf, ntp.conf and so on. We do

Hello, we successfully migrated from a Samba 3.x NT Domain to a Samba AD Domain using Samba 4.7.x. However, there are still some issues and I hope for your help. The biggest problem so far follows: For historical reasons our Samba file servers carry a lot of aliases. Now that they have become AD Members I did set a lot of CNAMEs in the AD DNS (using the Windows DNS Tool). Most of the aliases

...802.3ad MIIMonitorSec=1s #LACPTransmitRate=fast #UpDelaySec=2s #DownDelaySec=8s #TransmitHashPolicy=layer2 #TransmitHashPolicy=layer3+4 # /etc/systemd/network/30-bond1.network [Match] Name=bond1 [Network] DNS=192.168.1.2 DNS=192.168.1.1 Domains=internal.domain.tld NTP=ntp1.internal.domain.tld NTP=ntp2.internal.domain.tld # ntp1 and 2 are CNAMES to DC1 DC2. [Address] Address=192.168.1.11/24 [Route] Destination=0.0.0.0/0 Gateway=192.168.1.252 Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via...

Am 22.02.19 um 12:16 schrieb L.P.H. van Belle via samba: > Hai, > > Well, i did some extra checking, gone throug more logs. > ... Nothing. No errors. Sorry, i cant find anything.. > > Almost all my server run unattended updates, execpt the DC's. > > I had a few that where waiting for a reboot tomorrow night, all now rebooted, > and no problems before and

Hi, I have upgraded my Dell C151 to the latest 5.6. I have always used ntp to sync this machine and then the rest of the machines in the network would sync from it. Since the update I cannot keep the right time on the machine. This is with / without ntp. I have attempted various scenario's with no luck. I am now trying the old kernel now as I type this out. If anyone else has any

Hai Gregory,   No problem, now netplan, but i cant tell you much about netplan out of experiance, i've never used it. But what is it exact you want to know?? The how and why i configure like this is already a bit explained.   about this part: > So, I'm curious about the contrast between modifying netplan vs simply disabling systemd.resolved   But I did a bit reading.

...l for me. Very importent is that "old" entries are gone before you join the new But again above is a suggestion, i think you save time by doing a new correct install. And a tip, dont use any ip anyware for accessing server services. For example, ntp1.domain.tld CNAME DC1.domain.tld ntp2.domain.tld CNAME DC2.domain.tld ns1.domain.tld CNAME DC1.domain.tld ns2.domain.tld CNAME DC2.domain.tld ldap1.domain.tld CNAME DC1.domain.tld ldap2.domain.tld CNAME DC2.domain.tld now for an easy switch, also add ntp.domain.tld CNAME ntp1.domain.tld ldap.domain.tld CNAME ldap1.domain.tld so if...

..."old" entries are gone before you join the new > > But again above is a suggestion, i think you save time by doing a new > correct install. > > And a tip, dont use any ip anyware for accessing server services. > For example, > ntp1.domain.tld CNAME DC1.domain.tld > ntp2.domain.tld CNAME DC2.domain.tld > ns1.domain.tld CNAME DC1.domain.tld > ns2.domain.tld CNAME DC2.domain.tld > ldap1.domain.tld CNAME DC1.domain.tld > ldap2.domain.tld CNAME DC2.domain.tld > > now for an easy switch, also add > ntp.domain.tld CNAME ntp1.domain.tld > ldap.doma...

On 10/12/15 14:40, Ole Traupe wrote: > >>> However, my 2nd DC is not that new, I restarted it many times, just >>> again (samba service). No DNS records are created anywhere. >>> >>> If I go through the DNS console, in each and every container there >>> is some entry for the 1st DC, but none for the 2nd (except on the >>> top levels: FQDN