NO DNS RESOLUTION

IPv4/6, Port, VPN, proxy, SSH, remote access and more.
Locked
User avatar
deejc
Posts: 111
Joined: 09 Mar 2021, 03:35

NO DNS RESOLUTION

Post by deejc »

today i wanted to look into getting backblaze working on my account, oogged into the TOS front end, the HELP screen opened but alerted, no internet connection, i tried to open backblaze, and i only get a blank screen

i ssh in, try to resolve google.com ,

Code: Select all

nslookup: can't resolve 'google.com'
[root@MEDIA user]# nslookup google.com
Server:    127.0.0.1
Address 1: 127.0.0.1 MEDIA
nslookup: can't resolve 'google.com'
cat /etc/resolv.conf
Empty File.

i set network interface from DHCP to manual. .. still no resolution, i set interface back to DHCP still no resoltion

manually edited resolv.conf and add in 1.1.1.1 and 1.0.0.1

Code: Select all

[root@MEDIA user]# nslookup google.com
Server:    1.1.1.1
Address 1: 1.1.1.1 one.one.one.one

Name:      google.com
Address 1: 172.217.20.142 google.com
Address 2: 2a00:1450:4009:801::200e google.com
any ideas why i lost resolution ? it was working last week ?
F2-220 WITH 2 x WD RED 2TB RUNNING 4.2.17
User avatar
TMRyan
TerraMaster Team
Posts: 817
Joined: 01 Dec 2020, 11:50

Re: NO DNS RESOLUTION

Post by TMRyan »

This should be a problem with your network.
You can first try to obtain the IP manually.
The first three digits of IP and gateway need to be the same.
net.png
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement)
User avatar
deejc
Posts: 111
Joined: 09 Mar 2021, 03:35

Re: NO DNS RESOLUTION

Post by deejc »

Of course I tried manual but still no DNS resolution the I went back to DHCP and still no resolution until. I manually edit resolv.conf
F2-220 WITH 2 x WD RED 2TB RUNNING 4.2.17
User avatar
deejc
Posts: 111
Joined: 09 Mar 2021, 03:35

Re: NO DNS RESOLUTION - RESOLVED

Post by deejc »

BTW, i rebooted the NAS and now its OK :!: :!:
maybe you should recommend this before anything else.
F2-220 WITH 2 x WD RED 2TB RUNNING 4.2.17
Locked