问题原文
原帖链接 · PixelPaul · CC BY-SA 4.0
I have a certain domain I manage, which was moved to DNSmadeeasy a week ago. But sometimes when I do a dig request I get a weird IP back on the A record: 166.62.3.1
Others are reporting the same, from different locations. It seems to be random though, as most report the correct IP.
DNSmadeeasy say nothing is wrong in their end as usual, so I have no idea how this IP is getting out there.
The domain is: elyseecollective.com.au
已采纳解答
原帖链接 · Håkan Lindqvist · CC BY-SA 4.0
The authoritative answers for the ns{1-6}.maccentrecloud.com.au names point to:
ns1.maccentrecloud.com.au. 1800 IN A 208.94.148.4
ns2.maccentrecloud.com.au. 1800 IN A 208.80.124.4
ns3.maccentrecloud.com.au. 1800 IN A 208.80.126.4
ns4.maccentrecloud.com.au. 1800 IN A 208.80.125.4
ns5.maccentrecloud.com.au. 1800 IN A 208.80.127.4
ns6.maccentrecloud.com.au. 1800 IN A 208.94.149.4
But the glue records don't quite match:
ns1.maccentrecloud.com.au. 900 IN A 208.94.148.4
ns2.maccentrecloud.com.au. 900 IN A 112.140.180.10
ns3.maccentrecloud.com.au. 900 IN A 208.80.126.4
ns4.maccentrecloud.com.au. 900 IN A 208.80.125.4
ns5.maccentrecloud.com.au. 900 IN A 208.80.127.4
ns6.maccentrecloud.com.au. 900 IN A 208.94.149.4
Update the glue (through the registrar for maccentrecloud.com.au).
(ns2.maccentrecloud.com.au. / 112.140.180.10 responds differently, and the bad glue puts it into the mix of who should be queried)
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
