Author Topic: DNS error after update  (Read 1098 times)

nexter16

  • Zen Apprentice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
DNS error after update
« on: December 02, 2020, 10:29:20 am »
Hi, i have problem with the dns, if i manually add gw and dns then i can ping google, but if i restart it i cannot ping beacuse there is no gateway and dns.

when i want to change the dns forward settings i got this error
The following modules failed while saving their changes, their state is unknown: dns


the log:

Code: [Select]
Command output: .
Exit value: 1 at root command set -e
cp /etc/resolvconf/interface-order /var/lib/zentyal/tmp/resolvnoAq9D
echo zentyaldns.temp > /etc/resolvconf/interface-order
echo 'nameserver 127.0.0.1' | resolvconf -a zentyaldns.temp failed.
Error output: run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3
 run-parts: /etc/resolvconf/update.d/libc exited with return code 1

Command output: .
Exit value: 1 at /usr/share/perl5/EBox/Sudo.pm line 240
EBox::Sudo::_rootError('/usr/bin/sudo -p sudo: /var/lib/zentyal/tmp/GzpXTJHvqc.cmd 2> /var/lib/zentyal/tmp/stderr', 'set -e^Jcp /etc/resolvconf/interface-order /var/lib/zentyal/tmp/resolvn$
EBox::Sudo::_root(1, 'cp /etc/resolvconf/interface-order /var/lib/zentyal/tmp/resolvnoAq9D', 'echo zentyaldns.temp > /etc/resolvconf/interface-order', 'echo \'nameserver 127.0.0.1\' | reso$
EBox::Sudo::root('cp /etc/resolvconf/interface-order /var/lib/zentyal/tmp/resolvnoAq9D', 'echo zentyaldns.temp > /etc/resolvconf/interface-order', 'echo \'nameserver 127.0.0.1\' | resolvco$
EBox::DNS::_postServiceHook('EBox::DNS=HASH(0x5ed5648)', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 944
EBox::Module::Service::_regenConfig('EBox::DNS=HASH(0x5ed5648)') called at /usr/share/perl5/EBox/Module/Base.pm line 234
eval {...} at /usr/share/perl5/EBox/Module/Base.pm line 233
EBox::Module::Base::save('EBox::DNS=HASH(0x5ed5648)') called at /usr/share/perl5/EBox/GlobalImpl.pm line 648
eval {...} at /usr/share/perl5/EBox/GlobalImpl.pm line 647
EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x4dadff8)', 'progress', 'EBox::ProgressIndicator=HASH(0x4d50078)') called at /usr/share/perl5/EBox/Global.pm line 95
EBox::Global::AUTOLOAD('EBox::Global=HASH(0x4d500d8)', 'progress', 'EBox::ProgressIndicator=HASH(0x4d50078)') called at /usr/share/zentyal/global-action line 32
eval {...} at /usr/share/zentyal/global-action line 30
2020/12/01 14:04:02 ERROR> GlobalImpl.pm:652 EBox::GlobalImpl::saveAllModules - Failed to save changes in module dns: root command set -e
cp /etc/resolvconf/interface-order /var/lib/zentyal/tmp/resolvnoAq9D
echo zentyaldns.temp > /etc/resolvconf/interface-order
echo 'nameserver 127.0.0.1' | resolvconf -a zentyaldns.temp failed.
Error output: run-parts: /etc/resolvconf/update-libc.d/squid exited with return code 3
 run-parts: /etc/resolvconf/update.d/libc exited with return code 1

i did manually add dns and gw and now i can install the updates but still not working.

azharoth71

  • Zen Apprentice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Re: DNS error after update
« Reply #1 on: August 21, 2021, 12:11:59 pm »
same problem

turalyon

  • Zen Monk
  • **
  • Posts: 83
  • Karma: +11/-0
    • View Profile
Re: DNS error after update
« Reply #2 on: August 23, 2021, 10:58:53 am »
If you are not using the HTTP Proxy module, just remove the module or move the configuration file '/etc/resolvconf/update-libc.d/squid'. After that, try to restart the network module and check if the issue is fixed.

nexter16

  • Zen Apprentice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: DNS error after update
« Reply #3 on: September 15, 2021, 01:48:05 pm »
Thanks it works!

pksings

  • Zen Apprentice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: DNS error after update
« Reply #4 on: October 21, 2021, 02:03:33 am »
This fixed mine, it was really an IDS/IPS problem.

After some hours of research we found that in file "/etc/init.d/suricata" (date of 2nd March 2021) the line 68 was as following:
LISTEN_OPTIONS=" $NFQUEUE"
but it has to be
LISTEN_OPTIONS=" -q $NFQUEUE"
After correcting this and restarting the system, the module behaves as expected as far as we can see.