The domain github.com is resolving to github.com.mydomain

Support
,
1

What type of hardware are you using: Virtual machine
What YunoHost version are you running: 12.1.39
How are you able to access your server: SSH

Describe your issue

I’m encountering this bug specifically with Nextcloud, but the issue stems from a DNS configuration problem. Indeed, github .com is resolving to github.com.mydomain, which then resolves to ::1 (IPv6 localhost). This blocks Nextcloud during app updates because Nextcloud does not accept local resolutions.
One potential solution would be to remove the line “search mydomain” from /etc/resolv.conf. However, I don’t think this is a good idea, as it might break other things.
I’m not sure what I should do to fix this issue while maintaining a correct YunoHost configuration.

Share relevant logs or error messages

getent hosts github.com
::1             mydomain.fr github.com.mydomain.fr
2a01:cb19:80c4:8a00:bc07:baff:****:**** mydomain.fr github.com.mydomain.fr

ping github.com
PING github.com (140.82.121.3) 56(84) bytes of data.
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=1 ttl=53 time=31.8 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=2 ttl=53 time=26.1 ms

file: /etc/hosts

127.0.0.1   localhost
127.0.1.1   pc-1566.home    pc-1566

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

127.0.0.1   mydomain

File: /etc/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "resolvectl status" to see details about the actual nameservers.

nameserver 127.0.0.1
search mydomain
2

Do you have a public ipv4 address?

3

Yes. I have a public IPv4
I also have AdGuard deployed with a DNS redirection from *.mydomain to 192.xxxx

4

for information,

nslookup github.com
Server:		127.0.0.1
Address:	127.0.0.1#53

Non-authoritative answer:
Name:	github.com
Address: 140.82.121.4


dig github.com         

; <<>> DiG 9.18.44-1~deb12u1-Debian <<>> github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27200
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
github.com.		6	IN	A	140.82.121.4

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Sun Mar 08 13:41:55 CET 2026
;; MSG SIZE  rcvd: 55

So, dig and nslookup seems nice… however, i get the following message in Nextcloud log, when i try to update application. which is consistent with the output of getent

[no app in context] Erreur: Host "::1" (github.com:80) violates local access rules
	GET /nextcloud/settings/apps/update/calendar
	de 2a01:cb19:80c4:8a00:7d8e:cd3c:xxx.xxx par m*** à 8 mars 2026, 13:41:52
5

Can you share your /etc/dnsmasq.conf ?

6

File: /etc/dnsmasq.conf

domain-needed
expand-hosts
localise-queries



interface=lo

resolv-file=/etc/resolv.dnsmasq.conf
cache-size=256
7

hello,
Do you have any idea how to solve the problem?

8

Ultimately, I think it’s a DNS issue, most likely due to Adguard.

9

That’s a very important detail, if you’re using Adguard check its config, especially the “DNS rewrites” section