search

dns

dns troubleshooting with curly

hashtag
dns

 -D | --dns             DNS actions ...
    |                   root: check on root DNS servers
    |                   public: check on public DNS servers e.g 1.1.1.1
    |                   trace: trace from a public DNS server to main server
    | --dc              dns servers to use, default is: 1.1.1.1
    |                   or a file containing some DNS servers ( IPs | names )
circle-info

actions for DNS

  • root

  • public ( or pub)

  • trace

hashtag

hashtag
root

check ANY record from the root DNS server of a domain

root[0]shakiba:/pp# curly --dns root -d derak.cloud

mNS server A.NIC.CLOUD
;derak.cloud.                   IN      ANY
derak.cloud.            3600    IN      NS      4.top.derak.cloud.
derak.cloud.            3600    IN      NS      1.top.derak.cloud.
derak.cloud.            3600    IN      NS      2.top.derak.cloud.
derak.cloud.            3600    IN      NS      3.top.derak.cloud.
4.top.derak.cloud.      3600    IN      A       159.69.229.229
3.top.derak.cloud.      3600    IN      A       178.62.222.218
2.top.derak.cloud.      3600    IN      A       5.145.112.112
1.top.derak.cloud.      3600    IN      A       5.145.115.115

exit 0
root[0]shakiba:/pp#

hashtag
public

simply check the A record(s)

or when we have a custom DNS server and we want to check from there

for example we want to check derak.could on cloud root DNS servers

first we find root DNS servers for cloud TLD

now that we have DNS servers we can query them directly

hashtag
trace

As the name implies , it will trace from a public DNS server down to the authoritative DNS server

instated of 1.1.1.1 we can set another DNS server to start the trace from there

PrevioushttpNextip

Last updated