arch iso fails to boot due to wrong dns (0.0.0.0)

[berinaniesh]

Using netboot.xyz.efi with manual network configuration and dns 8.8.8.8, it downloads the initrd and kernel (I guess) and boots, then proceeds to download the root file system, but download fails due to wrong dns. It sets the dns to 0.0.0.0 itself.

[berinaniesh]

Ubuntu ISO works fine, please don't mind if the issue is with archlinux's ISO.

[oe3gwu]

I cant relate tho that. As you see in the 2nd picture, my DNS is correct (192.168.1.10). I am running Netboot on a Docker (no Host Network). As DNS I user a Pi Hole with a DHCP Helper.

Boot works fine for me of all components. I didnt test Arch further, because I really hate it.

[cicku]

The workaround is to echo "nameserver 1.1.1.1" > /etc/resolv.conf

Appears to be a busybox bug with static IP.

[berinaniesh]

The workaround is to echo "nameserver 1.1.1.1" > /etc/resolv.conf

Appears to be a busybox bug with static IP.

It just drops me to the emergency shell, can it be done with emergency shell?

[berinaniesh]

Tried it yesterday, with manual ip address (non dhcp) and it failed. Used netboot.xyz.efi hit m to failsafe mode, entered network ip, gateway and dns manually, initramfs downloads fine, when the rootfs downloads, it fails and drops to emergency shell.

[bartenbach]

Same issue. DNS doesn't resolve a hostname and I end up in an emergency shell.

Ironically it downloads the kernel and initramfs img just fine from the same host and then seconds later claims it can't resolve that hostname.

[bartenbach]

The workaround is to echo "nameserver 1.1.1.1" > /etc/resolv.conf Appears to be a busybox bug with static IP.

It just drops me to the emergency shell, can it be done with emergency shell?

Agree. I can set the DNS server and grab the file but then what?

[bartenbach]

Tried to just log out after adding DNS server to resolv.conf as the text suggests, but no luck there. Found a file in /tmp that clearly doesn't have the DNS servers that you can verify are present in the netboot network settings menu initially.

After this, it appears to continually try and execute the next line of some script and turns into an error message generator.

[ryester19]

The workaround is to echo "nameserver 1.1.1.1" > /etc/resolv.conf

Appears to be a busybox bug with static IP.

Is there a related bugreport on the Busybox's Bigzilla page that we can monitor?

[antonym]

I can adjust the kernel command line to put DNS entries if there's a place in the loader that can pull them out, I haven't managed to find it yet tho. I tried a few iterations of ip= but that didn't seem to work.

[bartenbach]

I can adjust the kernel command line to put DNS entries if there's a place in the loader that can pull them out, I haven't managed to find it yet tho. I tried a few iterations of ip= but that didn't seem to work.

I was looking at this too but found no solution.

I'm back at this same problem over a year later. The devs might as well just remove Arch from the list and admit that it doesn't work. It's essentially just marketing at this point. They just have a big list of items that probably don't work to make the app sound more useful/important than it actually is.

If you can avoid netboot, you can install Arch just fine.

[berinaniesh]

Only manual network configuration is a problem. Automatic configuration works just fine @bartenbach. BTW, the problem still persists. Tried a week before.

[antonym]

I'm open to suggestions for fixing manual config, automatic works just fine however as I installed Arch with it this week.