[KLUG Members] Can't ping IPCop!

[Justin Buist]

Nslookup -didn't- resolve 'ipcop', and neither did 'ping' probably because
it's actually looking for ipcop.mydomain.org.  The reverse-lookup of 192.168.1.1
returns 'ipcop.' and not 'ipcop.mydomain.org'.

You could either remove the default domain from your DHCP settings, or make
/etc/hosts fully qualified by using a line like:
192.168.1.1	ipcop	ipcop.mydomain.org

At least, that's my hunch.

Justin Buist

On Wed, Jan 15, 2003 at 08:33:40PM -0500, Mike Morrett wrote:
> C:\TEMP>ping ipcop
> Unknown host ipcop.
[snip]
> C:\TEMP>nslookup
> Default Server:  ipcop
> Address:  192.168.1.1
> 
> > ipcop
> Server:  ipcop
> Address:  192.168.1.1
> 
> *** No address (A) records available for ipcop
> > exit
> 
> Why does the name of the IPCop firewall box not get entered into its own
> DNS? Is there a way round this?
> 
> IPCop is using DNSMASQ and according to
> http://thekelleys.org.uk/dnsmasq/doc.html ...
> 
> "Dnsmasq will serve names from the /etc/hosts file on the firewall
> machine: If the names of local machines are there, then they can all be
> addressed without having to maintain /etc/hosts on each machine."
> 
> Well, "192.168.1.1 ipcop" is in the /etc/hosts file.
[snip]
> 
>         Connection-specific DNS Suffix  . : mydomain.org