Intermittent DNS 'temporarily failure in name resoluiton' on Ubuntu 18.04 Server - how do I debug this?DNS issues - How to debug?Ubuntu forgets custom DNS server after a whileFailover DNS When Primary Can't Resolve?18.04 ignoring DHCP-provided DNS serverConfiguring multiple DNS name servers on 18.04 serverUbuntu - Basic Host Name Resolution 18.04 IssuesUbuntu 18.04 - no DNS query
What is the difference between democracy and ochlocracy?
How to discourage mundane play?
Countering an uncounterable spell, triggers, and state-based actions
Rational Number RNG
Is there any algorithm that runs faster in Mathematica than in C or FORTRAN?
Is Jupiter bright enough to be seen in color by the naked eye from Jupiter orbit?
What are modes in real world?
Use of expression "statistically significantly positive"
Novel about immortality being kept secret by world leaders
Why do turf winterguard (applied late fall) fertilizers have no “P” (phosphorous)?
How are hillsides farmed?
Why is double encryption that's equivalent to single encryption no better than single encryption?
Should I stop applying faculty positions after I take on a postdoc job
Why do some web servers still provide information on vendor and version in the HTTP response headers
Why do Climate activists attack public transport?
Are these 2 resistors in parallel?
Plain Hunt Bell-Ringing
"traversal failed: u: Bad message" when deleting an extremely large directory in Linux
How can I more clearly ask people to accomodate for my autism?
What elements would be created in a star composed entirely of gold?
Parents suppressing the teaching
Why is a Lockheed MC-130J Commando II creating such a loud droning sound?
Does animal blood, esp. human, really have similar salinity as ocean water, and does that prove anything about evolution?
Asimov's story where a man's speech contains no information
Intermittent DNS 'temporarily failure in name resoluiton' on Ubuntu 18.04 Server - how do I debug this?
DNS issues - How to debug?Ubuntu forgets custom DNS server after a whileFailover DNS When Primary Can't Resolve?18.04 ignoring DHCP-provided DNS serverConfiguring multiple DNS name servers on 18.04 serverUbuntu - Basic Host Name Resolution 18.04 IssuesUbuntu 18.04 - no DNS query
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I have multiple Ubuntu 18.04 LTS Server installations on the same vSphere 6.7 host. One runs my DHCP and DNS server and has done so reliably for years, all the way from 14.04 to 18.04.
However, one of the servers is suddenly getting moments (multiple times per day) where it can't use DNS to resolve addresses. If you ping something from the command line, you get 'Temporary failure in name resolution'. This can last from 30 minutes to 12 hours. Eventually - with no changes on my part - it will start working again, only to fail again at some point. Resetting the host tends to resolve the issue for a while too.
This server was recently installed (about 2 weeks ago) 18.04 from the ISO and contains all the latest patches. I believe that because it is from the default that means it is using resolved and not interfaces, but I don't know for sure as I haven't followed how Ubuntu changed in that area. I do know that this host gets its address from DHCP and on a reboot, it reliably picks up not only its address but the DNS server list just fine (systemd-resolve --status displays all the DNS server IPs correctly).
What I don't know is how to debug this? What should I be looking for?
It is super challenging to learn when it happens - I notice it much later when I realize that its rsync jobs to update the other servers with weather data isn't working and I now know from experience that this means name resolution isn't working. Is there more debug info than what is in syslog? Any thoughts on how I can pin down when it starts happening to see if there are relevant syslog entries? Also, is there better debug info from whatever is doing name resolution (sockets?) when I attempt it and it fails?
Should I be looking for anything on the DNS server itself? I am the sysadmin for it so I can do whatever I need to.
networking dns
asked May 22 at 16:40
scottshscottsh
12 bronze badges
add a comment
|
I have multiple Ubuntu 18.04 LTS Server installations on the same vSphere 6.7 host. One runs my DHCP and DNS server and has done so reliably for years, all the way from 14.04 to 18.04.
However, one of the servers is suddenly getting moments (multiple times per day) where it can't use DNS to resolve addresses. If you ping something from the command line, you get 'Temporary failure in name resolution'. This can last from 30 minutes to 12 hours. Eventually - with no changes on my part - it will start working again, only to fail again at some point. Resetting the host tends to resolve the issue for a while too.
This server was recently installed (about 2 weeks ago) 18.04 from the ISO and contains all the latest patches. I believe that because it is from the default that means it is using resolved and not interfaces, but I don't know for sure as I haven't followed how Ubuntu changed in that area. I do know that this host gets its address from DHCP and on a reboot, it reliably picks up not only its address but the DNS server list just fine (systemd-resolve --status displays all the DNS server IPs correctly).
What I don't know is how to debug this? What should I be looking for?
It is super challenging to learn when it happens - I notice it much later when I realize that its rsync jobs to update the other servers with weather data isn't working and I now know from experience that this means name resolution isn't working. Is there more debug info than what is in syslog? Any thoughts on how I can pin down when it starts happening to see if there are relevant syslog entries? Also, is there better debug info from whatever is doing name resolution (sockets?) when I attempt it and it fails?
Should I be looking for anything on the DNS server itself? I am the sysadmin for it so I can do whatever I need to.
networking dns
asked May 22 at 16:40
scottshscottsh
12 bronze badges
add a comment
|
I have multiple Ubuntu 18.04 LTS Server installations on the same vSphere 6.7 host. One runs my DHCP and DNS server and has done so reliably for years, all the way from 14.04 to 18.04.
However, one of the servers is suddenly getting moments (multiple times per day) where it can't use DNS to resolve addresses. If you ping something from the command line, you get 'Temporary failure in name resolution'. This can last from 30 minutes to 12 hours. Eventually - with no changes on my part - it will start working again, only to fail again at some point. Resetting the host tends to resolve the issue for a while too.
This server was recently installed (about 2 weeks ago) 18.04 from the ISO and contains all the latest patches. I believe that because it is from the default that means it is using resolved and not interfaces, but I don't know for sure as I haven't followed how Ubuntu changed in that area. I do know that this host gets its address from DHCP and on a reboot, it reliably picks up not only its address but the DNS server list just fine (systemd-resolve --status displays all the DNS server IPs correctly).
What I don't know is how to debug this? What should I be looking for?
It is super challenging to learn when it happens - I notice it much later when I realize that its rsync jobs to update the other servers with weather data isn't working and I now know from experience that this means name resolution isn't working. Is there more debug info than what is in syslog? Any thoughts on how I can pin down when it starts happening to see if there are relevant syslog entries? Also, is there better debug info from whatever is doing name resolution (sockets?) when I attempt it and it fails?
Should I be looking for anything on the DNS server itself? I am the sysadmin for it so I can do whatever I need to.
networking dns
asked May 22 at 16:40
scottshscottsh
12 bronze badges
I have multiple Ubuntu 18.04 LTS Server installations on the same vSphere 6.7 host. One runs my DHCP and DNS server and has done so reliably for years, all the way from 14.04 to 18.04.
However, one of the servers is suddenly getting moments (multiple times per day) where it can't use DNS to resolve addresses. If you ping something from the command line, you get 'Temporary failure in name resolution'. This can last from 30 minutes to 12 hours. Eventually - with no changes on my part - it will start working again, only to fail again at some point. Resetting the host tends to resolve the issue for a while too.
This server was recently installed (about 2 weeks ago) 18.04 from the ISO and contains all the latest patches. I believe that because it is from the default that means it is using resolved and not interfaces, but I don't know for sure as I haven't followed how Ubuntu changed in that area. I do know that this host gets its address from DHCP and on a reboot, it reliably picks up not only its address but the DNS server list just fine (systemd-resolve --status displays all the DNS server IPs correctly).
What I don't know is how to debug this? What should I be looking for?
It is super challenging to learn when it happens - I notice it much later when I realize that its rsync jobs to update the other servers with weather data isn't working and I now know from experience that this means name resolution isn't working. Is there more debug info than what is in syslog? Any thoughts on how I can pin down when it starts happening to see if there are relevant syslog entries? Also, is there better debug info from whatever is doing name resolution (sockets?) when I attempt it and it fails?
Should I be looking for anything on the DNS server itself? I am the sysadmin for it so I can do whatever I need to.
networking dns
networking dns
asked May 22 at 16:40
scottshscottsh
12 bronze badges
asked May 22 at 16:40
scottshscottsh
12 bronze badges
edited May 30 at 1:23
scottsh
asked May 22 at 16:40
scottshscottsh
12 bronze badges
asked May 22 at 16:40
scottshscottsh
12 bronze badges
asked May 22 at 16:40
scottshscottsh
12 bronze badges
12 bronze badges
add a comment
|
add a comment
|
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
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/4.0/"u003ecc by-sa 4.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
);
);
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%2faskubuntu.com%2fquestions%2f1145420%2fintermittent-dns-temporarily-failure-in-name-resoluiton-on-ubuntu-18-04-server%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- 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.
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%2faskubuntu.com%2fquestions%2f1145420%2fintermittent-dns-temporarily-failure-in-name-resoluiton-on-ubuntu-18-04-server%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
