dns not work after fatcory default

[vividy]

After firmware update to 6.5.2, booting 99% and out of memory error occurred.

According to many advise here, I run backup & factory default.

After factory default, I set IP to fix 192.168.0.2 and add dns server 192.168.0.1 as usual.

I can access admin page at 192.168.0.2, but I can't send test mail from nas.

So i login into nas shell via ssh, it seems nas is refer to name server at 127.0.0.1.

But name server at 127.0.0.1 is not working.

Here is the output.

___________________________________________________________________________

admin@jwnas:~$ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver 127.0.0.1
nameserver ::1
admin@jwnas:~$ nslookup google.com
Server:    127.0.0.1
Address 1: 127.0.0.1 localhost

nslookup: can't resolve 'google.com'

___________________________________________________________________________

But there is a working local name server from netstat command.

___________________________________________________________________________

 admin@jwnas:~$ netstat -lnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:8200            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:10000           0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:3702            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     
tcp6       0      0 ::1:4700                :::*                    LISTEN     
tcp6       0      0 :::445                  :::*                    LISTEN     
tcp6       0      0 :::548                  :::*                    LISTEN     
tcp6       0      0 :::139                  :::*                    LISTEN     
tcp6       0      0 ::1:53                  :::*                    LISTEN     
tcp6       0      0 :::22                   :::*                    LISTEN     

___________________________________________________________________________

Then add 192.168.0.1 to resolv.conf, dns is working.

___________________________________________________________________________

admin@jwnas:~$ cat /etc/resolv.conf
# Generated by Connection Manager
nameserver 192.168.0.1
nameserver 127.0.0.1
nameserver ::1

admin@jwnas:~$ nslookup google.com
Server:    192.168.0.1
Address 1: 192.168.0.1 router.justware

Name:      google.com
Address 1: 216.58.200.206 nrt12s12-in-f14.1e100.net
Address 2: 2404:6800:4004:817::200e nrt12s12-in-x0e.1e100.net

___________________________________________________________________________

I don't think I have to add 192.168.0.1 to resolv.conf manually.

I think there is still something wrong. I want to clear all potential risk before restoring data.

What should I do now? Any suggestion?

Thanks.

[StephenB · Accepted solution]

127.0.0.1 is of course localhost.

Does it work if you add 8.8.8.8 as a DNS server?

BTW, a better strategy is to to leave the IP configuration as DHCP/Automatic in the NAS, and configure your router to reserve 192.168.0.2 for the NAS. Most routers provide a way to do this.

[StephenB · Accepted solution]

127.0.0.1 is of course localhost.

Does it work if you add 8.8.8.8 as a DNS server?

BTW, a better strategy is to to leave the IP configuration as DHCP/Automatic in the NAS, and configure your router to reserve 192.168.0.2 for the NAS. Most routers provide a way to do this.

[vividy]

First, delete added line from resolv.conf.

Then add 8.8.8.8 via admin page, IT WORKED!

And after that even if I change dns server back to 192.168.0.1, it still work!

Not very clear about the reason, but problem is gone, Thanks!