![]() Formerly used for IPv6 to IPv4 relay (included IPv6 address block 2002::/16). Īssigned as TEST-NET-1, documentation and examples. IETF Protocol Assignments, DS-Lite (/29). Used for link-local addresses between two hosts on a single link when no IP address is otherwise specified, such as would have normally been retrieved from a DHCP server. Used for loopback addresses to the local host. Shared address space for communications between a service provider and its subscribers when using a carrier-grade NAT. Used for local communications within a private network. IPv4 designates special usage or applications for various addresses or address blocks: Special address blocks Read the nf(5) manual page for that.This section is transcluded from IPv4#Special-use addresses. The systemd-resolved configuration files are a whole bunch of files in various directories that get combined, and how to configure them for the second choice aforementioned is beyond the scope of this answer. Make your own /etc/nf file, an actual regular file instead of a symbolic link, list 1.1.1.1 there and remember to turn off nss-resolve so that you go back to using nss-dns and the BIND DNS Client.Configure systemd-resolved via its own configuration mechanisms to use that instead of what it is seeing in the DHCP leases.systemd-resolved will learn of that via the DHCP leases and use it. Configure your DHCP server to hand that out instead of handing out 192.168.1.1.If you want to use a third-party resolving proxy DNS server at 1.1.1.1, or some other IP address, you have three choices: as the Desktop Bus is reached via an AF_LOCAL socket. It's not even IP traffic, let alone IP traffic over a loopback network interface. To intercept that you have to monitor the Desktop Bus traffic with dbus-monitor or some such tool. Instead, nss-resolve speaks a non-standard and idiosyncratic protocol over the (system-wide) Desktop Bus to systemd-resolved, which again makes back end queries of 192.168.1.1 or whatever your DHCP leases and configuration files say. Nss-resolve gets listed ahead of nss-dns in your /etc/nf file, causing your C libraries to not use the BIND DNS Client, or the DNS protocol, to perform name→address lookups at all. Previously, your C libraries would have used another plug-in named nss-dns which uses the BIND DNS Client to make queries using the DNS protocol to the server(s) listed in /etc/nf, applying the domain suffixes listed therein. There's an NSS module provided with systemd-resolved, named nss-resolve, that is a plug-in for your C libraries. ![]() Ironically, although it could be that you haven't captured loopback interface traffic to/from 127.0.0.53 properly, it is more likely that you aren't seeing it because systemd-resolved also (optionally) bypasses the BIND DNS Client in your C libraries and generates no such traffic to be captured. Your DNS client libraries, in your applications programs, are themselves only talking to systemd-resolved. In which case, the thing that knows about the 192.168.1.1 setting, that is (presumably) handed out in DHCP leases by the DHCP server on your LAN, is systemd-resolved, which is forwarding query traffic to it as you have observed. It's likely that you have such a symbolic link.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |