0

Why can't I use @dns1.nextdns.io in dig? (@IP-address does work)

> dig +short HOSTNAME @dns1.nextdns.io
;; connection timed out; no servers could be reached

> dig +short HOSTNAME @45.90.28.35
IP-ADDRESS

Why does the IP address work, but can't I use @dns1.nextdns.io in dig?

(I'm trying to execute dig on an ASUS router running Asuswrt-merlin where the nextdns-cli is running and 45.90.28.35 is the WAN IP address)

Is there any other hostname I can use instead? Or should I really use an IP address?

4 replies

null
    • olivier
    • 4 yrs agoWed, February 3, 2021 at 10:06 AM UTC
    • Reported - view

    What is the result if dig dns1.nextdns.io

      • iOS Developer
      • Rob
      • 4 yrs agoWed, February 3, 2021 at 10:52 AM UTC
      • Reported - view

      Olivier Poitrey  

      ;; ANSWER SECTION:
dns1.nextdns.io.    11    IN    CNAME    dns1.steering.nextdns.io.
dns1.steering.nextdns.io. 60    IN    A    188.172.219.167
      • olivier
      • 4 yrs agoWed, February 3, 2021 at 10:59 AM UTC
      • Reported - view

      Rob you can use anycast.dns1.nextdns.io

      • iOS Developer
      • Rob
      • 4 yrs agoWed, February 3, 2021 at 12:10 PM UTC
      • Reported - view

      Olivier Poitrey Yes, that works. Thanks!

      In the mean time I discovered the domain I'm testing is registered at Hover, so maybe it's better to use their name server ns1.hover.com instead?

Login to reply

Content aside

  • 4 yrs agoWed, February 3, 2021 at 12:10 PM UTCLast active
  • 4Replies
  • 186Views
  • 2 Following