Weird Issue with Ubuntu DNS
-
So with my Ubuntu servers, I pull the IPs via DHCP and set reservations for all my servers. I've found it's easier than trying to set everything static. Anyways, there is a weird issue I've found with how Ubuntu handles DNS server order in /etc/resolv.conf.
I had my DHCP scope set to hand out my local as primary, OpenDNS primary as the secondary option and Google DNS primary as the tertiary. Well, Ubuntu doesn't maintain that order but will order them numerically, which means it puts Google (8.8.8.8) at the top, then my local (172.16.255.10) and then OpenDNS (208.67.222.222). I removed Google DNS from the scope options for DNS and that will hopefully fix it, but it screws up local name resolution.
Has anyone else seen this before?
-
Why are you handing out public DNS? Just have your local 172.16.255.10 setup to forward to this in the order you want.
-
Wow.. that's pretty terrible.
That said, in a windows environment you don't want to provide external DNS ever to an end client because you'll break all kinds of locally needed DNS entries (like your current problem).
As Creative says, why have the external ones there at all? If DNS is down, that's a pretty big deal you should be working to resolve.
-
@Dashrender said:
That said, in a windows environment you don't want to provide external DNS ever to an end client because you'll break all kinds of locally needed DNS entries (like your current problem).
As Creative says, why have the external ones there at all? If DNS is down, that's a pretty big deal you should be working to resolve.Really, in any enviroment, you do not want external DNS handed out to the internal network. The internal DNS device should handle all forwarding for anything it does not now.
-
It was just kind of an emergency failover kind of thing. If my internal server went down, my machines could still get online. It's mostly my family so if my internal DNS server has an issue, they won't notice an issue as it'll still resolve with external servers.
-
@JaredBusch said:
@Dashrender said:
That said, in a windows environment you don't want to provide external DNS ever to an end client because you'll break all kinds of locally needed DNS entries (like your current problem).
As Creative says, why have the external ones there at all? If DNS is down, that's a pretty big deal you should be working to resolve.Really, in any enviroment, you do not want external DNS handed out to the internal network. The internal DNS device should handle all forwarding for anything it does not now.
I find that "lots" of really small environments (mostly those under a dozen users) and home users typically use all public and have no internal DNS at all. I agree, don't hand out public if you have internal, but I think having no internal is often fine too.
-
I completely agree.. if you don't have DNS internal, use external.
