|
||||||||
Hi All I can now confirm that the DNS issue I was having was related to having a wildcard DNS entry with my DNS provider. Removing this entry has resolved my issue. I hope this will help someone else if they ever come across this. Mark Mark Wass wrote: > Hi Tim > > You're absolutely right! I do recall seeing a wild card entry in our > DNS settings with our DNS provider for that particular domain. This > was left over from years ago and we don't make use of that any more. > I'll try removing it and see if it fixes it. > > Thanks :-) > > > > Tim Kingman wrote: > >> The domain you're entering in General Setup is being passed to DHCP >> clients as a search domain. Normally, this means that DNS lookups will >> try to append those domains to all lookups. For example, on my >> computer at work, I have sub.ourdomain.edu and domain.edu set as >> search domains, so I only have to ssh hostname, and it works even >> though I'm really getting to hostname.sub.domain.edu. >> >> I'm going to guess that the difference in your case is that your real >> domain's DNS provider is doing wildcard dns, so >> anything.your-real-domain.com will resolve to your-real-domain.com's >> IP address. Even though mycorp.com is a real domain name, it does not >> have wildcard DNS, so google.com.mycorp.com doesn't resolve, so the >> Windows DNS resolver tries again without the search domain appended. >> >> The next logical question is: can m0n0wall be set to not pass the >> entered domain to DHCP clients as a search domain? Or, can you just >> enter a completely bogus domain name and not inadvertently break some >> other component? I assume you can, because my General Setup is >> configured with a hostname of m0n0wall and a domain of just my >> apartment number. I guess it's possible that this causes my computers >> to query RoadRunner's DNS servers for google.com.123 every time, but I >> haven't seen any problems. >> >> -tim >> >> >> On 11/9/05, Mark Wass <mark dot wass at market dash analyst dot com> wrote: >> >> >>> Ok Guys I have figured out what the problem was. >>> >>> In my General Setup in m0n0wall I used our real domain name. This is a >>> real domain that we own and resolves to a real IP. >>> >>> As soon as I used mycorp.com (the suggested example) as the domain name >>> in General Settings all was ok. >>> >>> One thing to note is that our domain contains a hyphen "-" in it, I >>> wonder if that was the problem. >>> >>> So my question now is, Why can't I use my real domain but I can use >>> mycorp.com? >>> >>> Mark >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch >> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > > |