Can nslookup but not ping after OpenSuse Tumbleweed updateDomain resolve problem with stock DebianDNS Issues...
Pushing the e-pawn
Why isn't there armor to protect from spells in the Potterverse?
Can a passenger predict that an airline is about to go bankrupt?
Sci-fi movie with one survivor and an organism(?) recreating his memories
Is a Middle Name a Given Name?
Received a package but didn't order it
Create the same subfolders in another folder
When did Unix stop storing passwords in clear text?
Windows 10 deletes lots of tiny files super slowly. Anything that can be done to speed it up?
Smallest PRIME containing the first 11 primes as sub-strings
Why is Pelosi so opposed to impeaching Trump?
How many stack cables would be needed if we want to stack two 3850 switches
Would an object shot from earth fall into the sun?
What is this end portal thingy?
Assembly of PCBs containing a mix of SMT and thru-hole parts?
Do interval ratios take overtones into account or solely the fundamental frequency?
Is there a relationship between prime numbers and music?
I transpose the source code, you transpose the input!
Why does Captain Marvel in the MCU not have her sash?
Discrepancy regarding AoE point of origin between English and German PHB
GPLv3 forces us to make code available, but to who?
LM324 - Issue with output in negative feedback
What does it mean by "my days-of-the-week underwear only go to Thursday" in this context?
Avoiding dust scattering when you drill
Can nslookup but not ping after OpenSuse Tumbleweed update
Domain resolve problem with stock DebianDNS Issues on RHEL 6OpenBSD with adsuck: nslookup works, other applications notCannot Intentionally break/stop DNS via /etc/resolv.conf - Always resolving no matter NS configPing works only with IP addresses (not with domain names)Why am I getting “Curl (6) Could not resolve host” after I did a “yum -y update”?Can ping 8.8.8.8 but can't browse internetUnable to ping router but broadcast ping returns response from itHow to locate the module that handles DNS resolving in buildroot?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Following the 02/09 Tumbleweed update my DNS seems to be broken.
My wifi icon in top right has a question mark, ping google.com returns Name or service not known, but nslookup google.com correctly returns the IP address. If I go to Google's IP address in Firefox I get the message We can't connect to the server at www.google.com. so it is being resolved somehow.
I can ping 8.8.8.8.
I've tried all the other answers I can see for related issues but none have worked for me. My resolv.conf is:
search MYDOMAIN
nameserver IP1
nameserver IP2
where IP1 & 2 are my companies addresses.
I've tried changing nsswitch.conf and reduced the hosts line to files dns (removing the mdns4 bit).
If I force Google's DNS then it still doesn't work, i.e. if I try nslookup google.com 8.8.8.8 it fails, and if I go into NetworkManager and add 8.8.8.8,8.8.4.4 to DNS in IPv4 settings for my Wifi then it still doesn't work.
wifi dns opensuse
asked Feb 13 at 13:51
Stuart LacyStuart Lacy
1112 bronze badges
add a comment
|
Following the 02/09 Tumbleweed update my DNS seems to be broken.
My wifi icon in top right has a question mark, ping google.com returns Name or service not known, but nslookup google.com correctly returns the IP address. If I go to Google's IP address in Firefox I get the message We can't connect to the server at www.google.com. so it is being resolved somehow.
I can ping 8.8.8.8.
I've tried all the other answers I can see for related issues but none have worked for me. My resolv.conf is:
search MYDOMAIN
nameserver IP1
nameserver IP2
where IP1 & 2 are my companies addresses.
I've tried changing nsswitch.conf and reduced the hosts line to files dns (removing the mdns4 bit).
If I force Google's DNS then it still doesn't work, i.e. if I try nslookup google.com 8.8.8.8 it fails, and if I go into NetworkManager and add 8.8.8.8,8.8.4.4 to DNS in IPv4 settings for my Wifi then it still doesn't work.
wifi dns opensuse
asked Feb 13 at 13:51
Stuart LacyStuart Lacy
1112 bronze badges
Do not usepingto troubleshoot DNS issues. The correct tool for that isdig, which is superiot tonslookup. By default it will use nameservers defined in/etc/resolv.confso the first step is making sure you can contact them.
– Patrick Mevzek
Feb 14 at 23:17
add a comment
|
Following the 02/09 Tumbleweed update my DNS seems to be broken.
My wifi icon in top right has a question mark, ping google.com returns Name or service not known, but nslookup google.com correctly returns the IP address. If I go to Google's IP address in Firefox I get the message We can't connect to the server at www.google.com. so it is being resolved somehow.
I can ping 8.8.8.8.
I've tried all the other answers I can see for related issues but none have worked for me. My resolv.conf is:
search MYDOMAIN
nameserver IP1
nameserver IP2
where IP1 & 2 are my companies addresses.
I've tried changing nsswitch.conf and reduced the hosts line to files dns (removing the mdns4 bit).
If I force Google's DNS then it still doesn't work, i.e. if I try nslookup google.com 8.8.8.8 it fails, and if I go into NetworkManager and add 8.8.8.8,8.8.4.4 to DNS in IPv4 settings for my Wifi then it still doesn't work.
wifi dns opensuse
asked Feb 13 at 13:51
Stuart LacyStuart Lacy
1112 bronze badges
Following the 02/09 Tumbleweed update my DNS seems to be broken.
My wifi icon in top right has a question mark, ping google.com returns Name or service not known, but nslookup google.com correctly returns the IP address. If I go to Google's IP address in Firefox I get the message We can't connect to the server at www.google.com. so it is being resolved somehow.
I can ping 8.8.8.8.
I've tried all the other answers I can see for related issues but none have worked for me. My resolv.conf is:
search MYDOMAIN
nameserver IP1
nameserver IP2
where IP1 & 2 are my companies addresses.
I've tried changing nsswitch.conf and reduced the hosts line to files dns (removing the mdns4 bit).
If I force Google's DNS then it still doesn't work, i.e. if I try nslookup google.com 8.8.8.8 it fails, and if I go into NetworkManager and add 8.8.8.8,8.8.4.4 to DNS in IPv4 settings for my Wifi then it still doesn't work.
wifi dns opensuse
wifi dns opensuse
asked Feb 13 at 13:51
Stuart LacyStuart Lacy
1112 bronze badges
asked Feb 13 at 13:51
Stuart LacyStuart Lacy
1112 bronze badges
asked Feb 13 at 13:51
Stuart LacyStuart Lacy
1112 bronze badges
asked Feb 13 at 13:51
Stuart LacyStuart Lacy
1112 bronze badges
asked Feb 13 at 13:51
Stuart LacyStuart Lacy
1112 bronze badges
1112 bronze badges
Do not usepingto troubleshoot DNS issues. The correct tool for that isdig, which is superiot tonslookup. By default it will use nameservers defined in/etc/resolv.confso the first step is making sure you can contact them.
– Patrick Mevzek
Feb 14 at 23:17
add a comment
|
Do not usepingto troubleshoot DNS issues. The correct tool for that isdig, which is superiot tonslookup. By default it will use nameservers defined in/etc/resolv.confso the first step is making sure you can contact them.
– Patrick Mevzek
Feb 14 at 23:17
Do not use
ping to troubleshoot DNS issues. The correct tool for that is dig, which is superiot to nslookup. By default it will use nameservers defined in /etc/resolv.conf so the first step is making sure you can contact them.– Patrick Mevzek
Feb 14 at 23:17
Do not use
ping to troubleshoot DNS issues. The correct tool for that is dig, which is superiot to nslookup. By default it will use nameservers defined in /etc/resolv.conf so the first step is making sure you can contact them.– Patrick Mevzek
Feb 14 at 23:17
add a comment
|
3 Answers
3
active
oldest
votes
I had a similar problem after update from Leap 15.0 to Leap 15.1: nslookup worked but ping or anything else that required dns resolution didn't. I did all the standard checks (resolv.conf, nsswitch.conf, /etc/sysconfig/network/config) and these were in order. Switching from wicked to NetworkManager and enabling dnsmasq as above solved my issue initially.
I dug a little deeper and found a tip here that it may be related to issues in apparmor configuration: https://forums.opensuse.org/showthread.php/536437-DNS-problem-after-upgrade-from-15-0?p=2906092#post2906092
Similarly to that thread on my system that there was an updated configuration in /etc/apparmor.d/abstractions/nameservice.rpmnew which allowed access to additional directories used by nscd. Once I copied over this new config file and cleared the apparmor cache as described in that post, wicked started working and I could revert my network manager config back to the original version, without needing to use dnsmasq.
answered Jul 16 at 15:45
myrosiamyrosia
111 bronze badge
Exactly the same thing here after the update from 15.0 to 15.1.
– Claas
Jul 17 at 7:32
add a comment
|
I got this working by adding dns=dnsmasq under [main] in /etc/NetworkManager/NetworkManager.conf.
answered Feb 14 at 15:55
Stuart LacyStuart Lacy
1112 bronze badges
add a comment
|
Same dns issue after upgrade from 15.0 to 15.1
After deleting the app armor cache directory contents as described above, name resolution started working.
answered 1 hour ago
FredsterFredster
1
New contributor
Fredster is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment
|
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f500394%2fcan-nslookup-but-not-ping-after-opensuse-tumbleweed-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had a similar problem after update from Leap 15.0 to Leap 15.1: nslookup worked but ping or anything else that required dns resolution didn't. I did all the standard checks (resolv.conf, nsswitch.conf, /etc/sysconfig/network/config) and these were in order. Switching from wicked to NetworkManager and enabling dnsmasq as above solved my issue initially.
I dug a little deeper and found a tip here that it may be related to issues in apparmor configuration: https://forums.opensuse.org/showthread.php/536437-DNS-problem-after-upgrade-from-15-0?p=2906092#post2906092
Similarly to that thread on my system that there was an updated configuration in /etc/apparmor.d/abstractions/nameservice.rpmnew which allowed access to additional directories used by nscd. Once I copied over this new config file and cleared the apparmor cache as described in that post, wicked started working and I could revert my network manager config back to the original version, without needing to use dnsmasq.
answered Jul 16 at 15:45
myrosiamyrosia
111 bronze badge
Exactly the same thing here after the update from 15.0 to 15.1.
– Claas
Jul 17 at 7:32
add a comment
|
I had a similar problem after update from Leap 15.0 to Leap 15.1: nslookup worked but ping or anything else that required dns resolution didn't. I did all the standard checks (resolv.conf, nsswitch.conf, /etc/sysconfig/network/config) and these were in order. Switching from wicked to NetworkManager and enabling dnsmasq as above solved my issue initially.
I dug a little deeper and found a tip here that it may be related to issues in apparmor configuration: https://forums.opensuse.org/showthread.php/536437-DNS-problem-after-upgrade-from-15-0?p=2906092#post2906092
Similarly to that thread on my system that there was an updated configuration in /etc/apparmor.d/abstractions/nameservice.rpmnew which allowed access to additional directories used by nscd. Once I copied over this new config file and cleared the apparmor cache as described in that post, wicked started working and I could revert my network manager config back to the original version, without needing to use dnsmasq.
answered Jul 16 at 15:45
myrosiamyrosia
111 bronze badge
Exactly the same thing here after the update from 15.0 to 15.1.
– Claas
Jul 17 at 7:32
add a comment
|
I had a similar problem after update from Leap 15.0 to Leap 15.1: nslookup worked but ping or anything else that required dns resolution didn't. I did all the standard checks (resolv.conf, nsswitch.conf, /etc/sysconfig/network/config) and these were in order. Switching from wicked to NetworkManager and enabling dnsmasq as above solved my issue initially.
I dug a little deeper and found a tip here that it may be related to issues in apparmor configuration: https://forums.opensuse.org/showthread.php/536437-DNS-problem-after-upgrade-from-15-0?p=2906092#post2906092
Similarly to that thread on my system that there was an updated configuration in /etc/apparmor.d/abstractions/nameservice.rpmnew which allowed access to additional directories used by nscd. Once I copied over this new config file and cleared the apparmor cache as described in that post, wicked started working and I could revert my network manager config back to the original version, without needing to use dnsmasq.
answered Jul 16 at 15:45
myrosiamyrosia
111 bronze badge
I had a similar problem after update from Leap 15.0 to Leap 15.1: nslookup worked but ping or anything else that required dns resolution didn't. I did all the standard checks (resolv.conf, nsswitch.conf, /etc/sysconfig/network/config) and these were in order. Switching from wicked to NetworkManager and enabling dnsmasq as above solved my issue initially.
I dug a little deeper and found a tip here that it may be related to issues in apparmor configuration: https://forums.opensuse.org/showthread.php/536437-DNS-problem-after-upgrade-from-15-0?p=2906092#post2906092
Similarly to that thread on my system that there was an updated configuration in /etc/apparmor.d/abstractions/nameservice.rpmnew which allowed access to additional directories used by nscd. Once I copied over this new config file and cleared the apparmor cache as described in that post, wicked started working and I could revert my network manager config back to the original version, without needing to use dnsmasq.
answered Jul 16 at 15:45
myrosiamyrosia
111 bronze badge
answered Jul 16 at 15:45
myrosiamyrosia
111 bronze badge
answered Jul 16 at 15:45
myrosiamyrosia
111 bronze badge
answered Jul 16 at 15:45
myrosiamyrosia
111 bronze badge
111 bronze badge
Exactly the same thing here after the update from 15.0 to 15.1.
– Claas
Jul 17 at 7:32
add a comment
|
Exactly the same thing here after the update from 15.0 to 15.1.
– Claas
Jul 17 at 7:32
Exactly the same thing here after the update from 15.0 to 15.1.
– Claas
Jul 17 at 7:32
Exactly the same thing here after the update from 15.0 to 15.1.
– Claas
Jul 17 at 7:32
add a comment
|
I got this working by adding dns=dnsmasq under [main] in /etc/NetworkManager/NetworkManager.conf.
answered Feb 14 at 15:55
Stuart LacyStuart Lacy
1112 bronze badges
add a comment
|
I got this working by adding dns=dnsmasq under [main] in /etc/NetworkManager/NetworkManager.conf.
answered Feb 14 at 15:55
Stuart LacyStuart Lacy
1112 bronze badges
add a comment
|
I got this working by adding dns=dnsmasq under [main] in /etc/NetworkManager/NetworkManager.conf.
answered Feb 14 at 15:55
Stuart LacyStuart Lacy
1112 bronze badges
I got this working by adding dns=dnsmasq under [main] in /etc/NetworkManager/NetworkManager.conf.
answered Feb 14 at 15:55
Stuart LacyStuart Lacy
1112 bronze badges
answered Feb 14 at 15:55
Stuart LacyStuart Lacy
1112 bronze badges
answered Feb 14 at 15:55
Stuart LacyStuart Lacy
1112 bronze badges
answered Feb 14 at 15:55
Stuart LacyStuart Lacy
1112 bronze badges
1112 bronze badges
add a comment
|
add a comment
|
Same dns issue after upgrade from 15.0 to 15.1
After deleting the app armor cache directory contents as described above, name resolution started working.
answered 1 hour ago
FredsterFredster
1
New contributor
Fredster is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment
|
Same dns issue after upgrade from 15.0 to 15.1
After deleting the app armor cache directory contents as described above, name resolution started working.
answered 1 hour ago
FredsterFredster
1
New contributor
Fredster is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment
|
Same dns issue after upgrade from 15.0 to 15.1
After deleting the app armor cache directory contents as described above, name resolution started working.
answered 1 hour ago
FredsterFredster
1
New contributor
Fredster is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Same dns issue after upgrade from 15.0 to 15.1
After deleting the app armor cache directory contents as described above, name resolution started working.
answered 1 hour ago
FredsterFredster
1
New contributor
Fredster is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 1 hour ago
FredsterFredster
1
New contributor
Fredster is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 1 hour ago
FredsterFredster
1
answered 1 hour ago
FredsterFredster
1
1
New contributor
Fredster is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Fredster is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment
|
add a comment
|
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f500394%2fcan-nslookup-but-not-ping-after-opensuse-tumbleweed-update%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
Do not use
pingto troubleshoot DNS issues. The correct tool for that isdig, which is superiot tonslookup. By default it will use nameservers defined in/etc/resolv.confso the first step is making sure you can contact them.– Patrick Mevzek
Feb 14 at 23:17