search for: ip_of_1stdc

...THORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;_ldap._tcp.gc._msdcs.my.domain.tld. IN SRV ;; ANSWER SECTION: _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 dc1.my.domain.tld. _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 dc2.my.domain.tld. ;; Query time: 1 msec ;; SERVER: IP_of_1stDC#53(IP_of_1stDC) ;; WHEN: Thu Dec 17 13:28:06 2015 ;; MSG SIZE rcvd: 103 So, how do I get rid of this problematic record for my DC2?

...ld. IN SRV >> >> ;; ANSWER SECTION: >> _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >> dc1.my.domain.tld. >> _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >> dc2.my.domain.tld. >> >> ;; Query time: 1 msec >> ;; SERVER: IP_of_1stDC#53(IP_of_1stDC) >> ;; WHEN: Thu Dec 17 13:28:06 2015 >> ;; MSG SIZE rcvd: 103 >> >> >> So, how do I get rid of this problematic record for my DC2? >> >> > > Hi Ole, can you identify the DN of the record you want to remove? One way would be with ldbe...

...>> _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >>>> dc1.my.domain.tld. >>>> _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >>>> dc2.my.domain.tld. >>>> >>>> ;; Query time: 1 msec >>>> ;; SERVER: IP_of_1stDC#53(IP_of_1stDC) >>>> ;; WHEN: Thu Dec 17 13:28:06 2015 >>>> ;; MSG SIZE rcvd: 103 >>>> >>>> >>>> So, how do I get rid of this problematic record for my DC2? >>>> >>>> >>> >>> >> >> Hi...

...IN SRV 0 100 3268 >>>>>> dc1.my.domain.tld. >>>>>> _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >>>>>> dc2.my.domain.tld. >>>>>> >>>>>> ;; Query time: 1 msec >>>>>> ;; SERVER: IP_of_1stDC#53(IP_of_1stDC) >>>>>> ;; WHEN: Thu Dec 17 13:28:06 2015 >>>>>> ;; MSG SIZE rcvd: 103 >>>>>> >>>>>> >>>>>> So, how do I get rid of this problematic record for my DC2? >>>>>> >>>>...

...t; ;_ldap._tcp.gc._msdcs.my.domain.tld. IN SRV > > ;; ANSWER SECTION: > _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 > dc1.my.domain.tld. > _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 > dc2.my.domain.tld. > > ;; Query time: 1 msec > ;; SERVER: IP_of_1stDC#53(IP_of_1stDC) > ;; WHEN: Thu Dec 17 13:28:06 2015 > ;; MSG SIZE rcvd: 103 > > > So, how do I get rid of this problematic record for my DC2? > >

...;; ANSWER SECTION: >>> _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >>> dc1.my.domain.tld. >>> _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >>> dc2.my.domain.tld. >>> >>> ;; Query time: 1 msec >>> ;; SERVER: IP_of_1stDC#53(IP_of_1stDC) >>> ;; WHEN: Thu Dec 17 13:28:06 2015 >>> ;; MSG SIZE rcvd: 103 >>> >>> >>> So, how do I get rid of this problematic record for my DC2? >>> >>> >> >> > > Hi Ole, can you identify the DN of the record y...

...msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >>>>> dc1.my.domain.tld. >>>>> _ldap._tcp.gc._msdcs.my.domain.tld. 180 IN SRV 0 100 3268 >>>>> dc2.my.domain.tld. >>>>> >>>>> ;; Query time: 1 msec >>>>> ;; SERVER: IP_of_1stDC#53(IP_of_1stDC) >>>>> ;; WHEN: Thu Dec 17 13:28:06 2015 >>>>> ;; MSG SIZE rcvd: 103 >>>>> >>>>> >>>>> So, how do I get rid of this problematic record for my DC2? >>>>> >>>>> >>>> &g...

Am 17.12.2015 um 14:32 schrieb Rowland penny: > On 17/12/15 12:50, Ole Traupe wrote: >> >> I somehow doubt that. Still it seems that no one here has an idea of >> why log-on from member servers isn't working properly (for me). >> However, in the meantime I have created all the necessary DNS >> records. This can't be the issue anymore. >> >>

On 10/12/15 15:13, Ole Traupe wrote: > > > Am 10.12.2015 um 15:49 schrieb Rowland penny: >> 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