On Thu 30 Sep 2021 at 14:46:50 (-0400), Greg Wooledge wrote: > On Thu, Sep 30, 2021 at 01:30:20PM -0500, David Wright wrote: > > 192.168.1.1 looks like the d-i ran a DHCP client to get an address > > for your PC, and that the DHCP server that responded was probably > > your router, address 192.168.1.1, and so the d-i figured that your > > router would be able to resolve DNS. > > The DHCP server actually sends nameserver addresses to the DHCP client. > In the case of a home router, the nameserver address will typically > be the router's internal IP address, which is often 192.168.1.1. > > It's *not* d-i deciding to try using the router as a nameserver on a whim.
Yes, badly expressed personification, I'm afraid. … Though it does appear that the syslog also expresses this less than clearly: netcfg[5552]: WARNING **: Started DHCP client; PID is 5581 udhcpc: Got IP 192.168.1.14 (using enp3s0) and routing through 192.168.1.1 netcfg[5552]: DEBUG: Reading domain name returned via DHCP → netcfg[5552]: DEBUG: Reading nameservers from /etc/resolv.conf netcfg[5552]: DEBUG: Read nameserver 192.168.1.1 Might one assume that the nameservers are written into /etc/resolv.conf by the DHCP client at →, so that they can immediately be read again in order to attempt (and fail) to ascertain the hostname from the nameserver. Cheers, David.
