I had this exact problem on my linux box, but I thought it was because I was inexperienced with Bind9 but once I moved to the RB750G, I am having the same problem.
I have a bunch of local devices that have web interfaces, so I set up a DNS server to resolve them all. “Like https://router, http://mainswitch, etc.” The problem I am having is that it seems to work “sometimes” but more often than not, not at all. However, I can do nslookup and it comes up but just typing the dns name into a web browser doesn’t. Flushing the DNS cashe doesn’t fix it neither.
I thought it might be because I didn’t set up a local domain so I used “home.local” (As in “http://router.home.local”) and properly set up the records (DHCP, changing the A records, etc) to match and it still doesn’t look it up 100% of the time.
What makes it more annoying is I have a samba linux server that always resolves its name for shares but never for the web interface.
I know I am missing some important bit of information but I just don’t see what I am doing wrong. I know I can configure my hosts file for it, but it seems that if I am using a DNS server, I might as well learn something.
If you use a console command, like ssh, telnet and ping, you can use a non-fqdn domain. A web browser requires a fqdn. Try using something like http://login.yourdomain.com
Just curious, but I own a domain but with the exception of one host, it doesn’t have any other domains. If I was to put in “router.warlockd.net” and push down that everyone is on the warlockd.net domain, would that work?
I just want to make sure if this is a “best practices” thing. Basically, if there is an internal IP for a site and an external one, if using a static DNS for internal resolving is the best idea.
yourdomain was supposed to be replaced with your domain. You should use your domain name, and use different server names. I use location abbreviations for the server name, like for yours I would use something like this: hdgs.warlockd.net hdgv.warlockd.net
etc
Heh, I know. I used to use yourdomain or example on some old networks.
Still having a problem with firefox not resolve the short name though (http://test dosn’t resolve but http://test.warlockd.net does even with both static rules in) It does do the long name now so its enough.
Have you set your search scope via the “domain” option in “/ip dhcp-server network”, or manually in the TCP/IP properties of the host? A host with a search domain of ‘warlockd.net’ should try ‘test’ first, fail to find it, and then query for ‘test.warlockd.net’.