search for: resolvconf

>It seems that you cannot create a new /etc/resolv.conf .. Did you remove resolvconf with apt-get remove --purge resolvconf? That should have restored the static resolv.conf back. Or just make use of resolvconf, Debian/ubuntu : just correctly configure interfaces. /etc/network/interfaces auto eth0 allow-hotplug eth0 iface eth0 inet static address 10.0.0.11 netmask 255.2...

On 2017-05-08 10:39, Rowland Penny via samba wrote: > On Mon, 8 May 2017 16:50:55 +0200 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > It seems that you cannot create a new /etc/resolv.conf .. > Did you remove resolvconf with apt-get remove --purge resolvconf? > That should have restored the static resolv.conf back. Well no, I didn't, but then again this was on Centos 7.3, it wasn't anything to do with resolvconf, I couldn't create any new file in /etc. I just wanted to test something so, more out...

On 11/05/2015 12:14 PM, Reindl Harald wrote: > > > Am 05.11.2015 um 18:08 schrieb Steve Ankeny: >> 'network-manager' is not installed but 'resolvconf' is -- >> >> adam at eagle:~$ cat /etc/resolv.conf >> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by >> resolvconf(8) >> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN >> nameserver 192.168.121.149 >> search sm...

...twork/interfaces' (instead of 'resolv.conf') -- > > Don't believe Ubuntu :-D > > Is this on the DC ? if so, can I suggest 'apt-get purge network-manager' > > This will remove Network Manager (you don't need it on a machine with > a fixed IP) > If resolvconf is installed, I would also remove this. > > Set /etc/resolv.conf to point to itself: > > search smbdomain.com > nameserver 127.0.0.1 # or you could use the DCs IP > 'network-manager' is not installed but 'resolvconf' is -- adam at eagle:~$ cat /etc/resolv.conf #...

Hello, Seems that file ressource gets a new idea of what to be given. I have the following recipe : class resolvconf { file { "/etc/resolv.conf": owner => root, group => wheel, mode => 644, source => "puppet:///puppet/dist/resolv.conf", } } When doin...

...ba.org> wrote: > > On 2017-05-08 10:39, Rowland Penny via samba wrote: > > On Mon, 8 May 2017 16:50:55 +0200 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > It seems that you cannot create a new /etc/resolv.conf .. > Did you remove resolvconf with apt-get remove --purge resolvconf? > That should have restored the static resolv.conf back. > Well no, I didn't, but then again this was on Centos 7.3, it wasn't > anything to do with resolvconf, I couldn't create any new file > in /etc. > > I just wanted to te...

...< samba at lists.samba.org> wrote: > On Thu, 2 May 2019 16:51:02 -0400 > James Fowler <fowlerj at adst.org> wrote: > > See inline comments > > > root at DC2:~# cat /etc/resolv.conf > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > > resolvconf(8) > > # and managed by Zentyal. > > # > > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE > > OVERWRITTEN # > > nameserver 192.168.1.254 > > #search domain1.domain > I would do two things here, the first is 'apt-get purge resolvconf', >...

..., 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 the network service. But I > still get long timeouts and can't login via ssh, when I suspend my 1st DC. > > # c...

...> > On Thu, 2 May 2019 16:51:02 -0400 > > James Fowler <fowlerj at adst.org> wrote: > > > > See inline comments > > > > > root at DC2:~# cat /etc/resolv.conf > > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > > > resolvconf(8) > > > # and managed by Zentyal. > > > # > > > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE > > > OVERWRITTEN # > > > nameserver 192.168.1.254 > > > #search domain1.domain > > > I would do two things here, the first...

On 05/11/15 18:40, Steve Ankeny wrote: > On 11/05/2015 12:14 PM, Reindl Harald wrote: >> >> >> Am 05.11.2015 um 18:08 schrieb Steve Ankeny: >>> 'network-manager' is not installed but 'resolvconf' is -- >>> >>> adam at eagle:~$ cat /etc/resolv.conf >>> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by >>> resolvconf(8) >>> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN >>> nameserver 192.168.12...

...gt; On 2017-05-08 10:39, Rowland Penny via samba wrote: > > > On Mon, 8 May 2017 16:50:55 +0200 > > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > > > It seems that you cannot create a new /etc/resolv.conf .. > > Did you remove resolvconf with apt-get remove --purge resolvconf? > > That should have restored the static resolv.conf back. > > Well no, I didn't, but then again this was on Centos 7.3, it wasn't > anything to do with resolvconf, I couldn't create any new file > in /etc. > > I just wa...

...gt;> On 2017-05-08 10:39, Rowland Penny via samba wrote: >> >> On Mon, 8 May 2017 16:50:55 +0200 >> "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: >> >> It seems that you cannot create a new /etc/resolv.conf .. >> Did you remove resolvconf with apt-get remove --purge resolvconf? >> That should have restored the static resolv.conf back. >> Well no, I didn't, but then again this was on Centos 7.3, it wasn't >> anything to do with resolvconf, I couldn't create any new file >> in /etc. >> >&gt...

...to also. With squid 4.8 on buster, ( hint : repo buster-squid48 ssl enabled ) What a dragon this was, strongswan is last what im on now. If someone has a strongswan setup with user/ldap auth, pm me your config ;-) Ok, what you posted below. pre01svdeb03 : apt-get remove --purge --auroremove resolvconf Old dc: pre01svdeb02 : apt-get remove --purge --auroremove resolvconf Make these changes/verify them after the remove of resolvconf pre01svdeb03 /etc/resolv.conf search pilsbacher.at nameserver 192.168.16.206 nameserver 192.168.16.205 pre01svdeb02 /etc/resolv.conf search pilsbacher.at namese...

