But there's plenty out the box or online solutions out there that little or no technical knowledge... Any sort of hosting at home is done either because you know what you're doing and prefer to do it that way, or as a learning experience.
DNS hairpinning/accessing external IP inside NAT
- Thread starter Ol!ver
- Start date
But there's plenty out the box or online solutions out there that little or no technical knowledge... Any sort of hosting at home is done either because you know what you're doing and prefer to do it that way, or as a learning experience.
Permabanned
- Joined
- 9 Aug 2008
- Posts
- 35,711
yep.
Quick question whilst we are at it:
I'm reading about DHCP failover here: http://technet.microsoft.com/en-us/library/hh831385.aspx#config_dhcp2
My question: in that example, none neither of the two servers have the preferred DNS set as anything outside the network, and the primary node is set as the DNS conroller but pointing to itself.
Question: I've currently got my DNS server looking at Google's DNS servers. If I removed that, where would it be getting its info from?
Not convinced that makes much sense, but we'll see!
Cheers.
I'm reading about DHCP failover here: http://technet.microsoft.com/en-us/library/hh831385.aspx#config_dhcp2
My question: in that example, none neither of the two servers have the preferred DNS set as anything outside the network, and the primary node is set as the DNS conroller but pointing to itself.
Question: I've currently got my DNS server looking at Google's DNS servers. If I removed that, where would it be getting its info from?
Not convinced that makes much sense, but we'll see!
Cheers.
Associate
- Joined
- 13 Oct 2009
- Posts
- 241
- Location
- Cumbria
Their example will be a full blown Windows Domain controlled by Active Directory. You use an internal DNS server because Active Directory automatically adds DNS entries for clients to find a server to authenticate with (i.e. to find the domain controllers).
You'd set forwarders on the DNS controller (aka the server with the DNS role installed). It'll ask for the forwarders for any DNS lookups that it can't answer (e.g. for external websites).
Or, you can leave forwarders blank and it'll ask the root DNS servers.
You'd set forwarders on the DNS controller (aka the server with the DNS role installed). It'll ask for the forwarders for any DNS lookups that it can't answer (e.g. for external websites).
Or, you can leave forwarders blank and it'll ask the root DNS servers.
Associate
- Joined
- 13 Oct 2009
- Posts
- 241
- Location
- Cumbria
It sends the queries to the forwarders and routes the reply back to the PC (you set these by giving the IP) or root servers. i.e. it uses recursion. PC <--> DNS server <--> forwarder <--> root servers
So at some point you do need to give the server an external DNS server to use?
Associate
- Joined
- 13 Oct 2009
- Posts
- 241
- Location
- Cumbria
Yup, that's under the forwarders tab. I tend to pick the ISP DNS server IPs out of the router status page and add them as forwarders.
I think I'd bodged it to be honest. Didn't set it up as a forwarder, but set the server's ethernet connection to use Google's DNS. Was working fine until I just started playing
I think I'd bodged it to be honest. Didn't set it up as a forwarder, but set the server's ethernet connection to use Google's DNS. Was working fine until I just started playing
Client config won't affect how the DNS server looks up external names.
If there's no forwarder, it's using root hints. If its a domain controller, it has to be pointing to itself in the network settings. If its not it doesn't matter too much but wouldn't hurt
This is all on the server, not a client. The server's ethernet port was pointing to Google instead of itself. I assume that meant all DNS requests from clients that the server couldn't resolve were being routed via that else, well, it shouldn't have been working should it?
Either way, doing away with that Google DNS setting killed the connectivity.