From: Harry G. <ha...@hg...> - 2003-06-29 18:00:31
|
At 5:19 PM +0100 6/29/03, st...@wo... wrote: >On 29.06.2003 16:35 Matthew Dale wrote: >>Issue number 1: Local DNS >>Many people seem to have difficulty in getting to ipcop via >>http://ipcop:81 as stated in the manual - I am among these people. >>I'm using DHCP to set clients up - and the dns server is set as IPCop >>as it should be. However, all I get is 404s trying to access like >>that, and ping can't ping it either - leaving me with >>http://192.168.0.1:81 as the only surefire way to access it. >>I have recieved a couple of workaround, one of which in particular >>poses questions about how the lookup is handled. >>The first workaround is to set the DNS Suffix to mydomain.home (or >>something similar) and add a line "192.168.0.1 ipcop.mydomain.home" to >>/etc/hosts on the IPCop box. This works fine - it pings, and the >>browser can see it. > >I would have thought that you should be doing this anyway. I always have Both Windows and Mac OS X have a different way they do DNS lookups from the Unix/Linux systems of the world, if they see a name with no periods. Unix/Linux will try any name with or without periods before they append the DNS suffix to it while Windows and Mac OS X immediately append the suffix. In other words, a Unix box will first send a query for "ipcop" and then for "ipcop.mydomain.home", while Windows and Mac will never send the query for ipcop. Adding a period makes everyone happy. BTW, if you make a typo and try to browse "www.ipcop.orgg", everyone will first try "www.ipcop.orgg" and then "www.ipcop.orgg.mydowmain.home". >> >>Issue number 2: Global DNS Suffixes >>As I said above in the first workaround, DNS suffixs work fine for me >>locally. >>However, global ones don't. Here is a test case I just ran. >>I set the DNS suffix to "bbc.co.uk". I renewed my DHCP lease and >>checked that the new settings had come through. I then flushed the DNS >>cache on the box I was using to test the suffix to remove any chance >>of it using a precached result. >>With this setup, requesting "www" should get me http://www.bbc.co.uk, >>and requesting "news" should get me http://news.bbc.co.uk, and so on. >>Not so. any request that relies on the suffix results in a 404. >>However, an inspection of the local DNS cache after the request >>reveals an entry like: >>news > >Are you running a web proxy, if so it might not work, since you >would look for news and so might the proxy. >If domain name was not defaulted on the proxy then the it would look for news. >Just an idea. > >Why not net the domain and be done with it? > ><me thinks out aloud> >Maybe people who 'know' about networking are setting the domain >without thinking about it, whereas those we problems are not. ></me thinks out aloud> This sounds like you're not getting the DNS domain set properly on the machine doing the browsing and are you sure you didn't type "news."? Harry |