Debian 8 - Lan connection works but no internet [Unknown host]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















I have a Debian 8 server that has been running great for about a year. All of a sudden I am no longer getting internet access.



The server is connected over an ethernet cable and I can SSH into over the local network.



When I do ping www.google.com then I get Unknown Host. If I do ping 8.8.8.8 then it works.



So I would guess that it is a DNS issue? My /etc/network/interfaces file looks like this..



auto eth0
allow-hotplug eth0
iface eth0 inet dhcp


Where else should I be lookgin to resolve this?










share|improve this question



















  • 1





    What does it show in /etc/resolv.conf ?

    – Jesse_b
    Feb 9 at 20:26






  • 1





    /etc/resolv.conf is blank

    – fightstarr20
    Feb 9 at 20:30











  • Weird that it would become blank. Do you have any configuration management software in your environment, and are you hosting your own DNS servers?

    – Jesse_b
    Feb 9 at 20:39















1















I have a Debian 8 server that has been running great for about a year. All of a sudden I am no longer getting internet access.



The server is connected over an ethernet cable and I can SSH into over the local network.



When I do ping www.google.com then I get Unknown Host. If I do ping 8.8.8.8 then it works.



So I would guess that it is a DNS issue? My /etc/network/interfaces file looks like this..



auto eth0
allow-hotplug eth0
iface eth0 inet dhcp


Where else should I be lookgin to resolve this?










share|improve this question



















  • 1





    What does it show in /etc/resolv.conf ?

    – Jesse_b
    Feb 9 at 20:26






  • 1





    /etc/resolv.conf is blank

    – fightstarr20
    Feb 9 at 20:30











  • Weird that it would become blank. Do you have any configuration management software in your environment, and are you hosting your own DNS servers?

    – Jesse_b
    Feb 9 at 20:39













1












1








1








I have a Debian 8 server that has been running great for about a year. All of a sudden I am no longer getting internet access.



The server is connected over an ethernet cable and I can SSH into over the local network.



When I do ping www.google.com then I get Unknown Host. If I do ping 8.8.8.8 then it works.



So I would guess that it is a DNS issue? My /etc/network/interfaces file looks like this..



auto eth0
allow-hotplug eth0
iface eth0 inet dhcp


Where else should I be lookgin to resolve this?










share|improve this question
















I have a Debian 8 server that has been running great for about a year. All of a sudden I am no longer getting internet access.



The server is connected over an ethernet cable and I can SSH into over the local network.



When I do ping www.google.com then I get Unknown Host. If I do ping 8.8.8.8 then it works.



So I would guess that it is a DNS issue? My /etc/network/interfaces file looks like this..



auto eth0
allow-hotplug eth0
iface eth0 inet dhcp


Where else should I be lookgin to resolve this?







linux debian dns






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 9 at 23:08









AnFi

1,11959




1,11959










asked Feb 9 at 20:24









fightstarr20fightstarr20

13016




13016







  • 1





    What does it show in /etc/resolv.conf ?

    – Jesse_b
    Feb 9 at 20:26






  • 1





    /etc/resolv.conf is blank

    – fightstarr20
    Feb 9 at 20:30











  • Weird that it would become blank. Do you have any configuration management software in your environment, and are you hosting your own DNS servers?

    – Jesse_b
    Feb 9 at 20:39












  • 1





    What does it show in /etc/resolv.conf ?

    – Jesse_b
    Feb 9 at 20:26






  • 1





    /etc/resolv.conf is blank

    – fightstarr20
    Feb 9 at 20:30











  • Weird that it would become blank. Do you have any configuration management software in your environment, and are you hosting your own DNS servers?

    – Jesse_b
    Feb 9 at 20:39







1




1





What does it show in /etc/resolv.conf ?

– Jesse_b
Feb 9 at 20:26





What does it show in /etc/resolv.conf ?

– Jesse_b
Feb 9 at 20:26




1




1





/etc/resolv.conf is blank

– fightstarr20
Feb 9 at 20:30





/etc/resolv.conf is blank

– fightstarr20
Feb 9 at 20:30













Weird that it would become blank. Do you have any configuration management software in your environment, and are you hosting your own DNS servers?

– Jesse_b
Feb 9 at 20:39





Weird that it would become blank. Do you have any configuration management software in your environment, and are you hosting your own DNS servers?

– Jesse_b
Feb 9 at 20:39










1 Answer
1






active

oldest

votes


















1














I would try updating your /etc/resolv.conf file with the following:



nameserver 8.8.8.8
nameserver 8.8.4.4
search local


