apt-get broken trust chain while updating
0
This morning I restarted my server and discovered an issue while doing apt-get update:
Err:1 http://hwraid.le-vert.net/ubuntu xenial InRelease
Could not resolve 'hwraid.le-vert.net'
Err:2 http://ppa.launchpad.net/certbot/certbot/ubuntu xenial InRelease
Could not resolve 'ppa.launchpad.net'
Err:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:4 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
Could not resolve 'ppa.launchpad.net'
Err:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
Could not resolve 'security.ubuntu.com'
Err:6 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:8 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 InRelease
Could not resolve 'repo.mongodb.org'
Err:9 https://download.docker.com/linux/ubuntu xenial InRelease
Could not resolve host: download.docker.com
Err:10 https://deb.nodesource.com/node_8.x xenial InRelease
Could not resolve host: deb.nodesource.com
Reading package lists... Done
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Could not resolve 'security.ubuntu.com'
W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/xenial/InRelease Could not resolve host: download.docker.com
W: Failed to fetch http://hwraid.le-vert.net/ubuntu/dists/xenial/InRelease Could not resolve 'hwraid.le-vert.net'
W: Failed to fetch http://ppa.launchpad.net/certbot/certbot/ubuntu/dists/xenial/InRelease Could not resolve 'ppa.launchpad.net'
W: Failed to fetch http://repo.mongodb.org/apt/ubuntu/dists/xenial/mongodb-org/3.2/InRelease Could not resolve 'repo.mongodb.org'
W: Failed to fetch https://deb.nodesource.com/node_8.x/dists/xenial/InRelease Could not resolve host: deb.nodesource.com
W: Failed to fetch http://ppa.launchpad.net/ondrej/php/ubuntu/dists/xenial/InRelease Could not resolve 'ppa.launchpad.net'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Now this isnt a big deal, I know the common issues and fixes for apt and attempted a few of them, however during my troubleshooting I came across something interesting, whenever I run the update in the syslog I get the following:
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.us.archive.ubuntu.com/SRV: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.us.archive.ubuntu.com/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.repo.mongodb.org/SRV: bad cache hit (org/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.repo.mongodb.org/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.ppa.launchpad.net/SRV: bad cache hit (net/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.ppa.launchpad.net/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.hwraid.le-vert.net/SRV: bad cache hit (net/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.hwraid.le-vert.net/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.security.ubuntu.com/SRV: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.security.ubuntu.com/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating deb.nodesource.com/A: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving 'deb.nodesource.com/A/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating download.docker.com/CNAME: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving 'download.docker.com/A/IN': 10.0.2.1#53
...
I have no idea what this means and Googleing it hasnt helped me thus far, what does this mean and how can I fix it successfully?
ubuntu apt-get
asked Dec 10 at 15:15
13aal
10311
add a comment |
0
This morning I restarted my server and discovered an issue while doing apt-get update:
Err:1 http://hwraid.le-vert.net/ubuntu xenial InRelease
Could not resolve 'hwraid.le-vert.net'
Err:2 http://ppa.launchpad.net/certbot/certbot/ubuntu xenial InRelease
Could not resolve 'ppa.launchpad.net'
Err:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:4 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
Could not resolve 'ppa.launchpad.net'
Err:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
Could not resolve 'security.ubuntu.com'
Err:6 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:8 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 InRelease
Could not resolve 'repo.mongodb.org'
Err:9 https://download.docker.com/linux/ubuntu xenial InRelease
Could not resolve host: download.docker.com
Err:10 https://deb.nodesource.com/node_8.x xenial InRelease
Could not resolve host: deb.nodesource.com
Reading package lists... Done
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Could not resolve 'security.ubuntu.com'
W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/xenial/InRelease Could not resolve host: download.docker.com
W: Failed to fetch http://hwraid.le-vert.net/ubuntu/dists/xenial/InRelease Could not resolve 'hwraid.le-vert.net'
W: Failed to fetch http://ppa.launchpad.net/certbot/certbot/ubuntu/dists/xenial/InRelease Could not resolve 'ppa.launchpad.net'
W: Failed to fetch http://repo.mongodb.org/apt/ubuntu/dists/xenial/mongodb-org/3.2/InRelease Could not resolve 'repo.mongodb.org'
W: Failed to fetch https://deb.nodesource.com/node_8.x/dists/xenial/InRelease Could not resolve host: deb.nodesource.com
W: Failed to fetch http://ppa.launchpad.net/ondrej/php/ubuntu/dists/xenial/InRelease Could not resolve 'ppa.launchpad.net'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Now this isnt a big deal, I know the common issues and fixes for apt and attempted a few of them, however during my troubleshooting I came across something interesting, whenever I run the update in the syslog I get the following:
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.us.archive.ubuntu.com/SRV: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.us.archive.ubuntu.com/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.repo.mongodb.org/SRV: bad cache hit (org/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.repo.mongodb.org/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.ppa.launchpad.net/SRV: bad cache hit (net/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.ppa.launchpad.net/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.hwraid.le-vert.net/SRV: bad cache hit (net/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.hwraid.le-vert.net/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.security.ubuntu.com/SRV: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.security.ubuntu.com/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating deb.nodesource.com/A: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving 'deb.nodesource.com/A/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating download.docker.com/CNAME: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving 'download.docker.com/A/IN': 10.0.2.1#53
...
I have no idea what this means and Googleing it hasnt helped me thus far, what does this mean and how can I fix it successfully?
ubuntu apt-get
asked Dec 10 at 15:15
13aal
10311
add a comment |
0
0
0
This morning I restarted my server and discovered an issue while doing apt-get update:
Err:1 http://hwraid.le-vert.net/ubuntu xenial InRelease
Could not resolve 'hwraid.le-vert.net'
Err:2 http://ppa.launchpad.net/certbot/certbot/ubuntu xenial InRelease
Could not resolve 'ppa.launchpad.net'
Err:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:4 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
Could not resolve 'ppa.launchpad.net'
Err:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
Could not resolve 'security.ubuntu.com'
Err:6 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:8 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 InRelease
Could not resolve 'repo.mongodb.org'
Err:9 https://download.docker.com/linux/ubuntu xenial InRelease
Could not resolve host: download.docker.com
Err:10 https://deb.nodesource.com/node_8.x xenial InRelease
Could not resolve host: deb.nodesource.com
Reading package lists... Done
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Could not resolve 'security.ubuntu.com'
W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/xenial/InRelease Could not resolve host: download.docker.com
W: Failed to fetch http://hwraid.le-vert.net/ubuntu/dists/xenial/InRelease Could not resolve 'hwraid.le-vert.net'
W: Failed to fetch http://ppa.launchpad.net/certbot/certbot/ubuntu/dists/xenial/InRelease Could not resolve 'ppa.launchpad.net'
W: Failed to fetch http://repo.mongodb.org/apt/ubuntu/dists/xenial/mongodb-org/3.2/InRelease Could not resolve 'repo.mongodb.org'
W: Failed to fetch https://deb.nodesource.com/node_8.x/dists/xenial/InRelease Could not resolve host: deb.nodesource.com
W: Failed to fetch http://ppa.launchpad.net/ondrej/php/ubuntu/dists/xenial/InRelease Could not resolve 'ppa.launchpad.net'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Now this isnt a big deal, I know the common issues and fixes for apt and attempted a few of them, however during my troubleshooting I came across something interesting, whenever I run the update in the syslog I get the following:
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.us.archive.ubuntu.com/SRV: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.us.archive.ubuntu.com/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.repo.mongodb.org/SRV: bad cache hit (org/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.repo.mongodb.org/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.ppa.launchpad.net/SRV: bad cache hit (net/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.ppa.launchpad.net/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.hwraid.le-vert.net/SRV: bad cache hit (net/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.hwraid.le-vert.net/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.security.ubuntu.com/SRV: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.security.ubuntu.com/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating deb.nodesource.com/A: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving 'deb.nodesource.com/A/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating download.docker.com/CNAME: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving 'download.docker.com/A/IN': 10.0.2.1#53
...
I have no idea what this means and Googleing it hasnt helped me thus far, what does this mean and how can I fix it successfully?
ubuntu apt-get
asked Dec 10 at 15:15
13aal
10311
This morning I restarted my server and discovered an issue while doing apt-get update:
Err:1 http://hwraid.le-vert.net/ubuntu xenial InRelease
Could not resolve 'hwraid.le-vert.net'
Err:2 http://ppa.launchpad.net/certbot/certbot/ubuntu xenial InRelease
Could not resolve 'ppa.launchpad.net'
Err:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:4 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
Could not resolve 'ppa.launchpad.net'
Err:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
Could not resolve 'security.ubuntu.com'
Err:6 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Could not resolve 'us.archive.ubuntu.com'
Err:8 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 InRelease
Could not resolve 'repo.mongodb.org'
Err:9 https://download.docker.com/linux/ubuntu xenial InRelease
Could not resolve host: download.docker.com
Err:10 https://deb.nodesource.com/node_8.x xenial InRelease
Could not resolve host: deb.nodesource.com
Reading package lists... Done
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease Could not resolve 'us.archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Could not resolve 'security.ubuntu.com'
W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/xenial/InRelease Could not resolve host: download.docker.com
W: Failed to fetch http://hwraid.le-vert.net/ubuntu/dists/xenial/InRelease Could not resolve 'hwraid.le-vert.net'
W: Failed to fetch http://ppa.launchpad.net/certbot/certbot/ubuntu/dists/xenial/InRelease Could not resolve 'ppa.launchpad.net'
W: Failed to fetch http://repo.mongodb.org/apt/ubuntu/dists/xenial/mongodb-org/3.2/InRelease Could not resolve 'repo.mongodb.org'
W: Failed to fetch https://deb.nodesource.com/node_8.x/dists/xenial/InRelease Could not resolve host: deb.nodesource.com
W: Failed to fetch http://ppa.launchpad.net/ondrej/php/ubuntu/dists/xenial/InRelease Could not resolve 'ppa.launchpad.net'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Now this isnt a big deal, I know the common issues and fixes for apt and attempted a few of them, however during my troubleshooting I came across something interesting, whenever I run the update in the syslog I get the following:
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.us.archive.ubuntu.com/SRV: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.us.archive.ubuntu.com/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.repo.mongodb.org/SRV: bad cache hit (org/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.repo.mongodb.org/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.ppa.launchpad.net/SRV: bad cache hit (net/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.ppa.launchpad.net/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.hwraid.le-vert.net/SRV: bad cache hit (net/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.hwraid.le-vert.net/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating _http._tcp.security.ubuntu.com/SRV: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving '_http._tcp.security.ubuntu.com/SRV/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating deb.nodesource.com/A: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving 'deb.nodesource.com/A/IN': 10.0.2.1#53
Dec 10 09:11:37 magic named[2715]: validating download.docker.com/CNAME: bad cache hit (com/DS)
Dec 10 09:11:37 magic named[2715]: broken trust chain resolving 'download.docker.com/A/IN': 10.0.2.1#53
...
I have no idea what this means and Googleing it hasnt helped me thus far, what does this mean and how can I fix it successfully?
ubuntu apt-get
ubuntu apt-get
asked Dec 10 at 15:15
13aal
10311
asked Dec 10 at 15:15
13aal
10311
asked Dec 10 at 15:15
13aal
10311
asked Dec 10 at 15:15
13aal
10311
asked Dec 10 at 15:15
13aal
10311
10311
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
1
The "could not resolve" suggests that you're having a DNS resolution issue, which in turn causes the broken trust chain. I would examine your DNS settings - doing a simple ping to a domain name (not an IP address) should confirm this theory. Try ping us.archive.ubuntu.com for instance.
answered Dec 10 at 15:25
Jon G - Megaphone Tech
54449
I was able to fix it with asudo echo "nameserver 8.8.8.8" > /etc/resolv.confseems like when i rebooted it wiped my resolv.conf?
– 13aal
Dec 10 at 15:26
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1382347%2fapt-get-broken-trust-chain-while-updating%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
The "could not resolve" suggests that you're having a DNS resolution issue, which in turn causes the broken trust chain. I would examine your DNS settings - doing a simple ping to a domain name (not an IP address) should confirm this theory. Try ping us.archive.ubuntu.com for instance.
answered Dec 10 at 15:25
Jon G - Megaphone Tech
54449
I was able to fix it with asudo echo "nameserver 8.8.8.8" > /etc/resolv.confseems like when i rebooted it wiped my resolv.conf?
– 13aal
Dec 10 at 15:26
add a comment |
1
The "could not resolve" suggests that you're having a DNS resolution issue, which in turn causes the broken trust chain. I would examine your DNS settings - doing a simple ping to a domain name (not an IP address) should confirm this theory. Try ping us.archive.ubuntu.com for instance.
answered Dec 10 at 15:25
Jon G - Megaphone Tech
54449
I was able to fix it with asudo echo "nameserver 8.8.8.8" > /etc/resolv.confseems like when i rebooted it wiped my resolv.conf?
– 13aal
Dec 10 at 15:26
add a comment |
1
1
1
The "could not resolve" suggests that you're having a DNS resolution issue, which in turn causes the broken trust chain. I would examine your DNS settings - doing a simple ping to a domain name (not an IP address) should confirm this theory. Try ping us.archive.ubuntu.com for instance.
answered Dec 10 at 15:25
Jon G - Megaphone Tech
54449
The "could not resolve" suggests that you're having a DNS resolution issue, which in turn causes the broken trust chain. I would examine your DNS settings - doing a simple ping to a domain name (not an IP address) should confirm this theory. Try ping us.archive.ubuntu.com for instance.
answered Dec 10 at 15:25
Jon G - Megaphone Tech
54449
answered Dec 10 at 15:25
Jon G - Megaphone Tech
54449
answered Dec 10 at 15:25
Jon G - Megaphone Tech
54449
answered Dec 10 at 15:25
Jon G - Megaphone Tech
54449
54449
I was able to fix it with asudo echo "nameserver 8.8.8.8" > /etc/resolv.confseems like when i rebooted it wiped my resolv.conf?
– 13aal
Dec 10 at 15:26
add a comment |
I was able to fix it with asudo echo "nameserver 8.8.8.8" > /etc/resolv.confseems like when i rebooted it wiped my resolv.conf?
– 13aal
Dec 10 at 15:26
I was able to fix it with a
sudo echo "nameserver 8.8.8.8" > /etc/resolv.conf seems like when i rebooted it wiped my resolv.conf?– 13aal
Dec 10 at 15:26
I was able to fix it with a
sudo echo "nameserver 8.8.8.8" > /etc/resolv.conf seems like when i rebooted it wiped my resolv.conf?– 13aal
Dec 10 at 15:26
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1382347%2fapt-get-broken-trust-chain-while-updating%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
