search for: dnses

Is it a temporary situation, because Yum no longer resolves this adress, then yum update fails... -- (?- Bernard Lheureux Gestionnaire des MailingLists ML, TechML, LinuxML //\ http://www.bbsoft4.org/Mailinglists.htm ** MailTo:root at bbsoft4.org v_/_ http://www.bbsoft4.org/ <<<<<< * >>>>>> http://www.portalinux.org/

...\nmytld\x02at\x00', 'D\x00\x06\x00\x05\xf0\x00\x00!\x96\t\x00\x00\x00\x0e\x10\x00\x00\x00\x00l\xef7\x00\x00\t\x96!\x00\x00\x03\x84\x00\x00\x02X\x00\x01Q\x80\x00\x00\x0e\x10\x12\x03\x02dc\nmytld\x02at\x00\x1a\x03\nhostmaster\nmytld\x02at\x00'] FAILED As far as I interpret, the 2 DCs/DNSes have different records for "dc.mytld.at", right? Could correcting this lead to proper replication again?

...really seems to be a routing problem (or firewall blocking), but I have no clue. The configuration is very simple: tincd.conf: Name = client1 ConnectTo = server hosts\client1: Subnet = 10.10.119.1/32 client1 tap tcp4 interface: IP: 10.10.119.1 Netmask: 255.255.0.0 Gateway: empty DNSes: empty server: 10.10.6.1 (10.10.6.0/24 on hosts). Any ideas? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20130607/89a62984/attachment.html>

...stigated this a bit, and I think that using 18.04 for the new DC will not be successful anyway. Reasons: the AD I have has been created back in the days when 14.04 LTS was fresh. The provisioning scripts worked differently. 14.04 has been upgraded to 16.04, and I think that I do not have all of the DNSes configured properly and this might be the cause of the synchronization items. I would really like to get to the bottom of this and understand the issue to fix it on the old DC. Is there a checklist on what needs to be done during the initial provisioning and what are the requirements for samba-too...

...altech.com. IN NS ns1.businessexprezz.com. NS: myportaltech.com. IN NS ns2.businessexprezz.com. The above myportaltech is just a fictitious name of my domain but I can provide the actual domain name if needed. After the above records have been propagated to all other DNSes, I test sending email from the same permitted domain, this time using domain name & the email never arrives & I did not receive a 'bounced mail' notification too. Then I test sending from the same domain to recipient_id@[202.6.163.31] & this time round, the test email never sho...

Really sorry about this, www.mjuware.com is still unstable (thanks Jan for pointing this out). Please continue using the mirror at http://www2.mjuware.com for now. The situation should be fixed within a day or so (time for the information to propagate across DNSes around the world...). And sorry for polluting your intray... Kind regards, Pyt. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/flac/attachments/20140912/e5e916e2/attachment.htm

Really sorry about this, www.mjuware.com is still unstable (thanks Jan for pointing this out). Please continue using the mirror at http://www2.mjuware.com for now. The situation should be fixed within a day or so (time for the information to propagate across DNSes around the world...). And sorry for polluting your intray... Kind regards, Pyt. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/flac/attachments/20140912/e5e916e2/attachment.htm

...9;, > 'D\x00\x06\x00\x05\xf0\x00\x00!\x96\t\x00\x00\x00\x0e\x10\x00\x00\x00\x00l\xef7\x00\x00\t\x96!\x00\x00\x03\x84\x00\x00\x02X\x00\x01Q\x80\x00\x00\x0e\x10\x12\x03\x02dc\nmytld\x02at\x00\x1a\x03\nhostmaster\nmytld\x02at\x00'] > FAILED > > As far as I interpret, the 2 DCs/DNSes have different records for > "dc.mytld.at", right? Yes, they are different. > > Could correcting this lead to proper replication again? Wouldn't hurt ;-) Rowland

...and I think that using 18.04 for the > new DC will not be successful anyway. Reasons: the AD I have has been > created back in the days when 14.04 LTS was fresh. The provisioning > scripts worked differently. 14.04 has been upgraded to 16.04, and I > think that I do not have all of the DNSes configured properly and > this might be the cause of the synchronization items. The basic provision has always worked in the same way, it has just been tweaked. > > I would really like to get to the bottom of this and understand the > issue to fix it on the old DC. Is there a checkl...

...ing 18.04 for the > > new DC will not be successful anyway. Reasons: the AD I have has been > > created back in the days when 14.04 LTS was fresh. The provisioning > > scripts worked differently. 14.04 has been upgraded to 16.04, and I > > think that I do not have all of the DNSes configured properly and > > this might be the cause of the synchronization items. > > The basic provision has always worked in the same way, it has just been > tweaked. > > > > > I would really like to get to the bottom of this and understand the > > issue to fix...

Am 13.03.19 um 17:13 schrieb Stefan G. Weichinger via samba: > Am 13.03.19 um 16:53 schrieb L.P.H. van Belle: >> Ok thats small, a dc should be rebooted within 1-2 min and 1-2 min really max for AD sync. one more observation: manually running this works: root at pre01svdeb03:~# samba-tool drs replicate dc PRE01SVDEB03 dc=blabla,dc=at --full-sync but the one user I created (and

Hi! I want to get down to the root cause of the issue I am having with my new DC in my domain. I have followed some tutorials on the internet and basically do not get the results. I have 1 old DC, that is providing the AD domain for the whole local network. I wanted to add another one. Both are Ubuntus 16.04, fully updated. I have followed this