DNS can’t resolve hosts?

[pfiozzo]

you can disable IPV6, w/o revert back to previous revision of firmware

That worked for me as well. Disabled IPV6 + reboot and now DNS resolution is working correctly.
Thanks!

[peelos]

thanks for this - disabling IPv6 in the virtual switch settings seems to be the solution here

[peelos]

anyone else having dnsmasq process running at high (13%) CPU usage? Also have the DNS message still popping up even after switching off IPv6..

[ereche]

anyone else having dnsmasq process running at high (13%) CPU usage? Also have the DNS message still popping up even after switching off IPv6..

Yep. The same here. Using the last QTS 5.0 firmware. Never happened before.

[herbie28]

Yes I agree. I've wasted soooooo.... much time trying to resolve this and have come to the conclusion it's something to do with the upgrade to v5.0. It's completely stuffed my ability to use my VPN because of DNS leakage issues too.

[peelos]

Also wasted a bunch of time here, might need to bite the bullet and roll back to previous firmware..

[jimmy999]

I noticed in the release notes that there is some issue of "Auto router configuration" affecting connectivity. I disabled the auto router configuration in myQNAPcloud and that seems to have sorted out the connectivity issue. I was able to update the apps in app centre the DNS error message is gone. Hopefully they will fix it with the next release

EDIT: After updating all the apps like QuFirewall, QVPN etc. I switched the auto configuration back on. This time NAS did not lose connectivity, so maybe an issue lies with the update for some of the apps. Just to note - I have no clue about DNS, manual configs etc. This workaround worked for me and I hope it will work for you

[LovelyCupOfTea]

Same Issue here, TVS 871. worked perfectly until QTS 5 update. Get the same DNS message

No apps connect due to the DNS issue, I have tried some of the remedies above and also swapped ports and tried manual IP config, turned off IPV6, Set DNS to router and router to forward, tried setting it to google DNS even but still nothing. ( I don't have myqnapcloud installed)

Driving me bananas! Clearly this is an issue caused by QTS 5

Any other suggestions or ways to fix please advise as at the moment I cannot use my Qnap and I have spent hours trying to resolve. Was about to roll back the firmware then got a long message about it not supporting rolling back so didn't want to proceed.

Can someone advise how to update the resolv.conf please as I have not done this.

[peelos]

Same issue, stuck and not even Qtransmission works anymore.. editing resolve.conf to manually specify my DNS server has also not solved this issue. No way to roll back based on support messages .. What a nightmare firmware upgrade that was / is.

[hhliu]

Same. The problem seems gone after forcing my DHCP server on the router to use 8.8.8.8 and 8.8.4.4 as the offerings of DNS server instead of ISP's. Before that, I had rebooted NAS several times but in vain. Have not changed any configurations of NAS, though, and have no idea what's going on with the problem. But anyway, so far so good for 2 days. Keep fingers crossed. QNAP, it's your responsibility to figure it out!!

[holger_kuehn]

editing /etc/resolv.conf does not work on the TS-873U-RP I am managing, it gets reset on every reboot
testing edits to dnsmasq.conf instead

[adam_jannetta]

Same issue here after upgrading to 5.0. Tried disabling IPv6 and rebooting, no luck.

I was able to use a workaround by manually editing /etc/resolv.conf and adding my DNS server back in. But I don't think that will persist on a reboot. This is what it looks like post 5.0 upgrade:

Code: Select all

[~] # more /etc/resolv.conf 
nameserver 127.0.1.1

Have we heard from QNAP? Clearly a bug.

[gipasoft]

Same issue after qts 5 installation, this the last qnap support reply:

"It has been escalated to our development team, please wait for an update."

Inviato dal mio GM1913 utilizzando Tapatalk

[dosborne]

Everyone - PLEASE log the issue with QNAP. It is the only way to get the issue properly fixed. The more people that log it, the more likely and quicker it will get resolved.

[BigAtom]

QVPN Service has just been updated in AppCenter. I've just installed it but I also disabled then enable IPv6 then rebooted so not sure which one fixed the issue.