Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

DNS not resolving correctly Unraid 7.2.0-rc.2

  • Closed

DNS is acting strangely resolving to 127.0.0.1 . My Linux laptop on the exact same network using the exact same DNS 1.0.0.1 (cloudflare) resolves just fine, but Unraid does not. This issue is also passed down to the Dockers as well.

Laptop

dig bitsearch.to                                                                                                                       

; <<>> DiG 9.20.13 <<>> bitsearch.to
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19339
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 3

;; QUESTION SECTION:
;bitsearch.to.                  IN      A

;; ANSWER SECTION:
bitsearch.to.           17      IN      A       172.67.198.127
bitsearch.to.           17      IN      A       104.21.52.117

;; ADDITIONAL SECTION:
inf.portmaster.         0       IN      TXT     "accepted: allowing dns request"
inf.portmaster.         0       IN      TXT     "freshly resolved by Cloudflare (dot://cloudflare-dns.com:853#config)"
inf.portmaster.         0       IN      TXT     "record valid for 3m17s"

;; Query time: 56 msec
;; SERVER: 1.0.0.1#53(1.0.0.1) (UDP)
;; WHEN: Sat Nov 01 23:43:12 CDT 2025
;; MSG SIZE  rcvd: 287



cat /etc/resolv.conf                                                                                                                   
# Generated by NetworkManager
nameserver 1.0.0.1
nameserver 1.1.1.1

ping bitsearch.to                                                                                                                     1 ✘ 
PING bitsearch.to (172.67.198.127) 56(84) bytes of data.
64 bytes from 172.67.198.127: icmp_seq=1 ttl=59 time=14.8 ms
64 bytes from 172.67.198.127: icmp_seq=2 ttl=59 time=13.7 ms
^C
--- bitsearch.to ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 13.747/14.253/14.759/0.506 ms

Unraid

~# dig bitsearch.to

; <<>> DiG 9.20.13 <<>> bitsearch.to
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27484
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; MBZ: 0x0900, udp: 1232
;; QUESTION SECTION:
;bitsearch.to.                  IN      A

;; ANSWER SECTION:
bitsearch.to.           2311    IN      A       0.0.0.0

;; Query time: 1 msec
;; SERVER: 1.0.0.1#53(1.0.0.1) (UDP)
;; WHEN: Sat Nov 01 23:47:08 CDT 2025
;; MSG SIZE  rcvd: 69

~# cat /etc/resolv.conf
# Generated by rc.inet1
nameserver 1.0.0.1  # eth0:v4

~# ping bitsearch.to
PING bitsearch.to (127.0.0.1) 56(84) bytes of data.
64 bytes from Unraid (127.0.0.1): icmp_seq=1 ttl=64 time=0.015 ms
64 bytes from Unraid (127.0.0.1): icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from Unraid (127.0.0.1): icmp_seq=3 ttl=64 time=0.019 ms
64 bytes from Unraid (127.0.0.1): icmp_seq=4 ttl=64 time=0.038 ms
^C
--- bitsearch.to ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3099ms
rtt min/avg/max/mdev = 0.015/0.024/0.038/0.008 ms

When testing inside Dockers, they mimic the host and have the same issue.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.