Same here haaretz.co.il won’t resolve with 22.214.171.124 but will resolve with 126.96.36.199
Same here, can’t resolve any of the domains listed by @MohammadAG.
Weird, I can resolve all of them, so maybe it only happen from some POPs (due to rate limiting?).
For people who can’t resolve this, can you resolve
resolver.dnscrypt.info to check what Cloudflare servers are used?
Accoording to the list, it looks like we have issue to reach those ns servers in our Tel Aviv PoP
We are looking into this.
Additionally, it seems like WiFi calling for Partner does not work, I’m not sure how to get the domain name that doesn’t resolve for that though.
This shows up in the iPhone’s logs, which confirms the issue is related to DNS at least:
CommCenter: #N DATA.dns: operator(): Failed to resolve name with error (12:8).
Edit: Actually seems like partner.co.il does not resolve at all, adding to the list.
Edit 2: Found the domain, epdg.epc.mnc001.mcc425.pub.3gppnetwork.org
Our local provider applied some changes. Please kindly retry.
I think it looks good now, thanks!
Everything seems to be fine now, thanks!
I see its working now… still need to be tasted with IL domains
Update: Still not resolving sxhssatyanagar.in !
According to the post, I’d like to add to the test some more Israeli websites which found as not working with 188.8.131.52, but with Google DNS (184.108.40.206) it works flawless.
Hi @dahan.amit1, we are checking regarding those two domains
Would appreciate if you can keep us posted for these 2 domains.
This is a problem with the DNS settings for the zone. The zone owner has specified DNSSEC but the the DNSSEC settings for the zone are invalid. The 220.127.116.11 servers check to verify this is valid and it is failing so we aren’t returning results.
If you happen to know the zone owner, you might let them know they have a problem with their zone settings.
segment.com not resolving:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> segment.com @18.104.22.168
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53043
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;segment.com. IN A
;; Query time: 148 msec
;; SERVER: 22.214.171.124#53(126.96.36.199)
;; WHEN: Fri Apr 06 15:32:04 PDT 2018
;; MSG SIZE rcvd: 88
$ dig segment.com @188.8.131.52 +short
Using the Google DNS Settings no issues.
Only with CludFlare DNS it happens that way
Talked to the ISP and no issues with them, so it seems only something from your direction.
Derp! I should have tried the dig with the 184.108.40.206 NS… you’re absolutely correct!
Turns out, I was being blocked by my pi-hole service…