My Centos Server DNS resolves to 127.0.0.1 and not the real IP

compumec

5/14/23, 4:50 PM

Im using CWP on CentOS 7, it was working just fine but some time from now, my DNS Server resolves all my domains to 127.0.0.1. So I could open up a page that were hosted on my vps on my clients ether phone or pc and it directly tried to open up localhost.

Then I used dnschecker.org DnsChecker showing error to see what was going on and on some geographic locations were pointing correctly to the IP from my VPS and to others to the localhost (127.0.0.1).

I think it might be some kinda malware installed on my server because this is not normal.

0 + 0

dns-server

Alexis Wilke

5/14/23, 5:29 PM

To debug a DNS, you use `dig @server-name-or-ip <domain-name>`. Have you tried that? What is the output? (please copy paste in your question)

Score:0

Server

compumec

5/15/23, 10:52 PM

I registered a free domain for testing purposes and this is the result I get from dig command:

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.8 <<>> @vps.compu-mecanic.com compu-test.tk ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44567 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3 ;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;compu-test.tk. IN A

;; ANSWER SECTION: compu-test.tk. 14400 IN A 104.225.217.18

;; AUTHORITY SECTION: compu-test.tk. 86400 IN NS ns4.compu-mecanic.com. compu-test.tk. 86400 IN NS ns3.compu-mecanic.com.

;; ADDITIONAL SECTION: ns3.compu-mecanic.com. 14400 IN A 104.225.217.18 ns4.compu-mecanic.com. 14400 IN A 185.136.96.99

;; Query time: 0 msec ;; SERVER: 104.225.217.18#53(104.225.217.18) ;; WHEN: Sat Jan 15 15:47:10 MST 2022 ;; MSG SIZE rcvd: 143

And this is what I get from pinging this domain from my computer Pinging compu-test.tk [127.0.0.1] with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

0 + 0

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: My Centos Server DNS resolves to 127.0.0.1 and not the real IP

TH: DNS เซิร์ฟเวอร์ Centos ของฉันแก้ไขเป็น 127.0.0.1 ไม่ใช่ IP จริง

RO: DNS-ul meu Centos Server se rezolvă la 127.0.0.1 și nu IP-ul real

RU: DNS моего сервера Centos разрешается в 127.0.0.1, а не в настоящий IP

VI: DNS máy chủ Centos của tôi phân giải thành 127.0.0.1 chứ không phải IP thực

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.