I can ping my host domain/8.8.8.8 but can't ping google: name resolution failure











up vote
1
down vote

favorite












I think I configured the bind dns server correctly on my ubuntu 18.04 server on my virtual network. I can ping my other server ' www.boblowlaw.com ' just fine and I can also ping 8.8.8.8 and I get



ping google.com: temporary failure in name resolution.


These are my results when I do a nslookup on www.boblowlaw.com & google.com



enter image description here



When I use the command systemctl-resolve --status this is my results



enter image description here



I've tried all types of different trouble shooting to try to figure out whats wrong and I just can't figure it out. Any advice/help would be appreicated



ls -al /etc/resolv.conf
- 1rwxrwxrwx 1 root root 32 Dec 3 21 21 /etc/resolv.conf -> /run/system/
resolve/resolv.conf

cat /etc/resolv.con
nameserver 10.161.10.2
nameserver 8.8.8.8

cat /etc/netplan/01-netcfg.yaml1
network:
renderer: networkd
ethernets:
ens160:
addresses:
- 10.161.10.2/24
gateway4: 10.161.10.1
nameservers:
addresses: [8.8.8.8]

cat /etc/systemd/resolve.conf
[Resolve]
DNS=10.161.10.2
#FallbackDNS=
#Domains=

cat /run/systemd/resolve/resolv.conf
nameserver 8.8.8.8



cat /run/systemd/resolve/stub-resolv.conf
nameserver 127.0.0.53



cat /etc/systemd/resolved.conf
DNS = 8.8.8.8
FALLbackDNS=8.8.4.4
#Domains=
#LLMNR=NO
#MulticastDNS=NO
#DNSSEC=NO
#Cache=yes


/etc/bind/named.conf.options



options {
directory "/var/cache/bind";

listen-on port 53 (localhost; 10.161.10.0/24;};
allow-query {localhost; 10.161.10.0/24;};
forwarders {8.8.8.8, 8.8.4.4};
recursion yes;
auth-nxdomain no;

};


ip route show



default via 10.161.10.1 dev ens160 proto static
10.161.10.0/24 dev ens160 proto kernel scope link src 10.161.10.2









share|improve this question
























  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Thomas Ward
    Dec 7 at 17:02















up vote
1
down vote

favorite












I think I configured the bind dns server correctly on my ubuntu 18.04 server on my virtual network. I can ping my other server ' www.boblowlaw.com ' just fine and I can also ping 8.8.8.8 and I get



ping google.com: temporary failure in name resolution.


These are my results when I do a nslookup on www.boblowlaw.com & google.com



enter image description here



When I use the command systemctl-resolve --status this is my results



enter image description here



I've tried all types of different trouble shooting to try to figure out whats wrong and I just can't figure it out. Any advice/help would be appreicated



ls -al /etc/resolv.conf
- 1rwxrwxrwx 1 root root 32 Dec 3 21 21 /etc/resolv.conf -> /run/system/
resolve/resolv.conf

cat /etc/resolv.con
nameserver 10.161.10.2
nameserver 8.8.8.8

cat /etc/netplan/01-netcfg.yaml1
network:
renderer: networkd
ethernets:
ens160:
addresses:
- 10.161.10.2/24
gateway4: 10.161.10.1
nameservers:
addresses: [8.8.8.8]

cat /etc/systemd/resolve.conf
[Resolve]
DNS=10.161.10.2
#FallbackDNS=
#Domains=

cat /run/systemd/resolve/resolv.conf
nameserver 8.8.8.8



cat /run/systemd/resolve/stub-resolv.conf
nameserver 127.0.0.53



cat /etc/systemd/resolved.conf
DNS = 8.8.8.8
FALLbackDNS=8.8.4.4
#Domains=
#LLMNR=NO
#MulticastDNS=NO
#DNSSEC=NO
#Cache=yes


/etc/bind/named.conf.options



options {
directory "/var/cache/bind";

listen-on port 53 (localhost; 10.161.10.0/24;};
allow-query {localhost; 10.161.10.0/24;};
forwarders {8.8.8.8, 8.8.4.4};
recursion yes;
auth-nxdomain no;

};


ip route show



default via 10.161.10.1 dev ens160 proto static
10.161.10.0/24 dev ens160 proto kernel scope link src 10.161.10.2









share|improve this question
























  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Thomas Ward
    Dec 7 at 17:02













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I think I configured the bind dns server correctly on my ubuntu 18.04 server on my virtual network. I can ping my other server ' www.boblowlaw.com ' just fine and I can also ping 8.8.8.8 and I get



ping google.com: temporary failure in name resolution.


These are my results when I do a nslookup on www.boblowlaw.com & google.com



enter image description here



When I use the command systemctl-resolve --status this is my results



enter image description here



I've tried all types of different trouble shooting to try to figure out whats wrong and I just can't figure it out. Any advice/help would be appreicated



ls -al /etc/resolv.conf
- 1rwxrwxrwx 1 root root 32 Dec 3 21 21 /etc/resolv.conf -> /run/system/
resolve/resolv.conf

cat /etc/resolv.con
nameserver 10.161.10.2
nameserver 8.8.8.8

cat /etc/netplan/01-netcfg.yaml1
network:
renderer: networkd
ethernets:
ens160:
addresses:
- 10.161.10.2/24
gateway4: 10.161.10.1
nameservers:
addresses: [8.8.8.8]

cat /etc/systemd/resolve.conf
[Resolve]
DNS=10.161.10.2
#FallbackDNS=
#Domains=

cat /run/systemd/resolve/resolv.conf
nameserver 8.8.8.8



cat /run/systemd/resolve/stub-resolv.conf
nameserver 127.0.0.53



cat /etc/systemd/resolved.conf
DNS = 8.8.8.8
FALLbackDNS=8.8.4.4
#Domains=
#LLMNR=NO
#MulticastDNS=NO
#DNSSEC=NO
#Cache=yes


/etc/bind/named.conf.options



options {
directory "/var/cache/bind";

listen-on port 53 (localhost; 10.161.10.0/24;};
allow-query {localhost; 10.161.10.0/24;};
forwarders {8.8.8.8, 8.8.4.4};
recursion yes;
auth-nxdomain no;

};


ip route show



default via 10.161.10.1 dev ens160 proto static
10.161.10.0/24 dev ens160 proto kernel scope link src 10.161.10.2









share|improve this question















I think I configured the bind dns server correctly on my ubuntu 18.04 server on my virtual network. I can ping my other server ' www.boblowlaw.com ' just fine and I can also ping 8.8.8.8 and I get



ping google.com: temporary failure in name resolution.


These are my results when I do a nslookup on www.boblowlaw.com & google.com



enter image description here



When I use the command systemctl-resolve --status this is my results



enter image description here



I've tried all types of different trouble shooting to try to figure out whats wrong and I just can't figure it out. Any advice/help would be appreicated



ls -al /etc/resolv.conf
- 1rwxrwxrwx 1 root root 32 Dec 3 21 21 /etc/resolv.conf -> /run/system/
resolve/resolv.conf

cat /etc/resolv.con
nameserver 10.161.10.2
nameserver 8.8.8.8

cat /etc/netplan/01-netcfg.yaml1
network:
renderer: networkd
ethernets:
ens160:
addresses:
- 10.161.10.2/24
gateway4: 10.161.10.1
nameservers:
addresses: [8.8.8.8]

cat /etc/systemd/resolve.conf
[Resolve]
DNS=10.161.10.2
#FallbackDNS=
#Domains=

cat /run/systemd/resolve/resolv.conf
nameserver 8.8.8.8



cat /run/systemd/resolve/stub-resolv.conf
nameserver 127.0.0.53



cat /etc/systemd/resolved.conf
DNS = 8.8.8.8
FALLbackDNS=8.8.4.4
#Domains=
#LLMNR=NO
#MulticastDNS=NO
#DNSSEC=NO
#Cache=yes


/etc/bind/named.conf.options



options {
directory "/var/cache/bind";

listen-on port 53 (localhost; 10.161.10.0/24;};
allow-query {localhost; 10.161.10.0/24;};
forwarders {8.8.8.8, 8.8.4.4};
recursion yes;
auth-nxdomain no;

};


ip route show



default via 10.161.10.1 dev ens160 proto static
10.161.10.0/24 dev ens160 proto kernel scope link src 10.161.10.2






networking server dns display-resolution






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 7 at 0:23

























asked Dec 5 at 20:11









reed sager

63




63












  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Thomas Ward
    Dec 7 at 17:02


















  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Thomas Ward
    Dec 7 at 17:02
















Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward
Dec 7 at 17:02




Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward
Dec 7 at 17:02















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',
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


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098751%2fi-can-ping-my-host-domain-8-8-8-8-but-cant-ping-google-name-resolution-failure%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.





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














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098751%2fi-can-ping-my-host-domain-8-8-8-8-but-cant-ping-google-name-resolution-failure%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

Eduardo VII do Reino Unido