...rs > The 192.168.0.3 line should be: 192.168.0.3 dc1.biuro.gsbk.pl dc1 Provided, of course, that DC1 has a fixed IP and it should have a fixed IP > */etc/hostname* > > DC1 > > */etc/resolv.conf* > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE > OVERWRITTEN nameserver 192.168.0.3 > search biuro.gsbk.pl > I personally would remove resolvconf, it is totally unneeded on a machine with a fixed IP Rowland

...ur 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 the network service. But I still get long timeouts and can't login via ssh, when I suspend my 1st DC. # cat /etc/resolvconf/resolv.conf.d/...

...s > > > 172.30.9.1 khorshid > 127.0.0.1 printmah.jasondomain.jj printmah localhost localhost.localdomain localhost4 localhost4.localdomain4 > ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 > > +++++++++++++++++++++++++++++++++++++++ > > /etc/init.d/resolvconf > > [root at printmah ~]# cat /etc/init.d/resolvconf > cat: /etc/init.d/resolvconf: No such file or directory > > [root at printmah ~]# cat /etc/resolv.conf > # Generated by NetworkManager > domain jasondomain.jj > search jasondomain.jj > nameserver 172.30.9.1 > namese...

...86400 ;; Query time: 17 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Wed Feb 04 17:05:19 PST 2015 ;; MSG SIZE rcvd: 120 nikola var # cat resolv.conf cat: resolv.conf: No such file or directory nikola var # cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 nikola var # man resolvconf(8) bash: syntax error near unexpected token `(' nikola var # man resolvconf nikola var # dig nikola.ozco.home ; <<>> DiG 9.9.5-3ubuntu0.1-Ubuntu <<>&...

Hello James, To your questions: *"Are DC1 and DC2 in the same geographical location?"* Yes, they are in same location, & they are in the same subnet as well. *"I'm also unclear from your message if you are still having password issues or not."* **It appears to have been resolved. When we randomly checked, users were able to change their passwords. However

...) > > What a dragon this was, strongswan is last what im on now. > > If someone has a strongswan setup with user/ldap auth, pm > me your config ;-) > > > > > > Ok, what you posted below. > > > > pre01svdeb03 : apt-get remove --purge --auroremove resolvconf > > Old dc: pre01svdeb02 : apt-get remove --purge --auroremove > resolvconf > > > > Make these changes/verify them after the remove of resolvconf > > > > pre01svdeb03 > > /etc/resolv.conf > > search pilsbacher.at > > nameserver 192.168.16.20...

root at DC2:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # and managed by Zentyal. # # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # nameserver 192.168.1.254 #search domain1.domain /etc/hostname cat /etc/hostname DC2 /etc/hosts root at DC2:~cat /etc/hosts 127.0.0.1 localhost.localdomain localhost 127.0.1.1 DC2.D...