Debian - DNS Issue - Can resolve IPs, not domains
Multi tool use
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have someone limited experience with linux and definitely limited to when it comes to networking config on linux.
I am able to resolve IPs so I can do things like ping 127.217.12.206, but cannot ping google.com. This causes a number of other issues like being able to get packages during apt-get update.
Interestingly (at least to me) is that if I restart the network manager (with /etc/init.d/network-manager restart) I can resolve domains temporarily. Sometimes a few minutes, sometimes only for one command.
Some files:
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 debian-HomeServer
#192.168.1.45 debian-HomeServer
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
/etc/network/interfaces.d/:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
#source /etc/network/interfaces.d/*
# The loopback network interface
auto eth0
iface lo inet loopback
/etc/resolv.conf:
Is Blank and deletes anything (like nameserver 8.8.8.8) that I put in there.
I've been going through StackExchange amoung a number of other threads over the last week when I have some free time, but haven't been able to make anything stick. I have made a number of changes and some might still be in settings that should be. This started happening some time months ago before I moved, but only just got to setting it back up. It used to resolve no issue.
debian networking dns
asked Feb 15 at 18:23
SirInquire
1
add a comment |Â
up vote
0
down vote
favorite
I have someone limited experience with linux and definitely limited to when it comes to networking config on linux.
I am able to resolve IPs so I can do things like ping 127.217.12.206, but cannot ping google.com. This causes a number of other issues like being able to get packages during apt-get update.
Interestingly (at least to me) is that if I restart the network manager (with /etc/init.d/network-manager restart) I can resolve domains temporarily. Sometimes a few minutes, sometimes only for one command.
Some files:
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 debian-HomeServer
#192.168.1.45 debian-HomeServer
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
/etc/network/interfaces.d/:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
#source /etc/network/interfaces.d/*
# The loopback network interface
auto eth0
iface lo inet loopback
/etc/resolv.conf:
Is Blank and deletes anything (like nameserver 8.8.8.8) that I put in there.
I've been going through StackExchange amoung a number of other threads over the last week when I have some free time, but haven't been able to make anything stick. I have made a number of changes and some might still be in settings that should be. This started happening some time months ago before I moved, but only just got to setting it back up. It used to resolve no issue.
debian networking dns
asked Feb 15 at 18:23
SirInquire
1
3
Try creating a newresolv.confand making it immutable (chattr +i /etc/resolv.conf), and looking in the logs to see what screams about not being able to "properly" update it.
– DopeGhoti
Feb 15 at 18:25
1
@DopeGhoti I didn't know about chattr, thank you for that! I was able to edit /etc/resolv.conf and immute it quick enough after that it has not been cleared yet. With nameserver 8.8.8.8 actually staying in it now domain resolving is working normal again. Now I can proceed to try and figure out what was editing it. Very much appreciated, thank you!
– SirInquire
Feb 15 at 19:33
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have someone limited experience with linux and definitely limited to when it comes to networking config on linux.
I am able to resolve IPs so I can do things like ping 127.217.12.206, but cannot ping google.com. This causes a number of other issues like being able to get packages during apt-get update.
Interestingly (at least to me) is that if I restart the network manager (with /etc/init.d/network-manager restart) I can resolve domains temporarily. Sometimes a few minutes, sometimes only for one command.
Some files:
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 debian-HomeServer
#192.168.1.45 debian-HomeServer
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
/etc/network/interfaces.d/:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
#source /etc/network/interfaces.d/*
# The loopback network interface
auto eth0
iface lo inet loopback
/etc/resolv.conf:
Is Blank and deletes anything (like nameserver 8.8.8.8) that I put in there.
I've been going through StackExchange amoung a number of other threads over the last week when I have some free time, but haven't been able to make anything stick. I have made a number of changes and some might still be in settings that should be. This started happening some time months ago before I moved, but only just got to setting it back up. It used to resolve no issue.
debian networking dns
asked Feb 15 at 18:23
SirInquire
1
I have someone limited experience with linux and definitely limited to when it comes to networking config on linux.
I am able to resolve IPs so I can do things like ping 127.217.12.206, but cannot ping google.com. This causes a number of other issues like being able to get packages during apt-get update.
Interestingly (at least to me) is that if I restart the network manager (with /etc/init.d/network-manager restart) I can resolve domains temporarily. Sometimes a few minutes, sometimes only for one command.
Some files:
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 debian-HomeServer
#192.168.1.45 debian-HomeServer
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
/etc/network/interfaces.d/:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
#source /etc/network/interfaces.d/*
# The loopback network interface
auto eth0
iface lo inet loopback
/etc/resolv.conf:
Is Blank and deletes anything (like nameserver 8.8.8.8) that I put in there.
I've been going through StackExchange amoung a number of other threads over the last week when I have some free time, but haven't been able to make anything stick. I have made a number of changes and some might still be in settings that should be. This started happening some time months ago before I moved, but only just got to setting it back up. It used to resolve no issue.
debian networking dns
asked Feb 15 at 18:23
SirInquire
1
asked Feb 15 at 18:23
SirInquire
1
asked Feb 15 at 18:23
SirInquire
1
asked Feb 15 at 18:23
SirInquire
1
1
3
Try creating a newresolv.confand making it immutable (chattr +i /etc/resolv.conf), and looking in the logs to see what screams about not being able to "properly" update it.
– DopeGhoti
Feb 15 at 18:25
1
@DopeGhoti I didn't know about chattr, thank you for that! I was able to edit /etc/resolv.conf and immute it quick enough after that it has not been cleared yet. With nameserver 8.8.8.8 actually staying in it now domain resolving is working normal again. Now I can proceed to try and figure out what was editing it. Very much appreciated, thank you!
– SirInquire
Feb 15 at 19:33
add a comment |Â
3
Try creating a newresolv.confand making it immutable (chattr +i /etc/resolv.conf), and looking in the logs to see what screams about not being able to "properly" update it.
– DopeGhoti
Feb 15 at 18:25
1
@DopeGhoti I didn't know about chattr, thank you for that! I was able to edit /etc/resolv.conf and immute it quick enough after that it has not been cleared yet. With nameserver 8.8.8.8 actually staying in it now domain resolving is working normal again. Now I can proceed to try and figure out what was editing it. Very much appreciated, thank you!
– SirInquire
Feb 15 at 19:33
3
3
Try creating a new
resolv.conf and making it immutable (chattr +i /etc/resolv.conf), and looking in the logs to see what screams about not being able to "properly" update it.– DopeGhoti
Feb 15 at 18:25
Try creating a new
resolv.conf and making it immutable (chattr +i /etc/resolv.conf), and looking in the logs to see what screams about not being able to "properly" update it.– DopeGhoti
Feb 15 at 18:25
1
1
@DopeGhoti I didn't know about chattr, thank you for that! I was able to edit /etc/resolv.conf and immute it quick enough after that it has not been cleared yet. With nameserver 8.8.8.8 actually staying in it now domain resolving is working normal again. Now I can proceed to try and figure out what was editing it. Very much appreciated, thank you!
– SirInquire
Feb 15 at 19:33
@DopeGhoti I didn't know about chattr, thank you for that! I was able to edit /etc/resolv.conf and immute it quick enough after that it has not been cleared yet. With nameserver 8.8.8.8 actually staying in it now domain resolving is working normal again. Now I can proceed to try and figure out what was editing it. Very much appreciated, thank you!
– SirInquire
Feb 15 at 19:33
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f424435%2fdebian-dns-issue-can-resolve-ips-not-domains%23new-answer', 'question_page');
);
Post as a guest
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
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
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
3
Try creating a new
resolv.confand making it immutable (chattr +i /etc/resolv.conf), and looking in the logs to see what screams about not being able to "properly" update it.– DopeGhoti
Feb 15 at 18:25
1
@DopeGhoti I didn't know about chattr, thank you for that! I was able to edit /etc/resolv.conf and immute it quick enough after that it has not been cleared yet. With nameserver 8.8.8.8 actually staying in it now domain resolving is working normal again. Now I can proceed to try and figure out what was editing it. Very much appreciated, thank you!
– SirInquire
Feb 15 at 19:33