Assigning internal DNS with DHCP, can only resolve fqdn

Discussion in 'Networking Issues' started by FlexibleToast, Jul 18, 2013.

  1. FlexibleToast

    FlexibleToast Serious Server Member

    I have a computer that is CentOS 6.4 that is a VM host running a guest that is also CentOS and providing internal DNS. My router is a E4200 with Tomato installed. I've set it up so that the router provides the internal DNS information through DHCP. However, if I use, say my phone, open up terminal and perform an nslookup for "hostname" it returns saying it can't find "hostname". If I nslookup "hostname.domain" it successfully resolves. If I'm on the host CentOS machine that I setup as static and pointed it straight to the internal DNS I can successfully resolve "hostname" without adding the fqdn. Is there a setting that needs to be changed/added to the Tomato router? Under identification I did add the domain name in the appropriate box. I'm guessing because it is not actually providing DNS and instead assigning through DHCP, this is a different option.
  2. sleepermjs

    sleepermjs Serious Server Member

    Try adding the following advanced option to your DNSmasq configuration: expand-hosts
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice