Windows Server trying to register with public DNS?
-
Apparently at some point my Domain Controller decided the DNS server it should register to is the public DNS and not its local server like it's been doing for the past five years. I haven't changed anything except who the domain is on the public side (from bluehost to afraid.org), which shouldn't have mattered because the domain server isn't supposed to be concerned whatsoever about it anyways.
This, despite my configuration still being as expected (the "secondary" server is its LAN address just-in-fucking-case):
Why the fuck it it trying to talk to the top domain? It should be talking to itself FFS!
I don't know where this is being configured and nobody else seems to have this kind of issue...
-
@Tsaukpaetra I've read somewhere that it is supposed to get the DNS server from the config screen you are showing.
However, are you sure there's only one active network interface? Have you tried running
ipconfig /allto see if there is a network interface using the DNS server you see in the Event Log?
-
@JBert said in Windows Server trying to register with public DNS?:
@Tsaukpaetra I've read somewhere that it is supposed to get the DNS server from the config screen you are showing.
However, are you sure there's only one active network interface? Have you tried running
ipconfig /allto see if there is a network interface using the DNS server you see in the Event Log?Yes, there's only one actual interface other than the software tunnel devices.
Wanna see something else that's apparently fucked? Asking to lookup anything results in bullshit like this:
-
What's on 192.168.1.199? And what does that use as a DNS server?
I assume it's picked the alternate because it's after an answer it thinks it can't answer itself.
-
@loopback0 said in Windows Server trying to register with public DNS?:
What's on 192.168.1.199? And what does that use as a DNS server?
I assume it's picked the alternate because it's after an answer it thinks it can't answer itself.
199 is itself. It used to be 203 which is the secondary Domain Controller, but that has also fallen over because it can't talk to 199 because it has fallen over.
-
@Tsaukpaetra Is it just forwarding it to the default gateway?
-
@loopback0 said in Windows Server trying to register with public DNS?:
@Tsaukpaetra Is it just forwarding it to the default gateway?
I can't fucking tell because the DNS service won't let me into it.
I believe it was supposed to forward to Google's DNS for anything not in its own domain.
-
@Tsaukpaetra I suspect it's doing forwarding to your ISP and the rest of the shenanigans are the ISP messing with the results once it hits there, rather than the results actually coming from 1.1.1.1
-
@loopback0 said in Windows Server trying to register with public DNS?:
@Tsaukpaetra I suspect it's doing forwarding to your ISP and the rest of the shenanigans are the ISP messing with the results once it hits there, rather than the results actually coming from 1.1.1.1
The problem here is that I literally can't configure DNS because it's "not actually started but it says it is".
Like, dafuq? (I get the same message if I try localhost too).
-
@Tsaukpaetra Have you tried rebooting it? Sounds like it can't get much worse, especially if there's a secondary DC
-
@loopback0 said in Windows Server trying to register with public DNS?:
@Tsaukpaetra Have you tried rebooting it? Sounds like it can't get much worse, especially if there's a secondary DC
Yes. Also, the secondary DC is similarly fucked, because it can't talk to any DNS to verify it's in the domain because see above.
-
thenYour DNS is not where you left it
-
@loopback0 said in Windows Server trying to register with public DNS?:
thenYour DNS is not where you left it
Yeah, and looking up for how to fix this chicken'd egg is nearly impossible because it just magically sometimes fixes itself...
-
I suppose my biggest problem is figuring out how the NETLOGON service determines what the DNS server it's supposed to be fucking around with is. It's certainly not asking the computer what it should be from the network interface options...
-
Whelp, let's toss it over to SO and see what people close it for...
NETLOGON trying to register with incorrect DNS server?
So, I have a Domain Controller DOMAINSERVER, and a second domain controller DS1. They are part of the domain office.mydomainname.com, and all was well in the world; DNS server was working great, Cl...
-
@Tsaukpaetra I gave you a vote up over there.
