starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Temporary failure in name resolution #372

New Issue
Closed
opened 2025-12-29 01:27:51 +01:00 by adam · 1 comment
adam commented 2025-12-29 01:27:51 +01:00
Owner
Copy Link

Originally created by @doebi on GitHub (Nov 14, 2022).

Bug description

MagicDNS is not working and I don't know what is going on or how to approach this issue. It occured to me after a reboot of my notebook, and trying to log in to my server:

> $ ssh server1                                                                                                                        
ssh: Could not resolve hostname server1: Temporary failure in name resolution

while tailscale status reports...

100.64.0.1      <this machine>            private      linux   -
100.64.0.2      server1                   private      linux   active; offers exit node; direct X.X.X.X:1234, tx 1332 rx 1452
100.64.0.4      raspi                     private      linux   offline
100.64.0.3      server2                   private      linux   active; offers exit node; direct X.X.X.X:1234, tx 276 rx 156

...the public and even the tailscale IP are pingable...

> $ ping 100.64.0.2                                                                                         
PING 100.64.0.2 (100.64.0.2) 56(84) bytes of data.
64 bytes from 100.64.0.2: icmp_seq=1 ttl=64 time=2.58 ms
64 bytes from 100.64.0.2: icmp_seq=2 ttl=64 time=2.77 ms
64 bytes from 100.64.0.2: icmp_seq=3 ttl=64 time=2.94 ms
64 bytes from 100.64.0.2: icmp_seq=4 ttl=64 time=2.72 ms

...but dig returns an empty response:

> $ dig server1                                                                                              

; <<>> DiG 9.18.1-1ubuntu1.2-Ubuntu <<>> server1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4207
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4095
;; QUESTION SECTION:
;server1.				IN	A

;; Query time: 4 msec
;; SERVER: 100.100.100.100#53(100.100.100.100) (UDP)
;; WHEN: Mon Nov 14 22:18:33 CET 2022
;; MSG SIZE  rcvd: 35

other DNS requests work just fine:

> $ dig google.com                                                                                                                     

; <<>> DiG 9.18.1-1ubuntu1.2-Ubuntu <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 957
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4095
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		291	IN	A	142.251.36.110

;; Query time: 8 msec
;; SERVER: 100.100.100.100#53(100.100.100.100) (UDP)
;; WHEN: Mon Nov 14 22:30:25 CET 2022
;; MSG SIZE  rcvd: 55

the /etc/resolv.conf seems correct, with its search domain.

# resolv.conf(5) file generated by tailscale
# DO NOT EDIT THIS FILE BY HAND -- CHANGES WILL BE OVERWRITTEN

nameserver 100.100.100.100
search private.ts.net

I restarted the headless server, and reconnected my client. Same as before. No error logs on the server.

How to proceed?

Originally created by @doebi on GitHub (Nov 14, 2022). **Bug description** MagicDNS is not working and I don't know what is going on or how to approach this issue. It occured to me after a reboot of my notebook, and trying to log in to my server: ``` > $ ssh server1 ssh: Could not resolve hostname server1: Temporary failure in name resolution ``` while `tailscale status` reports... ``` 100.64.0.1 <this machine> private linux - 100.64.0.2 server1 private linux active; offers exit node; direct X.X.X.X:1234, tx 1332 rx 1452 100.64.0.4 raspi private linux offline 100.64.0.3 server2 private linux active; offers exit node; direct X.X.X.X:1234, tx 276 rx 156 ``` ...the public and even the tailscale IP are pingable... ``` > $ ping 100.64.0.2 PING 100.64.0.2 (100.64.0.2) 56(84) bytes of data. 64 bytes from 100.64.0.2: icmp_seq=1 ttl=64 time=2.58 ms 64 bytes from 100.64.0.2: icmp_seq=2 ttl=64 time=2.77 ms 64 bytes from 100.64.0.2: icmp_seq=3 ttl=64 time=2.94 ms 64 bytes from 100.64.0.2: icmp_seq=4 ttl=64 time=2.72 ms ``` ...but dig returns an empty response: ``` > $ dig server1 ; <<>> DiG 9.18.1-1ubuntu1.2-Ubuntu <<>> server1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4207 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4095 ;; QUESTION SECTION: ;server1. IN A ;; Query time: 4 msec ;; SERVER: 100.100.100.100#53(100.100.100.100) (UDP) ;; WHEN: Mon Nov 14 22:18:33 CET 2022 ;; MSG SIZE rcvd: 35 ``` other DNS requests work just fine: ``` > $ dig google.com ; <<>> DiG 9.18.1-1ubuntu1.2-Ubuntu <<>> google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 957 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4095 ;; QUESTION SECTION: ;google.com. IN A ;; ANSWER SECTION: google.com. 291 IN A 142.251.36.110 ;; Query time: 8 msec ;; SERVER: 100.100.100.100#53(100.100.100.100) (UDP) ;; WHEN: Mon Nov 14 22:30:25 CET 2022 ;; MSG SIZE rcvd: 55 ``` the `/etc/resolv.conf` seems correct, with its search domain. ``` # resolv.conf(5) file generated by tailscale # DO NOT EDIT THIS FILE BY HAND -- CHANGES WILL BE OVERWRITTEN nameserver 100.100.100.100 search private.ts.net ``` I restarted the headless server, and reconnected my client. Same as before. No error logs on the server. How to proceed?
adam added the bug label 2025-12-29 01:27:51 +01:00
adam closed this issue 2025-12-29 01:27:51 +01:00
adam commented 2025-12-29 01:27:52 +01:00
Author
Owner
Copy Link

@ChibangLW commented on GitHub (May 3, 2023):

I think something with setting the default search domain is not correct inside headscale, as I have the same problem. You should be able to resolve server1.<user>.<base_domain>.

@ChibangLW commented on GitHub (May 3, 2023): I think something with setting the default search domain is not correct inside headscale, as I have the same problem. You should be able to resolve `server1.<user>.<base_domain>`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#372
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?