search for: ip_of_2nd_dc

...ilable DNS servers >>>> on your workstations? As well as your member server? >>> Yes, of course. For member servers, this is the content of >>> /etc/resolv.conf: >>> >>> search my.domain.tld >>> nameserver IP_of_1st_DC >>> nameserver IP_of_2nd_DC >>> >>> >>>> I made a small tweak but haven't fully tested is adding the following >>>> options to my resolv.conf. >>>> >>>> cat /etc/resolvconf/resolv.conf.d/tail >>>> options timeout:1 >>> Great, this sound...

...t; >>> >>> >> >> Possibly, but can you try this on your second DC, run >> 'samba_dnsupdate --verbose' >> >> Rowland >> > > Doesn't look too good to me: > > > [root at DC2 me]# samba_dnsupdate --verbose > IPs: ['IP_of_2nd_DC'] > Looking for DNS entry A DC2.my.domain.tld IP_of_2nd_DC as > DC2.my.domain.tld. > Looking for DNS entry A my.domain.tld IP_of_2nd_DC as my.domain.tld. > Failed to find matching DNS entry A my.domain.tld IP_of_2nd_DC > Looking for DNS entry SRV _ldap._tcp.my.domain.tld DC2.my....

On 10/12/15 14:00, Ole Traupe wrote: > > > Am 10.12.2015 um 14:38 schrieb Rowland penny: >> On 10/12/15 13:25, Ole Traupe wrote: >>> Is it possible that kdc server is always the SOA, at least if >>> derived from DNS and not specified *explicitly* in the krb5.conf? >>> >>> In my DNS-Manager console I find that >>> >>>

...e prior 1st DC (with >> the same IP address)? >> >> >> > > Possibly, but can you try this on your second DC, run 'samba_dnsupdate > --verbose' > > Rowland > Doesn't look too good to me: [root at DC2 me]# samba_dnsupdate --verbose IPs: ['IP_of_2nd_DC'] Looking for DNS entry A DC2.my.domain.tld IP_of_2nd_DC as DC2.my.domain.tld. Looking for DNS entry A my.domain.tld IP_of_2nd_DC as my.domain.tld. Failed to find matching DNS entry A my.domain.tld IP_of_2nd_DC Looking for DNS entry SRV _ldap._tcp.my.domain.tld DC2.my.domain.tld 389 as _ldap._...

...t;> Possibly, but can you try this on your second DC, run >>> 'samba_dnsupdate --verbose' >>> >>> Rowland >>> >> >> Doesn't look too good to me: >> >> >> [root at DC2 me]# samba_dnsupdate --verbose >> IPs: ['IP_of_2nd_DC'] >> Looking for DNS entry A DC2.my.domain.tld IP_of_2nd_DC as >> DC2.my.domain.tld. >> Looking for DNS entry A my.domain.tld IP_of_2nd_DC as my.domain.tld. >> Failed to find matching DNS entry A my.domain.tld IP_of_2nd_DC >> Looking for DNS entry SRV _ldap._tcp.m...

...bytes) to my.domain.tld [25433] 1452162734.434842: Resolving hostname dc2.my.domain.tld. [25433] 1452162739.441465: Sending initial UDP request to dgram IP_of_1st_DC:88 [25433] 1452162740.442397: Resolving hostname dc3.my.domain.tld. [25433] 1452162745.448521: Sending initial UDP request to dgram IP_of_2nd_DC:88 [25433] 1452162745.457681: Received answer from dgram IP_of_2nd_DC:88 [25433] 1452162750.463572: Response was not from master KDC [25433] 1452162750.463632: Received error from KDC: -1765328359/Additional pre-authentication required [25433] 1452162750.463730: Processing preauth types: 16, 15, 2...

...ond DC, run > >>> 'samba_dnsupdate --verbose' > >>> > >>> Rowland > >>> > >> > >> Doesn't look too good to me: > >> > >> > >> [root at DC2 me]# samba_dnsupdate --verbose > >> IPs: ['IP_of_2nd_DC'] > >> Looking for DNS entry A DC2.my.domain.tld IP_of_2nd_DC as > >> DC2.my.domain.tld. > >> Looking for DNS entry A my.domain.tld IP_of_2nd_DC as my.domain.tld. > >> Failed to find matching DNS entry A my.domain.tld IP_of_2nd_DC > >> Looking for DN...

...your second DC, run >>>> 'samba_dnsupdate --verbose' >>>> >>>> Rowland >>>> >>> >>> Doesn't look too good to me: >>> >>> >>> [root at DC2 me]# samba_dnsupdate --verbose >>> IPs: ['IP_of_2nd_DC'] >>> Looking for DNS entry A DC2.my.domain.tld IP_of_2nd_DC as >>> DC2.my.domain.tld. >>> Looking for DNS entry A my.domain.tld IP_of_2nd_DC as my.domain.tld. >>> Failed to find matching DNS entry A my.domain.tld IP_of_2nd_DC >>> Looking for DNS en...

...pdate --verbose' > > >>> > > >>> Rowland > > >>> > > >> > > >> Doesn't look too good to me: > > >> > > >> > > >> [root at DC2 me]# samba_dnsupdate --verbose > > >> IPs: ['IP_of_2nd_DC'] > > >> Looking for DNS entry A DC2.my.domain.tld IP_of_2nd_DC as > > >> DC2.my.domain.tld. > > >> Looking for DNS entry A my.domain.tld IP_of_2nd_DC as my.domain.tld. > > >> Failed to find matching DNS entry A my.domain.tld IP_of_2nd_DC > &gt...

