It happens that name resolving fails at first try for example:
~# ping google.com
ping: bad address 'google.com'
~# ping google.com
PING google.com (142.251.209.46): 56 data bytes
64 bytes from 142.251.209.46: seq=0 ttl=116 time=9.819 ms
no matter the site. Also wget, curl or opkg update commands fail at first try.
nslookup behaviour slightly different, first time:
nslookup google.com
Server: 127.0.0.1
Address: 127.0.0.1:53
One of your configured DNS servers is active, but not able to resolve google.com so it returns NXDOMAIN. NXDOMAIN is a valid result, so the system does not fail over to another server.
Please run the following commands (copy-paste the whole block) and paste the output here, using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have
ubus call system board; \
uci export network; \
uci export dhcp; \
ls -l /etc/resolv.* /tmp/resolv.* /tmp/resolv.*/* ; head -n -0 /etc/resolv.* /tmp/resolv.* /tmp/resolv.*/*
You can try to query the nameserver directly. nslookup openwrt.org 192.168.3.1
It will have the same problem.
Better add some specific nameservers to be used instead of this one:
That's what I did to solve the problem. But can't figure out why this happens. openwrt19 works fine. while with openwrt23:
first try after reboot or new name to be resolved differs from next times
yes, it my home router fault d-link DVA-5592_A1_WI_20191219 or internet provider dns, but no other device complains about this. all in all the address is resolved
I could suggest you to run a tcpdump, but I don't think we'll see anything interesting there.
I believe you have limited to no access at all on the dlink, hence not much you can troubleshoot. Solutions I can think:
Change the DNS and enjoy your weekend.
Collect packet captures from working and not working examples, be prepared to open tickets with your ISP.