On Mon, Aug 05, 2024 at 11:25:21PM +0200, Klaus Vink Slott via Dnsmasq-discuss
wrote:
Hi. I am new to dnsmasq and do not really care about IPv6 as our ISP does
not support it. I am trying to replace the build in dhcp/dns in pfSense with
a dnsmasq on a separate machine. Currently there is 3 Linux host on this
vlan, on with dnsmasq.
I have setup everything as I think it should work. But I am confused on how
to configure the IPv6 part. For IPv4 everything seem fine: hosts gets a ip
fixed or dynamic addresses - and testing with the dig command on all hosts
works perfectly:
localadm@dhcpdns:~> dig sshgw.tier1.internal +short
192.168.80.8
localadm@dhcpdns:~> dig -x 192.168.80.8 +short
sshgw.tier1.internal.
But when I try to use any internal address, everything takes ages. A test
with the host command reveals:
localadm@dhcpdns:~> host sshgw.tier1.internal
sshgw.tier1.internal has address 192.168.80.8
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out
;; no servers could be reached
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out
;; no servers could be reached
On 18.08.24 14:29, Geert Stappers wrote:
Mmm, interesting that `dig` and `host` reporting differences.
"host" without "-t" parameter asks for A, AAAA and MX in this order.
In the example above the AAAA and MX queries timeout.
Other clients may ask for AAAA which can result into timeouts.
What might help, is logging of loq queries by dnsmasq.
yeah
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
My mind is like a steel trap - rusty and illegal in 37 states.
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