8.8.8.8 and 8.8.4.4 are Google's public DNS servers as you seem to already be aware of.




nameserver Name server IP address




Internet address of a name server that the resolver should
query, either an IPv4 address (in dot notation), or an IPv6
address in colon (and possibly dot) notation as per RFC 2373.
Up to MAXNS (currently 3, see ) name servers may be
listed, one per keyword. If there are multiple servers, the
resolver library queries them in the order listed. If no
nameserver entries are present, the default is to use the name
server on the local machine. (The algorithm used is to try a
name server, and if the query times out, try the next, until
out of name servers, then repeat trying all the name servers
until a maximum number of retries are made.)







search Search list for host-name lookup.




The search list is normally determined from the local domain
name; by default, it contains only the local domain name.
This may be changed by listing the desired domain search path
following the search keyword with spaces or tabs separating
the names. Resolver queries having fewer than ndots dots
(default is 1) in them will be attempted using each component
of the search path in turn until a match is found. For
environments with multiple subdomains please read options
ndots:n below to avoid man-in-the-middle attacks and
unnecessary traffic for the root-dns-servers. Note that this
process may be slow and will generate a lot of network traffic
if the servers for the listed domains are not local, and that
queries will time out if no server is available for one of the
domains.
The search list is currently limited to six domains with a
total of 256 characters.





resolv.conf(5)






share|improve this answer


















  • 1





    Thank you that did it. This server has reached EOL so it only has to survive for another 3 weeks. This will do until then :) Thanks for your solution, much appreciated

    – fightstarr20
    Feb 9 at 20:46










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/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%2funix.stackexchange.com%2fquestions%2f499684%2fdebian-8-lan-connection-works-but-no-internet-unknown-host%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














I would try updating your /etc/resolv.conf file with the following:



nameserver 8.8.8.8
nameserver 8.8.4.4
search local


8.8.8.8 and 8.8.4.4 are Google's public DNS servers as you seem to already be aware of.




nameserver Name server IP address




Internet address of a name server that the resolver should
query, either an IPv4 address (in dot notation), or an IPv6
address in colon (and possibly dot) notation as per RFC 2373.
Up to MAXNS (currently 3, see ) name servers may be
listed, one per keyword. If there are multiple servers, the
resolver library queries them in the order listed. If no
nameserver entries are present, the default is to use the name
server on the local machine. (The algorithm used is to try a
name server, and if the query times out, try the next, until
out of name servers, then repeat trying all the name servers
until a maximum number of retries are made.)







search Search list for host-name lookup.




The search list is normally determined from the local domain
name; by default, it contains only the local domain name.
This may be changed by listing the desired domain search path
following the search keyword with spaces or tabs separating
the names. Resolver queries having fewer than ndots dots
(default is 1) in them will be attempted using each component
of the search path in turn until a match is found. For
environments with multiple subdomains please read options
ndots:n below to avoid man-in-the-middle attacks and
unnecessary traffic for the root-dns-servers. Note that this
process may be slow and will generate a lot of network traffic
if the servers for the listed domains are not local, and that
queries will time out if no server is available for one of the
domains.
The search list is currently limited to six domains with a
total of 256 characters.





resolv.conf(5)






share|improve this answer


















  • 1





    Thank you that did it. This server has reached EOL so it only has to survive for another 3 weeks. This will do until then :) Thanks for your solution, much appreciated

    – fightstarr20
    Feb 9 at 20:46















1














I would try updating your /etc/resolv.conf file with the following:



nameserver 8.8.8.8
nameserver 8.8.4.4
search local


8.8.8.8 and 8.8.4.4 are Google's public DNS servers as you seem to already be aware of.




nameserver Name server IP address




Internet address of a name server that the resolver should
query, either an IPv4 address (in dot notation), or an IPv6
address in colon (and possibly dot) notation as per RFC 2373.
Up to MAXNS (currently 3, see ) name servers may be
listed, one per keyword. If there are multiple servers, the
resolver library queries them in the order listed. If no
nameserver entries are present, the default is to use the name
server on the local machine. (The algorithm used is to try a
name server, and if the query times out, try the next, until
out of name servers, then repeat trying all the name servers
until a maximum number of retries are made.)







search Search list for host-name lookup.




The search list is normally determined from the local domain
name; by default, it contains only the local domain name.
This may be changed by listing the desired domain search path
following the search keyword with spaces or tabs separating
the names. Resolver queries having fewer than ndots dots
(default is 1) in them will be attempted using each component
of the search path in turn until a match is found. For
environments with multiple subdomains please read options
ndots:n below to avoid man-in-the-middle attacks and
unnecessary traffic for the root-dns-servers. Note that this
process may be slow and will generate a lot of network traffic
if the servers for the listed domains are not local, and that
queries will time out if no server is available for one of the
domains.
The search list is currently limited to six domains with a
total of 256 characters.





resolv.conf(5)






share|improve this answer


















  • 1





    Thank you that did it. This server has reached EOL so it only has to survive for another 3 weeks. This will do until then :) Thanks for your solution, much appreciated

    – fightstarr20
    Feb 9 at 20:46













1












1








1







I would try updating your /etc/resolv.conf file with the following:



nameserver 8.8.8.8
nameserver 8.8.4.4
search local


8.8.8.8 and 8.8.4.4 are Google's public DNS servers as you seem to already be aware of.




nameserver Name server IP address




Internet address of a name server that the resolver should
query, either an IPv4 address (in dot notation), or an IPv6
address in colon (and possibly dot) notation as per RFC 2373.
Up to MAXNS (currently 3, see ) name servers may be
listed, one per keyword. If there are multiple servers, the
resolver library queries them in the order listed. If no
nameserver entries are present, the default is to use the name
server on the local machine. (The algorithm used is to try a
name server, and if the query times out, try the next, until
out of name servers, then repeat trying all the name servers
until a maximum number of retries are made.)







search Search list for host-name lookup.




The search list is normally determined from the local domain
name; by default, it contains only the local domain name.
This may be changed by listing the desired domain search path
following the search keyword with spaces or tabs separating
the names. Resolver queries having fewer than ndots dots
(default is 1) in them will be attempted using each component
of the search path in turn until a match is found. For
environments with multiple subdomains please read options
ndots:n below to avoid man-in-the-middle attacks and
unnecessary traffic for the root-dns-servers. Note that this
process may be slow and will generate a lot of network traffic
if the servers for the listed domains are not local, and that
queries will time out if no server is available for one of the
domains.
The search list is currently limited to six domains with a
total of 256 characters.





resolv.conf(5)






share|improve this answer













I would try updating your /etc/resolv.conf file with the following:



nameserver 8.8.8.8
nameserver 8.8.4.4
search local


8.8.8.8 and 8.8.4.4 are Google's public DNS servers as you seem to already be aware of.




nameserver Name server IP address




Internet address of a name server that the resolver should
query, either an IPv4 address (in dot notation), or an IPv6
address in colon (and possibly dot) notation as per RFC 2373.
Up to MAXNS (currently 3, see ) name servers may be
listed, one per keyword. If there are multiple servers, the
resolver library queries them in the order listed. If no
nameserver entries are present, the default is to use the name
server on the local machine. (The algorithm used is to try a
name server, and if the query times out, try the next, until
out of name servers, then repeat trying all the name servers
until a maximum number of retries are made.)







search Search list for host-name lookup.




The search list is normally determined from the local domain
name; by default, it contains only the local domain name.
This may be changed by listing the desired domain search path
following the search keyword with spaces or tabs separating
the names. Resolver queries having fewer than ndots dots
(default is 1) in them will be attempted using each component
of the search path in turn until a match is found. For
environments with multiple subdomains please read options
ndots:n below to avoid man-in-the-middle attacks and
unnecessary traffic for the root-dns-servers. Note that this
process may be slow and will generate a lot of network traffic
if the servers for the listed domains are not local, and that
queries will time out if no server is available for one of the
domains.
The search list is currently limited to six domains with a
total of 256 characters.





resolv.conf(5)







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 9 at 20:31









Jesse_bJesse_b

13.2k23369




13.2k23369







  • 1





    Thank you that did it. This server has reached EOL so it only has to survive for another 3 weeks. This will do until then :) Thanks for your solution, much appreciated

    – fightstarr20
    Feb 9 at 20:46












  • 1





    Thank you that did it. This server has reached EOL so it only has to survive for another 3 weeks. This will do until then :) Thanks for your solution, much appreciated

    – fightstarr20
    Feb 9 at 20:46







1




1





Thank you that did it. This server has reached EOL so it only has to survive for another 3 weeks. This will do until then :) Thanks for your solution, much appreciated

– fightstarr20
Feb 9 at 20:46





Thank you that did it. This server has reached EOL so it only has to survive for another 3 weeks. This will do until then :) Thanks for your solution, much appreciated

– fightstarr20
Feb 9 at 20:46

















draft saved

draft discarded
















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499684%2fdebian-8-lan-connection-works-but-no-internet-unknown-host%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

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)