...;> Rowland, as everything else are defaults): >>> >>> [libdefaults] >>> default_realm = MY.DOMAIN.TLD >>> >>> And my /etc/resolv.conf is this: >>> >>> search my.domain.tld >>> nameserver IP_of_1st_DC >>> nameserver IP_of_2nd_DC >> >> Any idea why I still get this when trying to log on to a member >> server while the first DC is down? >> >> # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while >> getting initial credentials >> >> Ole >> >> >...

...gt; > My /etc/krb5.conf looks like this (following your suggestions, > Rowland, as everything else are defaults): > > [libdefaults] > default_realm = MY.DOMAIN.TLD > > And my /etc/resolv.conf is this: > > search my.domain.tld > nameserver IP_of_1st_DC > nameserver IP_of_2nd_DC Any idea why I still get this when trying to log on to a member server while the first DC is down? # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while getting initial credentials Ole

...t to recap you do you both servers listed as available DNS servers > > on your workstations? As well as your member server? > > Yes, of course. For member servers, this is the content of > /etc/resolv.conf: > > search my.domain.tld > nameserver IP_of_1st_DC > nameserver IP_of_2nd_DC > > > > I made a small tweak but haven't fully tested is adding the following > > options to my resolv.conf. > > > > cat /etc/resolvconf/resolv.conf.d/tail > > options timeout:1 > > Great, this sounds exactly as what I need! However, I tried this: no...

Hi, I tested the AD (Samba4) domain log-in on Windows 7 clients and Linux member servers with my PDC being offline (plugged the cable). It is not working so well. On Windows it initially takes forever. It works again after rebooting the client, which seems to be the easiest solution (can be performed by the user). On Linux member servers, ssh log-in eventually times out. It works again,

...be the only solution. > > Just to recap you do you both servers listed as available DNS servers > on your workstations? As well as your member server? Yes, of course. For member servers, this is the content of /etc/resolv.conf: search my.domain.tld nameserver IP_of_1st_DC nameserver IP_of_2nd_DC > I made a small tweak but haven't fully tested is adding the following > options to my resolv.conf. > > cat /etc/resolvconf/resolv.conf.d/tail > options timeout:1 Great, this sounds exactly as what I need! However, I tried this: no effect. I created this file and restarted...

...gt; > My /etc/krb5.conf looks like this (following your suggestions, > Rowland, as everything else are defaults): > > [libdefaults] > default_realm = MY.DOMAIN.TLD > > And my /etc/resolv.conf is this: > > search my.domain.tld > nameserver IP_of_1st_DC > nameserver IP_of_2nd_DC > > > So from a Windows client point of view, I am more or less fine (even > without restarting the machines). But it would be great if I could > log-in to the Linux member servers as well. > > Ole > > > I am getting nearer, I can now add another NS record to the SO...

...IN.TLD' while getting initial credentials" My /etc/krb5.conf looks like this (following your suggestions, Rowland, as everything else are defaults): [libdefaults] default_realm = MY.DOMAIN.TLD And my /etc/resolv.conf is this: search my.domain.tld nameserver IP_of_1st_DC nameserver IP_of_2nd_DC So from a Windows client point of view, I am more or less fine (even without restarting the machines). But it would be great if I could log-in to the Linux member servers as well. Ole

...is (following your suggestions, >> Rowland, as everything else are defaults): >> >> [libdefaults] >> default_realm = MY.DOMAIN.TLD >> >> And my /etc/resolv.conf is this: >> >> search my.domain.tld >> nameserver IP_of_1st_DC >> nameserver IP_of_2nd_DC > > Any idea why I still get this when trying to log on to a member server > while the first DC is down? > > # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while > getting initial credentials > > Ole > > > Ole, I was trying to look back th...

...e defaults): >>>> >>>> [libdefaults] >>>> default_realm = MY.DOMAIN.TLD >>>> >>>> And my /etc/resolv.conf is this: >>>> >>>> search my.domain.tld >>>> nameserver IP_of_1st_DC >>>> nameserver IP_of_2nd_DC >>> >>> Any idea why I still get this when trying to log on to a member >>> server while the first DC is down? >>> >>> # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while >>> getting initial credentials >>> >&gt...

...e defaults): >>>> >>>> [libdefaults] >>>> default_realm = MY.DOMAIN.TLD >>>> >>>> And my /etc/resolv.conf is this: >>>> >>>> search my.domain.tld >>>> nameserver IP_of_1st_DC >>>> nameserver IP_of_2nd_DC >>> >>> Any idea why I still get this when trying to log on to a member >>> server while the first DC is down? >>> >>> # kinit: Cannot contact any KDC for realm 'MY.DOMAIN.TLD' while >>> getting initial credentials >>> >&gt...

...u both servers listed as available DNS servers >>> on your workstations? As well as your member server? >> Yes, of course. For member servers, this is the content of >> /etc/resolv.conf: >> >> search my.domain.tld >> nameserver IP_of_1st_DC >> nameserver IP_of_2nd_DC >> >> >>> I made a small tweak but haven't fully tested is adding the following >>> options to my resolv.conf. >>> >>> cat /etc/resolvconf/resolv.conf.d/tail >>> options timeout:1 >> Great, this sounds exactly as what I need! Howeve...