my Azure VM (Linux) is resolving a DNS entry (ile-cdn.pikimoni.net) as 127.0.0.1

Alessandro 0

from my azure VM I get this behavior when I run an nslookup command for my domain ile-cdn.pikimoni.net (I own this domain):

> nslookup ile-cdn.pikimoni.net
Server: 168.63.129.16
Address: 168.63.129.16#53
Non-authoritative answer:
ile-cdn.pikimoni.net canonical name = cl-ms0b922158.edgecdn.ru.
Name: cl-ms0b922158.edgecdn.ru
Address: 127.0.0.1
Name: cl-ms0b922158.edgecdn.ru
Address: ::1

ile-cdn.pikimoni.net resolves correctly to cl-ms0b922158.edgecdn.ru, but then cl-ms0b922158.edgecdn.ru is resolved to 127.0.0.1 while it should be something else:

ile-cdn.pikimoni.net.     900   IN  CNAME   cl-ms0b922158.edgecdn.ru.
cl-ms0b922158.edgecdn.ru. 60    IN  A       95.181.182.182

how can I have the DNS entry to resolve correctly?

Sai Prasanna Sinde 3,585 Reputation points Microsoft Vendor

2025-02-04T00:39:58.0733333+00:00
Hi @Alessandro

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

As we understand that you're encountering an issue with your Azure VM, which is resolving the CNAME record for ile-cdn.pikimoni.net correctly, but then it's resolving the A record for cl-ms0b922158.edgecdn.ru to 127.0.0.1 (localhost) and ::1 (IPv6 localhost).

This might be a local configuration issue on your VM, not a problem with your DNS records.

There might be an issue with your host's file. This file is used to override DNS entries. It probably contains a line that map cl-ms0b922158.edgecdn.ru to 127.0.0.1

Or else your VM is configured to use a local DNS server that has a misconfigured entry for cl-ms0b922158.edgecdn.ru

For Linux: Open /etc/hosts in a text editor as root.

Look for any lines that contain cl-ms0b922158.edgecdn.ru. If you find any, comment them out by adding a # at the beginning of the line, or delete them entirely and save the file.

After modifying the hosts file, you need to flush the DNS cache on your VM to ensure the changes take effect.

Linux: sudo systemd-resolve --flush-caches

If the problem persists, check your VM's DNS settings to make sure it's using the correct DNS servers. You can find this in your network settings.

You should be using a reliable public DNS server or your Azure provided DNS.

In some cases, a reboot might be required for the changes to fully take effect.

After making these changes, run nslookup ile-cdn.pikimoni.net again. You should now see the correct IP address for cl-ms0b922158.edgecdn.ru (95.181.182.182).

If you're using Azure DNS, make sure that your DNS records are configured correctly in the Azure portal. For your reference: https://learn.microsoft.com/en-us/azure/dns/dns-troubleshoot

Kindly let us know in the comments below if the above helps or you need further assistance on this issue.

Please Accept an answer if it helps, as original posters help the community find answers faster by identifying the correct answer.

Thanks,

Sai.
Alessandro 0 Reputation points

2025-02-04T06:51:44.88+00:00
Hello Sai,

thank you for your answer: My /etc/hosts file is clean:

# IPv4 and IPv6 localhost aliases 127.0.0.1 localhost ::1 localhost

this is my /etc/resolve,conf file:

nameserver 168.63.129.16 search xtkvqjakivfulpph2t055lo2oa.ax.internal.cloudapp.net

I am using default DNS server:

It seems it's not a local configuration issue. I'm not sure what I should check next.

Thank you for your feedback

Alessandro 0

if I run the dig command forcing the authoritative server (yandex DNS server) it resolves correctly:

dig @77.88.8.8 ile-cdn.pikimoni.net

; <<>> DiG 9.11.3-1ubuntu1.18-Ubuntu <<>> @77.88.8.8 ile-cdn.pikimoni.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52375
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ile-cdn.pikimoni.net.          IN      A

;; ANSWER SECTION:
ile-cdn.pikimoni.net.   789     IN      CNAME   cl-ms0b922158.edgecdn.ru.
cl-ms0b922158.edgecdn.ru. 48    IN      A       95.181.182.182

;; Query time: 956 msec
;; SERVER: 77.88.8.8#53(77.88.8.8)
;; WHEN: Tue Feb 04 20:52:36 UTC 2025
;; MSG SIZE  rcvd: 103

but if I use Azure-provided non-authoritative DNS server it does not work:

dig @168.63.129.16 ile-cdn.pikimoni.net

; <<>> DiG 9.11.2-P1 <<>> @168.63.129.16 ile-cdn.pikimoni.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5843
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1224
; COOKIE: 157d2156ec672385 (echoed)
;; QUESTION SECTION:
;ile-cdn.pikimoni.net.          IN      A

;; ANSWER SECTION:
ile-cdn.pikimoni.net.   900     IN      CNAME   cl-ms0b922158.edgecdn.ru.
cl-ms0b922158.edgecdn.ru. 60    IN      A       127.0.0.1

;; Query time: 90 msec
;; SERVER: 168.63.129.16#53(168.63.129.16)
;; WHEN: Tue Feb 04 20:55:00 UTC 2025
;; MSG SIZE  rcvd: 115

Any idea? I also tried to flush the cache with sudo systemd-resolve --flush-caches

Share via

my Azure VM (Linux) is resolving a DNS entry (ile-cdn.pikimoni.net) as 127.0.0.1

Your answer