Resolution fails for portoalegre-airport.com.br

[igorr]

PS C:\Users\Igor> nslookup portoalegre-airport.com.br 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** one.one.one.one can’t find portoalegre-airport.com.br: Server failed

PS C:\Users\Igor> nslookup portoalegre-airport.com.br 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

*** one.one.one.one can’t find portoalegre-airport.com.br: Server failed

PS C:\Users\Igor> nslookup portoalegre-airport.com.br 8.8.8.8
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: portoalegre-airport.com.br
Address: 45.231.147.38

PS C:\Users\Igor> nslookup -class=chaos -type=txt id.server 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
id.server text =

    "POA"

PS C:\Users\Igor> nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

    "POA"

PS C:\Users\Igor> nslookup -type=txt whoami.Cloudflare.com ns3.Cloudflare.com
Server: ns3.cloudflare.com
Address: 2400:cb00:2049:1::a29f:21

whoami.Cloudflare.com text =

    "2804:14d:4c58:822b:d4:5c89:bfc9:efa8"

[DarkDeviL]

The name servers for portoalegre-airport.com.br seems to have a heavily restrictive firewall that may be intercepting (and blocking) DNS queries.

One likely scenario would be due to regional restrictions (e.g. continent/country/region), perhaps together with a bad (or older) database of information where e.g. IP addresses “belong” to.

Querying Cloudflare (CPH/Copenhagen, Denmark), it has the exact same issue as you see.

From the United Kingdom, I’m also seeing the same failures as you do, also when going over Google and Quad 9. However, over OpenDNS here, it seems to resolve, although it takes a long while (2.2s) to provide the successful lookup.

Although 2.2s may sound like nothing, it is quite a long time for a DNS lookup to succeed.

I would declare this issue to be on the Porto Alegre (and Fortaleza) Airport’s side, as their authoritative DNS servers hasn’t been spread very well out, according to the Internet Standards, e.g. RFC2182 / BCP-16 (Best Current Practice).

While it appears that they have two name servers behind them, as per the minimum, …

• They are both located in Brazil.

• They both have a high latency for the majority of Internet locations, except in e.g. Brazil.

• While it appears (at first sight) that two different networks are running these two name servers on two different networks, both networks are using the exact same upstream providers to provide them with connectivity.

That’s just to mention a couple of things.

Unless the Porto Alegre (and Fortaleza) Airport’s are deciding to raise the quality of their authoritative DNS, I don’t believe you would be able to see any improvement on this.