Closed Bug 1654870 Opened 4 years ago Closed 4 years ago

"Server not found" for a specific page on mobile (but not desktop)

Categories

(Core :: Networking: DNS, defect)

Unspecified
All
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: miketaylr, Unassigned)

References

()

Details

Originally reported @ https://github.com/webcompat/web-bugs/issues/55690

STR:

  1. In Fenix (or Fennec...) try to load http://punjab.indiaresults.com/pseb/default.htm

Expected: it works
Actual: "Address Not Found"

This page loads without issue in Desktop, and AFAICT we're served the same page from the server.

I get "address not found" on desktop nightly

Performing a lookup for punjab.indiaresults.com in about:networking also results in unknown host.

I get the following resolver logs:

2020-07-23 18:48:01.760970 UTC - [Parent 1212365: Main Thread]: D/nsHostResolver Resolving host [punjab.indiaresults.com]<> type 0. [this=0x7fc2d378c040]
2020-07-23 18:48:01.760994 UTC - [Parent 1212365: Main Thread]: D/nsHostResolver   No usable record in cache for host [punjab.indiaresults.com] type 0.
2020-07-23 18:48:01.760999 UTC - [Parent 1212365: Main Thread]: D/nsHostResolver NameLookup host:punjab.indiaresults.com af:0
2020-07-23 18:48:01.761005 UTC - [Parent 1212365: Main Thread]: D/nsHostResolver NameLookup: punjab.indiaresults.com effectiveTRRmode: 1 flags: 0
2020-07-23 18:48:01.761016 UTC - [Parent 1212365: Main Thread]: D/nsHostResolver   DNS thread counters: total=3 any-live=0 idle=3 pending=1
2020-07-23 18:48:01.761040 UTC - [Parent 1212365: Main Thread]: D/nsHostResolver   DNS lookup for host [punjab.indiaresults.com] blocking pending 'getaddrinfo' or trr query: callback [0x7fc26e5d6280]
2020-07-23 18:48:01.761093 UTC - [Parent 1212365: DNS Resolver #57]: E/nsHostResolver DNS lookup thread - Calling getaddrinfo for host [punjab.indiaresults.com].
2020-07-23 18:48:01.779656 UTC - [Parent 1212365: DNS Resolver #57]: D/nsHostResolver Calling 'res_ninit'.
2020-07-23 18:48:01.781170 UTC - [Parent 1212365: DNS Resolver #57]: E/nsHostResolver DNS lookup thread - lookup completed for host [punjab.indiaresults.com]: failure: unknown host.
2020-07-23 18:48:01.781180 UTC - [Parent 1212365: DNS Resolver #57]: D/nsHostResolver nsHostResolver::CompleteLookup punjab.indiaresults.com (nil) 804B001E trr=0 stillResolving=0
2020-07-23 18:48:01.781185 UTC - [Parent 1212365: DNS Resolver #57]: D/nsHostResolver nsHostResolver record 0x7fc270da4480 new gencnt
2020-07-23 18:48:01.781195 UTC - [Parent 1212365: DNS Resolver #57]: D/nsHostResolver Caching host [punjab.indiaresults.com] negative record for 60 seconds.
2020-07-23 18:48:01.781199 UTC - [Parent 1212365: DNS Resolver #57]: D/nsHostResolver CompleteLookup: punjab.indiaresults.com has NO address
2020-07-23 18:48:01.781204 UTC - [Parent 1212365: DNS Resolver #57]: D/nsHostResolver nsHostResolver record 0x7fc270da4480 calling back dns users
Component: General → Networking: DNS
Product: GeckoView → Core

(In reply to James Willcox (:snorp) (jwillcox@mozilla.com) (he/him) from comment #1)

I get "address not found" on desktop nightly

Ah whoops, I guess I only tested in DevEdition. >_>

edit: no, at least on macOS, the lookup succeeds on the latest Nightly for me.

I cannot reproduce it on Fennec. Valentin, can you please have a look at it?

Flags: needinfo?(valentin.gosu)

I can't reproduce on either desktop or mobile.
The result seems to come from the DNS resolver, so I'm assuming the domain is either intentionally or mistakenly blocked.
It could also be caused by something like bug 1184059 that only manifests on mobile, but considering comment 1 I assume that's not the case.

James, can you still reproduce this? Could you let me know about what resolver you're using? https://whatismyresolver.com/
Also can you check if the domain can be resolved in the terminal? dig punjab.indiaresults.com and dig punjab.indiaresults.com @1.1.1.1

Flags: needinfo?(valentin.gosu) → needinfo?(snorp)

I can't reproduce this anymore. It seems to be resolving without issue now. When I was able to repro, dig was returning results just fine. I guess we can close? Pretty strange...

Flags: needinfo?(snorp)

Let's hope it was just an temporary DNS configuration/propagation issue.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.