QUOTE(Oltromen Ripot @ Nov 28 2023, 12:45 PM)
you have IPv6 enabled on WAN's side?
what if custom-DNSv6 in client device (i.e. skip resolving AAAA using router)?
does it eliminate the time length?
Yes, IPv6 enabled, it is showing IPv6 on my post, right?
And nope, it is not IPv6 related, it happen on both DNS relay server, which is IPv4 192.168.1.1 and IPv6 fe80::65e::Removed(Sry, that's my router Mac address lol).
Yes, overwrite by setting 8.8.8.8 8.8.4.4 on my Windows 10's NIC/network card's IPv4 and the same IPv6 DNS for IPv6, problem solved.
Sadly NETIS don't allow me to setup IPv6 DNS at DHCP/SLAAC, only IPv4 DHCP allowed...
Based on my recall it is quite buggy, so I also avoid it...
----
Anyways.
The problem is DNS Relay not respond to AAAA result, only, for, PBE, lol!!!!
I tested a lot like "dig aaaa www.baidu.com" or "dig aaaa www.qq.com" or "dig aaaa www.weibo.com", even those IPv4 only test website like
https://ipv4.jamieweb.net/, all return with result.
CODE
dig aaaa v4.ipv6test.app
; <<>> DiG 9.16.37 <<>> aaaa v4.ipv6test.app
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63006
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;v4.ipv6test.app. IN AAAA
;; AUTHORITY SECTION:
ipv6test.app. 890 IN SOA ns-1656.awsdns-15.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
;; Query time: 15 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Nov 28 12:24:01 Malay Peninsula Standard Time 2023
;; MSG SIZE rcvd: 131
For PBE, it is
CODE
dig aaaa www.pbebank.com
; <<>> DiG 9.16.37 <<>> aaaa www.pbebank.com
;; global options: +cmd
;; connection timed out; no servers could be reached
But it should be
CODE
dig aaaa www.pbebank.com @8.8.8.8
; <<>> DiG 9.16.37 <<>> aaaa www.pbebank.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 42027
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.pbebank.com. IN AAAA
;; Query time: 17 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 28 13:04:57 Malay Peninsula Standard Time 2023
;; MSG SIZE rcvd: 44
For extra, I also tested on my Android phone using Net Analyzer, the result is "Status: ERROR".
If I set it to 8.8.8.8, the result is "Status: SERVFAIL"
----
Ok, I double checked the result, there is 1 thing, special only for PBE.
1. PBE don't return their CNAME, and it is status: SERVFAIL in app.
2. For v4.ipv6test.app It is "Status: NOERROR" in app, with DIG you can see it got "AUTHORITY SECTION".
So I think the bug is either 2
1. If "status: SERVFAIL" in result(as shown in DIG)
or
2. If there is empty AUTHORITY SECTION from DNS server
The DNS RELAY on this NETIS router will drop the result...
So it is unlucky that, PBE setup wrongly on their AAAA for, at least 4 years?
QUOTE(kwss @ Nov 28 2023, 01:06 PM)
I am happy for you. The problem is still on your side.
Don't scream routing problem when it's actually your own hardware problem. None of your own advice works in this case. Your very own DNS problem doesn't means Public Bank get the blame either, or Cloudflare DNS, or Google DNS.
Does TM share the responsibility? Maybe, since they supply the hardware.
Use more logic instead of emotion next time.
About my long dig story, I don't do butt dyno. Measure it or it's just "feeling".
If I don't come and challenge you, you will still be blaming routing problem or other people's DNS problem instead of you.
Oh, you did learn my DNS diagnostic technique right? The Timing tool in Firefox. LMAO.
Anyway, proud of you. Fast learner.
lol, still fxxk u.
I never blaming routing problem, or other people's DNS problem, you still adding other's fault on my head, adding TM fault on my head.
Yet, I blame on PBE, and I am still correct.
Seem like the problem is PBE failed to configure AAAA correctly, it is status: SERVFAIL for it.
So the router's DNS relay saw it is "status: SERVFAIL", and dropped it.
Did DNS relay did it wrong/out of spec?
I don't know
Did browser did it wrong for keep waiting AAAA result?
I don't know, they got Happy Eyeballs, but, it only applied to server, not DNS AAAA result.
https://en.wikipedia.org/wiki/Happy_EyeballsShould they perform changing?
Except DNS relay should not drop result, only PBE need to fix their AAAA record, even it only host for IPv4.