Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
779 questions
my Azure VM (Linux) is resolving a DNS entry (ile-cdn.pikimoni.net) as 127.0.0.1
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 36%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Alessandro
0
Reputation points
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?
Azure DNS
Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
9,068 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 81%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Sai Prasanna Sinde 6,650 Reputation points Microsoft External Staff Moderator2025-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 localhostthis is my /etc/resolve,conf file:
nameserver 168.63.129.16 search xtkvqjakivfulpph2t055lo2oa.ax.internal.cloudapp.netI 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 Reputation points
2025-02-04T20:59:11.8633333+00:00 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: 103but 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: 115Any idea? I also tried to flush the cache with sudo systemd-resolve --flush-caches
-
Sai Prasanna Sinde 6,650 Reputation points Microsoft External Staff Moderator
2025-02-05T01:02:58.9966667+00:00 Hi @Alessandro
- Please go to the Azure portal, navigate to your DNS Private Zones. Find the zone that should contain records for pikimoni.net.
- Ensure that both the CNAME record for ile-cdn.pikimoni.net and the A record for cl-ms0b922158.edgecdn.ru are present and correct. The A record must point to 95.181.182.182.
- Double-check your VNet's DNS settings in the Azure portal. Verify that the forwarding rules are correctly set up. If you're forwarding to an on-premises DNS server, ensure that server has the correct DNS records for your CDN.
- Check your CDN's documentation or support resources. Look for any settings related to DNS or custom origins. Make sure your CDN is properly configured to serve requests for cl-ms0b922158.edgecdn.ru.
- Unfortunately, you don't have direct control over Azure's DNS cache. Sometimes, waiting a while (usually a short period) can resolve this.
- You could also try creating a test CNAME record in your DNS zone (e.g., test-ile-cdn.pikimoni.net pointing to the same CDN endpoint) and see if that resolves correctly. This could sometimes force a refresh of the Azure DNS cache.
- Use nslookup +trace ile-cdn.pikimoni.net to get a more detailed view of the DNS resolution process. This will show you which DNS servers are being queried and where the resolution fails
- And also, dig +trace ile-cdn.pikimoni.net will provide similar tracing information.
- If you have Azure Network Watcher configured, use its "DNS resolution" feature to diagnose the issue from within the Azure network. For your reference: https://learn.microsoft.com/en-us/azure/network-watcher/connection-troubleshoot-overview
Kindly let us know if the above helps or you need further assistance on this issue.
Thanks,
Sai.
-
Sai Prasanna Sinde 6,650 Reputation points Microsoft External Staff Moderator
2025-02-06T01:02:12.1+00:00 Hi @Anonymous
Just checking in to see if you have got a chance to see my response to your question in resolving the issue.
If you are still facing any further issues, please let us know in the comments below so that we can address them.
-
Sai Prasanna Sinde 6,650 Reputation points Microsoft External Staff Moderator
2025-02-06T23:02:36.67+00:00 Hi @Alessandro
Just checking in to see if you have got a chance to see my response to your question in resolving the issue.If you are still facing any further issues, please let us know in the comments below so that we can address them.
Sign in to comment
Sign in to answer