1.1.1.1 cannot resolve ovh.net domains and its subdomains

Hello,

Using Cloudflare 1.1.1.1 it cannot resolve ovh . net and its subdomains (for example ex2 . mail . ovh . net).

Note : it’s ovh . net without space, but Cloudflare forums doesn’t allow URLs.

Comparisons of nslookup with Cloudflare and Google DNS :

$ nslookup ovh . net 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53

** server can't find ovh . net: REFUSED
$ nslookup ovh . net 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: ovh . net
Address: 54.39.46.56

Comparisons of dig with Cloudflare and Google DNS :
(we can see the “status: REFUSED”)

$ dig A ovh . net @1.1.1.1 +dnssec
$ dig A ovh . net @1.1.1.1 +nodnssec

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 57210
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;ovh . net. IN A

;; Query time: 5 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Nov 25 11:12:28 CET 2022
;; MSG SIZE rcvd: 36
$ dig A ovh . net @8.8.8.8 +dnssec
$ dig A ovh . net @8.8.8.8 +nodnssec

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17685
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ovh . net. IN A

;; ANSWER SECTION:
ovh . net. 32 IN A 54.39.46.56

;; Query time: 9 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Nov 25 11:12:42 CET 2022
;; MSG SIZE rcvd: 52

I already tried the Purge cache : https://1.1.1.1/purge-cache/ on ovh.net domain, but it doesn’t seems to change anything.

Thanks!

1 Like

I can also reproduce this

Could you share a link from from https://1.1.1.1/help please and also send the output from the following command:

dig ovh.net @1.1.1.1 +nsid

I cannot reproduce this (getting 54.39.46.56 with above command), are you perhaps querying 1.1.1.1 for Families?

Can’t reproduce anymore:

[email protected]:~$ dig ovh.net @1.1.1.1 +nsid

; <<>> DiG 9.16.33-Debian <<>> ovh.net @1.1.1.1 +nsid
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15247
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; NSID: 38 34 6d 32 31 ("84m21")
;; QUESTION SECTION:
;ovh.net.                       IN      A

;; ANSWER SECTION:
ovh.net.                9       IN      A       54.39.46.56

;; Query time: 0 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Nov 25 20:04:04 AWST 2022
;; MSG SIZE  rcvd: 61

https://1.1.1.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjEuMS4xIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjAuMC4xIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTExMSI6Ik5vIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTAwMSI6Ik5vIiwiZGF0YWNlbnRlckxvY2F0aW9uIjoiUEVSIiwiaXNXYXJwIjoiTm8iLCJpc3BOYW1lIjoiQ2xvdWRmbGFyZSIsImlzcEFzbiI6IjEzMzM1In0=

Thanks for your reply!

Here is the output of dig nsid with Cloudflare and Google DNS :

$ dig ovh.net @1.1.1.1 +nsid

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 20530
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; NSID: 35 33 33 6d 31 32 ("533m12")
;; QUESTION SECTION:
;ovh.net.			IN	A

;; Query time: 6 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Nov 25 14:08:12 CET 2022
;; MSG SIZE  rcvd: 46
$ dig ovh.net @8.8.8.8 +nsid

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6512
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
; NSID: 67 70 64 6e 73 2d 70 61 72 ("gpdns-par")
;; QUESTION SECTION:
;ovh.net.			IN	A

;; ANSWER SECTION:
ovh.net.		7	IN	A	54.39.46.56

;; Query time: 9 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Nov 25 14:08:20 CET 2022
;; MSG SIZE  rcvd: 65
1 Like

Thanks for the information here - we’ve looked at this internally and have applied some potential mitigations - you should see this working now.

Thanks for reporting this - we’re talking to OVH directly, also.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.