bing.com

[adguard-bot]

Issue URL (Incorrect Blocking)

http://bing.com

Comment

Using Adguard DNS default server with default ruleset makes the DNS resolution oscillating. A sniff with Wireshark outlined that bing.com gets resolved to CNAME records which end up being resolved in another CNAME records infinitely until timeout hits in. No resolution to A or AAA records possible.
Username: @sarumaj

Screenshots

Screenshot 1

Screenshot 1 with AdGuard disabled

System configuration

Information	Value
AdGuard product:	AdGuard DNS
DNS setup:	Device or router settings
DNS server:	AdGuard DNS Default server
System version:	Fritzbox 6660
Browser:	Edge

[BlazDT]

Informed Devs. No filter issue though as it also happens with non-filtering DNS. No issue on Google DNS with local DNS filtering with AdGuard DNS blocking on Android.

[ameshkov]

Is the issue still happening? I cannot reproduce it, but maybe it's specific to some location?

What do you see if you open https://dns.adguard.com/info.txt?

[BlazDT]

Issue still happening.

dns2-dp-fra-5
dns2-dp-fra-9
dns2-dp-fra-12
dns2-dp-fra-13
dns2-dp-fra-14
dns2-dp-fra-15

Working with:
dns2-dp-fra-7
dns2-dp-fra-10
dns2-dp-fra-17

[BlazDT]

Looks like something got fixed, server 9 working now.

Now previously working server dns2-dp-fra-7 not working.

[ameshkov]

Weird, I have no idea what happened tbh:( Let's close it for now and reopen if it happens again.

[BlazDT]

You misunderstood me. It is still broken:

dns2-dp-fra-10

[ameshkov]

Can't reproduce it now:

dnslookup v1.9.1
dnslookup result (elapsed 319.836µs):
;; opcode: QUERY, status: NOERROR, id: 19989
;; flags: qr rd ra; QUERY: 1, ANSWER: 12, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.bing.com.	IN	 A

;; ANSWER SECTION:
www.bing.com.	10720	IN	CNAME	www-www.bing.com.trafficmanager.net.
www-www.bing.com.trafficmanager.net.	18	IN	CNAME	www.bing.com.edgekey.net.
www.bing.com.edgekey.net.	21558	IN	CNAME	e86303.dscx.akamaiedge.net.
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.129
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.171
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.186
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.178
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.123
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.177
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.185
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.163
e86303.dscx.akamaiedge.net.	60	IN	A	104.126.37.170

[BlazDT]

On -10 it works now, but on dns2-dp-fra-3 not.

All set via DNS settings in AdGuard Android Nightly.

[BlazDT]

@sarumaj
I can only reproduce on mobile data, not on Wi-Fi. Can you still reproduce? If yes, mobile or wifi?
So far only broken for me with Vodafone mobile data.

[sarumaj]

@BlazDT, Vodafone seems to have resolved the issue. It was an ISP-related issue. I vote to close it.

[BlazDT]

Glad it works again. Strange other sites could be resolved though.

[adguard-bot]

Issue URL (Incorrect Blocking)

http://bing.com

Screenshots

Screenshot 1

Screenshot 1 with AdGuard disabled

System configuration

Information	Value
AdGuard product:	AdGuard DNS
DNS setup:	Device or router settings
DNS server:	AdGuard DNS Default server
System version:	Fritzbox 7390, Android 12, Windows 10/11
Browser:	Edge

[adguard-bot]

Issue URL (Incorrect Blocking)

http://bing.com

Screenshots

Screenshot 1

Screenshot 1 with AdGuard disabled

System configuration

Information	Value
AdGuard product:	AdGuard DNS
DNS setup:	Device or router settings
DNS server:	AdGuard DNS Default server
System version:	Windows 11, version 23H2 および Android 14
Browser:	Edge

[Alex-302]

#176865 (comment)

not reproduced.

[Alex-302]

Maybe incorrect setup? Please try to use this server directly in Windows, and compare result.