Why am I having wrong IPs in my DNS?How can I find the answering DNS server?Why is DNS failover not recommended?DNS SERVFAIL and Incorrect Flag only via TCP: Broken DNS Servers?How to diagnose DNS problems after switching to Route 53DNS Server replication created duplicate A-Recordsdns a records become staticProperly configuring DNS for email sending on multi-domain hosting VPSTroubleshooting a Web Server with Timeouts?Root DNS servers report wrong NS
Weakening g4 move
Which cooking device allows flexible temperature programming?
Had Ravan tried would he have been able to lift Angad's feet?
How to compare the signature of two functions?
Is a job offer letter with no mention of salary structure legal or correct?
What is the point of teaching Coding and robotics to kids as young as 6 years old?
Stack Exchange Answerer
Could a chess engine do retro analysis?
Dropping "to be" and other verbs in Latin?
Can I apply for a passport in the country I'm in so I can travel to my home country?
Is it acceptable to say that a divergent series that tends to infinity is 'equal to' infinity?
How do you say "to play Devil's advocate" in German?
A good reference to the Gauss result on the structure of the multiplicative group of a residue ring
Why does the monotone convergence theorem not apply on Riemann integrals?
Three Tongues of Rock
TikZ: How to draw a pattern at the border of a not closed tikz path
Does a Thief rogue's Fast Hands allow you to drink a potion as a bonus action?
Feasible explanation to the continued existence of dangerous magical creatures in a modern setting
How can baseline humanity survive on its own in the future?
Is there a conflict between YAGNI and SRP?
In the UK, who owns the intellectual property of a thesis?
Signed overflow in C++ and UB
Should high school teachers say “real numbers” before teaching complex numbers?
A fantasy novel that takes place on a ship. There is a spy on the ship and at some point amphibious monsters catch him
Why am I having wrong IPs in my DNS?
How can I find the answering DNS server?Why is DNS failover not recommended?DNS SERVFAIL and Incorrect Flag only via TCP: Broken DNS Servers?How to diagnose DNS problems after switching to Route 53DNS Server replication created duplicate A-Recordsdns a records become staticProperly configuring DNS for email sending on multi-domain hosting VPSTroubleshooting a Web Server with Timeouts?Root DNS servers report wrong NS
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom: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
Some dig results are here
domain-name-system
add a comment
|
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
Some dig results are here
domain-name-system
add a comment
|
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
Some dig results are here
domain-name-system
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
Some dig results are here
domain-name-system
domain-name-system
edited Nov 11 at 1:33
womble♦
88.4k18 gold badges156 silver badges212 bronze badges
88.4k18 gold badges156 silver badges212 bronze badges
asked Oct 16 at 3:44
PixelPaulPixelPaul
3432 silver badges11 bronze badges
3432 silver badges11 bronze badges
add a comment
|
add a comment
|
2 Answers
2
active
oldest
votes
The authoritative answers for the ns1-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)
Can you add sample commands that would let someone verify these results?
– mgarciaisaia
Oct 17 at 3:55
1
@mgarciaisaia:dnstracer -s . <domain>
can be used to quickly see the delegations. For the actual comparison, you would rundig <domain> NS @<server>
against both sets of servers – once against the domain owner's ns# servers themselves, and then once against the parent TLD's nameservers which hold the "glue" records (e.g. for com.au they aret.au
,r.au
,q.au
, etc).
– grawity
Oct 17 at 5:56
add a comment
|
You have 6 name servers. 2 of them have the wrong zone information. Thus most of the time the answers are correct, but occasionally you hit a bad DNS server.
I'm not at my PC at the moment but you can check what each server is returning with a command like
dig @nsX.maccentrecloud.com.au elyseecollective.com.au A
For each nameserver and find the faulty ones. Then get the DNS provider to fix them or remove them from your registrars name server records for the domain.
7
The issue with this test is that it will look up the name nsX.maccentrecloud.com.au itself, ie the authoritative answer, and then send the specified query there. This doesn't play nice with looking for glue record mismatch, which seems to have been the problem in this case.
– Håkan Lindqvist
Oct 16 at 16:27
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f988169%2fwhy-am-i-having-wrong-ips-in-my-dns%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The authoritative answers for the ns1-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)
Can you add sample commands that would let someone verify these results?
– mgarciaisaia
Oct 17 at 3:55
1
@mgarciaisaia:dnstracer -s . <domain>
can be used to quickly see the delegations. For the actual comparison, you would rundig <domain> NS @<server>
against both sets of servers – once against the domain owner's ns# servers themselves, and then once against the parent TLD's nameservers which hold the "glue" records (e.g. for com.au they aret.au
,r.au
,q.au
, etc).
– grawity
Oct 17 at 5:56
add a comment
|
The authoritative answers for the ns1-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)
Can you add sample commands that would let someone verify these results?
– mgarciaisaia
Oct 17 at 3:55
1
@mgarciaisaia:dnstracer -s . <domain>
can be used to quickly see the delegations. For the actual comparison, you would rundig <domain> NS @<server>
against both sets of servers – once against the domain owner's ns# servers themselves, and then once against the parent TLD's nameservers which hold the "glue" records (e.g. for com.au they aret.au
,r.au
,q.au
, etc).
– grawity
Oct 17 at 5:56
add a comment
|
The authoritative answers for the ns1-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)
The authoritative answers for the ns1-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)
answered Oct 16 at 5:44
Håkan LindqvistHåkan Lindqvist
23.9k4 gold badges40 silver badges65 bronze badges
23.9k4 gold badges40 silver badges65 bronze badges
Can you add sample commands that would let someone verify these results?
– mgarciaisaia
Oct 17 at 3:55
1
@mgarciaisaia:dnstracer -s . <domain>
can be used to quickly see the delegations. For the actual comparison, you would rundig <domain> NS @<server>
against both sets of servers – once against the domain owner's ns# servers themselves, and then once against the parent TLD's nameservers which hold the "glue" records (e.g. for com.au they aret.au
,r.au
,q.au
, etc).
– grawity
Oct 17 at 5:56
add a comment
|
Can you add sample commands that would let someone verify these results?
– mgarciaisaia
Oct 17 at 3:55
1
@mgarciaisaia:dnstracer -s . <domain>
can be used to quickly see the delegations. For the actual comparison, you would rundig <domain> NS @<server>
against both sets of servers – once against the domain owner's ns# servers themselves, and then once against the parent TLD's nameservers which hold the "glue" records (e.g. for com.au they aret.au
,r.au
,q.au
, etc).
– grawity
Oct 17 at 5:56
Can you add sample commands that would let someone verify these results?
– mgarciaisaia
Oct 17 at 3:55
Can you add sample commands that would let someone verify these results?
– mgarciaisaia
Oct 17 at 3:55
1
1
@mgarciaisaia:
dnstracer -s . <domain>
can be used to quickly see the delegations. For the actual comparison, you would run dig <domain> NS @<server>
against both sets of servers – once against the domain owner's ns# servers themselves, and then once against the parent TLD's nameservers which hold the "glue" records (e.g. for com.au they are t.au
, r.au
, q.au
, etc).– grawity
Oct 17 at 5:56
@mgarciaisaia:
dnstracer -s . <domain>
can be used to quickly see the delegations. For the actual comparison, you would run dig <domain> NS @<server>
against both sets of servers – once against the domain owner's ns# servers themselves, and then once against the parent TLD's nameservers which hold the "glue" records (e.g. for com.au they are t.au
, r.au
, q.au
, etc).– grawity
Oct 17 at 5:56
add a comment
|
You have 6 name servers. 2 of them have the wrong zone information. Thus most of the time the answers are correct, but occasionally you hit a bad DNS server.
I'm not at my PC at the moment but you can check what each server is returning with a command like
dig @nsX.maccentrecloud.com.au elyseecollective.com.au A
For each nameserver and find the faulty ones. Then get the DNS provider to fix them or remove them from your registrars name server records for the domain.
7
The issue with this test is that it will look up the name nsX.maccentrecloud.com.au itself, ie the authoritative answer, and then send the specified query there. This doesn't play nice with looking for glue record mismatch, which seems to have been the problem in this case.
– Håkan Lindqvist
Oct 16 at 16:27
add a comment
|
You have 6 name servers. 2 of them have the wrong zone information. Thus most of the time the answers are correct, but occasionally you hit a bad DNS server.
I'm not at my PC at the moment but you can check what each server is returning with a command like
dig @nsX.maccentrecloud.com.au elyseecollective.com.au A
For each nameserver and find the faulty ones. Then get the DNS provider to fix them or remove them from your registrars name server records for the domain.
7
The issue with this test is that it will look up the name nsX.maccentrecloud.com.au itself, ie the authoritative answer, and then send the specified query there. This doesn't play nice with looking for glue record mismatch, which seems to have been the problem in this case.
– Håkan Lindqvist
Oct 16 at 16:27
add a comment
|
You have 6 name servers. 2 of them have the wrong zone information. Thus most of the time the answers are correct, but occasionally you hit a bad DNS server.
I'm not at my PC at the moment but you can check what each server is returning with a command like
dig @nsX.maccentrecloud.com.au elyseecollective.com.au A
For each nameserver and find the faulty ones. Then get the DNS provider to fix them or remove them from your registrars name server records for the domain.
You have 6 name servers. 2 of them have the wrong zone information. Thus most of the time the answers are correct, but occasionally you hit a bad DNS server.
I'm not at my PC at the moment but you can check what each server is returning with a command like
dig @nsX.maccentrecloud.com.au elyseecollective.com.au A
For each nameserver and find the faulty ones. Then get the DNS provider to fix them or remove them from your registrars name server records for the domain.
answered Oct 16 at 5:06
davidgodavidgo
4,0951 gold badge15 silver badges31 bronze badges
4,0951 gold badge15 silver badges31 bronze badges
7
The issue with this test is that it will look up the name nsX.maccentrecloud.com.au itself, ie the authoritative answer, and then send the specified query there. This doesn't play nice with looking for glue record mismatch, which seems to have been the problem in this case.
– Håkan Lindqvist
Oct 16 at 16:27
add a comment
|
7
The issue with this test is that it will look up the name nsX.maccentrecloud.com.au itself, ie the authoritative answer, and then send the specified query there. This doesn't play nice with looking for glue record mismatch, which seems to have been the problem in this case.
– Håkan Lindqvist
Oct 16 at 16:27
7
7
The issue with this test is that it will look up the name nsX.maccentrecloud.com.au itself, ie the authoritative answer, and then send the specified query there. This doesn't play nice with looking for glue record mismatch, which seems to have been the problem in this case.
– Håkan Lindqvist
Oct 16 at 16:27
The issue with this test is that it will look up the name nsX.maccentrecloud.com.au itself, ie the authoritative answer, and then send the specified query there. This doesn't play nice with looking for glue record mismatch, which seems to have been the problem in this case.
– Håkan Lindqvist
Oct 16 at 16:27
add a comment
|
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f988169%2fwhy-am-i-having-wrong-ips-in-my-dns%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown