1/1/2023 0 Comments Surgemail disable reverse dns![]() This may not be suitable in your case, but can be overridden. The default domain for hosts is '.local'. I have it working on the IPv6 side, but it is not publishing IPv4 addresses. You could also look at installing the avahi utilities which will enable automatic discovery on link-local networks. It should be fast, so it may work if you put it ahead of dns in the hosts entry. dnsmasq will automatically register names if they are provided in DHCP requests it handles.ĮDIT2: If none of your computers are always up, you may want to look at installing samba and using wins in your nsswitch configuration. You will need a /etc/hosts file, unless you can disable the DHCP server on your router, you can use dnsmasq for DHCP. Exim should use the resolver for is base lookups. Setting up dnsmasq and using it as your primary DNS nameserver in /etc/nf should resolve the issue if you have any programs which rely only on DNS for name lookups. ![]() If this returns but takes a few seconds, you may want to change the order of the hosts entry in /etc/nf move files to the front of the list. The host and dig commands only check DNS. This should return lookups from your /etc/hosts file as well as DNS. You can tune the timeouts and retries in /etc/nf to speed up the failures.ĮDIT: To test the resolver response try using time getent hosts 192.168.1.50. If you are redirected to a DNS server which isn't running DNS will take quite a while to fail. You may want to use the host or dig command to see which lookups are slow. It also acts as a DNS caching server to reduce load on your upstream DNS servers. However, I generally run dnsmasq which will read the hosts file and serve those entries for forward and reverse lookups. Unfortunately, the router's firmware doesn't include a DNS server.įailing DNS lookups should fail fast. It looks more and more like I'll have to find piecewise program options or parameters for each one trying to do reverse DNS lookups! None of the machines (virtual or not) can act as a DNS server on my LAN since they are not always up. Without dev-pc in /etc/hosts file: $ time getent hosts 192.168.1.50 With dev-pc in /etc/hosts file: $ time getent hosts 192.168.1.50 My /etc/nf (was automatically created during installation) nameserver 192.168.1.1īoth host and dig return very fast for a public ip but take 10s to timeout for a LAN ip. connection timed out no servers could be reached flags: qr rd ra QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0ġ2.119.34.64.in-addr.arpa. >HEADER<<- opcode: QUERY, status: NOERROR, id: 15537 Using host (dig gives the same results): # ip of I searched the net a lot for this and maybe I don't have the right search terms, but I can't find the solution. ![]() Do I really need to setup a DNS server somewhere on my LAN? That seems like a huge and useless effort for my needs and I can't believe there isn't another option in a DHCP environment like mine. However, I can't help but think that I'm missing something. Obviously, using /etc/hosts only goes so far because it is at odds with DHCP. Some of these have workarounds like adding my dev pc's Ip to /etc/hosts or adding a command-specific option to avoid doing DNS reverse lookups. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |