Darvlinig
n00b
Joined: 14 Apr 2023
Posts: 1
|
 Posted: Fri Apr 14, 2023 5:50 pm Post subject: DNS resolution failed on emerge. Android chrooted Prefix |
 |
|
Hello, guys, I have a problem.
When I emerge package on Android chrooted prefix, wget fails to resolve hostname. Also I must mention that I built the prefix and chrooted into it. Of course I mounted /sys /dev /proc directories to prefix
Here is emerge log:
| Code: |
root@localhost / # emerge -av neofetch
* IMPORTANT: 14 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 5.38 s.
[ebuild N ] app-misc/neofetch-7.1.0-r1::gentoo 94 KiB
Total: 1 package (1 new), Size of downloads: 94 KiB
Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) app-misc/neofetch-7.1.0-r1::gentoo
openpty failed: 'out of pty devices'
Unable to unshare: EINVAL (for FEATURES="ipc-sandbox network-sandbox pid-sandbox")
>>> Downloading 'http://distfiles.gentoo.org/distfiles/layout.conf'
--2023-04-14 17:07:02-- http://distfiles.gentoo.org/distfiles/layout.conf
Resolving distfiles.gentoo.org... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘distfiles.gentoo.org’
!!! Couldn't download '.layout.conf.distfiles.gentoo.org'. Aborting.
>>> Downloading 'http://distfiles.gentoo.org/distfiles/neofetch-7.1.0.tar.gz'
--2023-04-14 17:07:02-- http://distfiles.gentoo.org/distfiles/neofetch-7.1.0.tar.gz
Resolving distfiles.gentoo.org... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘distfiles.gentoo.org’
>>> Downloading 'https://github.com/dylanaraps/neofetch/archive/7.1.0/neofetch-7.1.0.tar.gz'
--2023-04-14 17:07:02-- https://github.com/dylanaraps/neofetch/archive/7.1.0/neofetch-7.1.0.tar.gz
Resolving github.com... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘github.com’
!!! Couldn't download 'neofetch-7.1.0.tar.gz'. Aborting.
* Fetch failed for 'app-misc/neofetch-7.1.0-r1', Log file:
* '/var/tmp/portage/app-misc/neofetch-7.1.0-r1/temp/build.log'
>>> Failed to emerge app-misc/neofetch-7.1.0-r1, Log file:
>>> '/var/tmp/portage/app-misc/neofetch-7.1.0-r1/temp/build.log'
* Messages for package app-misc/neofetch-7.1.0-r1:
* Fetch failed for 'app-misc/neofetch-7.1.0-r1', Log file:
* '/var/tmp/portage/app-misc/neofetch-7.1.0-r1/temp/build.log'
root@localhost / #
|
I must tell that resolv.conf configured correctly and outside of portage DNS resolution works just fine.
Here is logs for ping:
| Code: |
root@localhost / # 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=55 time=44.2 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=2 ttl=55 time=60.3 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=3 ttl=55 time=59.2 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=4 ttl=55 time=53.8 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=5 ttl=55 time=53.0 ms
^C
--- github.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4012ms
rtt min/avg/max/mdev = 44.241/54.117/60.313/5.714 ms
root@localhost / #
|
Before this post, I searched this forum, and somebody pointed to incorrect resolv.conf permissions
Here is resolv.conf permissions:
| Code: |
root@localhost / # ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 38 Apr 14 15:34 /etc/resolv.conf
root@localhost / #
|
Here is resolv.conf contains:
| Code: |
root@localhost / # cat /etc/resolv.conf
nameserver 8.8.4.4
nameserver 8.8.8.8
root@localhost / #
|
Here is list of network interfaces:
| Code: |
root@localhost / # ifconfig
dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500
inet6 fe80::cc4f:29ff:fe4e:fba1 prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 0 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11 bytes 770 (770.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 0 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p2p0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rmnet_ipa0: flags=65<UP,RUNNING> mtu 2000
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.11 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 2a03:f680:fe04:120d:da68:c3ff:fe49:70a5 prefixlen 64 scopeid 0x0<global>
inet6 fe80::da68:c3ff:fe49:70a5 prefixlen 64 scopeid 0x20<link>
inet6 2a03:f680:fe04:120d:fc94:7bf4:3f49:72b5 prefixlen 64 scopeid 0x0<global>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 160100 bytes 224375684 (213.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 70485 bytes 8874492 (8.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@localhost /
|
Why is portage cannot resolve domains despite other programs like ping can? |
|
Networking & Security
