Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[Solved] - Loss of DNS
[Solved] - Loss of DNS
my Debian server is running Debian 10 - Buster.
recently updated to Debian 4.19.0-25-amd64 - Debian 4.19.289-1
sometimes I loose DNS
when that happens, I can not ping any outside website.
my solution is, to reboot my server
that always sobes the problem
but there must me an easier way to get DNS back, I hope
any suggesntions ??
recently updated to Debian 4.19.0-25-amd64 - Debian 4.19.289-1
sometimes I loose DNS
when that happens, I can not ping any outside website.
my solution is, to reboot my server
that always sobes the problem
but there must me an easier way to get DNS back, I hope
any suggesntions ??
Last edited by fred44nl on 2024-05-04 21:23, edited 1 time in total.
Debian 12 - Bookworm on Compulab Fitlet2
-
- Global Moderator
- Posts: 3103
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 77 times
- Been thanked: 419 times
Re: Loss of DNS
sorry, I am more of an amateur
so I find that DNS stopted working and I only know, that a reboot does solve the problem and bring DNS back, of course
I am open for suggestions
so I find that DNS stopted working and I only know, that a reboot does solve the problem and bring DNS back, of course
I am open for suggestions
Debian 12 - Bookworm on Compulab Fitlet2
- Northpoint
- Posts: 91
- Joined: 2020-12-19 10:51
- Location: USA
- Has thanked: 51 times
- Been thanked: 13 times
Re: Loss of DNS
When its working correctly, Check your /etc/resolv.conf file and post its contents. Then when its not post the contents again.
Also, Please post the output of :
and
Also, Please post the output of :
Code: Select all
ip addr
Code: Select all
ip route
Get your linux on.
Re: Loss of DNS
thank you so far.
here is the output when working.
will come back when not working.
fred44nl@Debian:~$
fred44nl@Debian:~$ cat /etc/resolv.conf
# Generated by dhcpcd from eno1.dhcp
# /etc/resolv.conf.head can replace this line
domain WORKGROUP
nameserver 1.1.1.1
nameserver 192.168.1.1
# /etc/resolv.conf.tail can replace this line
fred44nl@Debian:~$
fred44nl@Debian:~$
fred44nl@Debian:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:01:c0:20:75:6d brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:01:c0:20:75:6e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.29/24 brd 192.168.1.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80:9622:ce1:d7e/64 scope link
valid_lft forever preferred_lft forever
fred44nl@Debian:~$
fred44nl@Debian:~$
fred44nl@Debian:~$ ip route
default via 192.168.1.1 dev eno1 proto dhcp src 192.168.1.29 metric 203
192.168.1.0/24 dev eno1 proto dhcp scope link src 192.168.1.29 metric 203
fred44nl@Debian:~$
here is the output when working.
will come back when not working.
fred44nl@Debian:~$
fred44nl@Debian:~$ cat /etc/resolv.conf
# Generated by dhcpcd from eno1.dhcp
# /etc/resolv.conf.head can replace this line
domain WORKGROUP
nameserver 1.1.1.1
nameserver 192.168.1.1
# /etc/resolv.conf.tail can replace this line
fred44nl@Debian:~$
fred44nl@Debian:~$
fred44nl@Debian:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:01:c0:20:75:6d brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:01:c0:20:75:6e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.29/24 brd 192.168.1.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80:9622:ce1:d7e/64 scope link
valid_lft forever preferred_lft forever
fred44nl@Debian:~$
fred44nl@Debian:~$
fred44nl@Debian:~$ ip route
default via 192.168.1.1 dev eno1 proto dhcp src 192.168.1.29 metric 203
192.168.1.0/24 dev eno1 proto dhcp scope link src 192.168.1.29 metric 203
fred44nl@Debian:~$
Debian 12 - Bookworm on Compulab Fitlet2
- Northpoint
- Posts: 91
- Joined: 2020-12-19 10:51
- Location: USA
- Has thanked: 51 times
- Been thanked: 13 times
Re: Loss of DNS
Ok, Now we have a 'base' of the proper working network setup. When the network fails then repost the output of the commands again so we can see if anything has changed. You save the output of the commands to a file by redirecting it in each command. Just append this to the end of each command and give it a new file name (network-error-1, network-error-2 ect... :
Code: Select all
> network-error.txt
Get your linux on.
- sunrat
- Administrator
- Posts: 6615
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 120 times
- Been thanked: 509 times
Re: Loss of DNS
@fred44nl please use code tags for terminal text output.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Re: Loss of DNS
it has been a very long time before the network problem came back.
but as before DNS is not working, meaning that I cannot access outside servers or websites.
below, I will post the output of the commands for inspecting this.
from what I can see the file /etc/resolv.conf is empty.
it has a size of 0 bytes.
this looks the same as before.
this also looks the same for me.
as you can see nothing appears.
the file is empty
I will go and find the contents of resolv.conf and make the file original again.
see what happens
edit1:
after restoring the file /etc/resolv.conf, DNS was working again properly.
edit2:
My machine is now updated from Buster to Bullseye
but as before DNS is not working, meaning that I cannot access outside servers or websites.
below, I will post the output of the commands for inspecting this.
from what I can see the file /etc/resolv.conf is empty.
it has a size of 0 bytes.
Code: Select all
fred44nl@Debian:~$ ip route
default via 192.168.1.1 dev eno1 proto dhcp src 192.168.1.29 metric 203
192.168.1.0/24 dev eno1 proto dhcp scope link src 192.168.1.29 metric 203
fred44nl@Debian:~$
Code: Select all
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:01:c0:20:75:6d brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:01:c0:20:75:6e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.29/24 brd 192.168.1.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80::2b70:9622:ce1:d7e/64 scope link
valid_lft forever preferred_lft forever
Code: Select all
fred44nl@Debian:~$ cat /etc/resolv.conf
fred44nl@Debian:~$
Code: Select all
fred44nl@Debian:~$ ls -al /etc/resolv.conf
-rw-r--r-- 1 root root 0 mei 2 01:16 /etc/resolv.conf
fred44nl@Debian:~$
I will go and find the contents of resolv.conf and make the file original again.
see what happens
edit1:
after restoring the file /etc/resolv.conf, DNS was working again properly.
edit2:
My machine is now updated from Buster to Bullseye
Debian 12 - Bookworm on Compulab Fitlet2
-
- Global Moderator
- Posts: 3103
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 77 times
- Been thanked: 419 times
Re: Loss of DNS
Hello,
Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message.
I'm glad you sorted it out. :)
Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message.