NO DNS server on bootup

Bug #1813842 reported by Rae
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned

Bug Description

They tried to fix this with no help

I have to do the following everytime I boot to correct the DNS issue

sudo nano /etc/resolv.conf comment out the existing DNS

Add nameserver 8.8.8.8
nameserver 192.159.10.2

then

sudo service network-manager restart

I reboot a few times a day

without this I can ping 8.8.8.8 but not yahoo.com

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.29
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
Uname: Linux 4.15.0-44-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 29 14:32:23 2019
InstallationDate: Installed on 2014-12-13 (1508 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
Rae (m5gorrf) wrote :
tags: added: xenial2bionic
tags: added: third-party-packages
affects: ubuntu-release-upgrader (Ubuntu) → ubuntu
Revision history for this message
Rae (m5gorrf) wrote : Re: [Bug 1813842] Re: NO DNS server on bootup

rae@rae-W540:~$ rae@rae-W540:~$ sudo ubuntu-bug
/var/crash/linux-image-4.15.0-44-generic.232084.crash
rae@rae-W540:~$: command not found

[image: image.png]

On Tue, Jan 29, 2019 at 5:50 PM Brian Murray <email address hidden> wrote:

> ** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1813842
>
> Title:
> NO DNS server on bootup
>
> Status in Ubuntu:
> New
>
> Bug description:
> They tried to fix this with no help
>
> I have to do the following everytime I boot to correct the DNS issue
>
> sudo nano /etc/resolv.conf comment out the existing DNS
>
> Add nameserver 8.8.8.8
> nameserver 192.159.10.2
>
> then
>
> sudo service network-manager restart
>
> I reboot a few times a day
>
> without this I can ping 8.8.8.8 but not yahoo.com
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubuntu-release-upgrader-core 1:18.04.29
> ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
> Uname: Linux 4.15.0-44-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7.5
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Jan 29 14:32:23 2019
> InstallationDate: Installed on 2014-12-13 (1508 days ago)
> InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
> (20140722.2)
> PackageArchitecture: all
> ProcEnviron:
> LANGUAGE=en_US
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: ubuntu-release-upgrader
> Symptom: dist-upgrade
> UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago)
> VarLogDistupgradeTermlog:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1813842/+subscriptions
>

Revision history for this message
Rae (m5gorrf) wrote :

Hello,

Sorry about sending the Xserver issue (now resolved)

My DNS issue remains. still have to edit resolv.conf

thanks

On Tue, Jan 29, 2019 at 5:50 PM Brian Murray <email address hidden> wrote:

> ** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1813842
>
> Title:
> NO DNS server on bootup
>
> Status in Ubuntu:
> New
>
> Bug description:
> They tried to fix this with no help
>
> I have to do the following everytime I boot to correct the DNS issue
>
> sudo nano /etc/resolv.conf comment out the existing DNS
>
> Add nameserver 8.8.8.8
> nameserver 192.159.10.2
>
> then
>
> sudo service network-manager restart
>
> I reboot a few times a day
>
> without this I can ping 8.8.8.8 but not yahoo.com
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubuntu-release-upgrader-core 1:18.04.29
> ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
> Uname: Linux 4.15.0-44-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7.5
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Jan 29 14:32:23 2019
> InstallationDate: Installed on 2014-12-13 (1508 days ago)
> InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
> (20140722.2)
> PackageArchitecture: all
> ProcEnviron:
> LANGUAGE=en_US
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: ubuntu-release-upgrader
> Symptom: dist-upgrade
> UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago)
> VarLogDistupgradeTermlog:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1813842/+subscriptions
>

Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.