On Saturday 06 June 2009 20:44:38 Tim Judd wrote:
On 6/4/09, Peter fb...@peterk.org wrote:
I do not think /etc/hosts does round robin, I always assumed first match
wins...DNS/bind I would understand...
It's the same library call: gethostbyname(3) and friends.
Why does ping always return
On 6/4/09, Peter fb...@peterk.org wrote:
On Thursday 04 June 2009 20:48:21 Peter wrote:
iH,
This all started with NFS not mounting at bootso, testing in VMs:
snip
Why is ping using one IP, and ssh/mount_nfs/showmount using another IP
from /etc/hosts?
Q: Where is described that name
On Thursday 04 June 2009 20:48:21 Peter wrote:
iH,
This all started with NFS not mounting at bootso, testing in VMs:
snip
Why is ping using one IP, and ssh/mount_nfs/showmount using another IP
from /etc/hosts?
Q: Where is described that name resolution for A or PTR records should be
On Thursday 04 June 2009 20:48:21 Peter wrote:
iH,
This all started with NFS not mounting at bootso, testing in VMs:
snip
Why is ping using one IP, and ssh/mount_nfs/showmount using another IP
from /etc/hosts?
Q: Where is described that name resolution for A or PTR records should
be
David Naylor [EMAIL PROTECTED] writes:
I am trying to redirect a URL request to a different address but it appears
that /etc/hosts is not doing the job. Example:
127.0.0.1 google.com
The way I understand it is that by typing google.com in a web browser it
should result in the local
Hello David:
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
David Naylor
Sent: Thursday, September 11, 2008 1:49 PM
To: freebsd-questions@freebsd.org
David Naylor [EMAIL PROTECTED] wrote:
I am trying to redirect a URL request to a different address but it
appears that /etc/hosts is not doing the job. Example:
127.0.0.1 google.com
The way I understand it is that by typing google.com in a web browser
it should result in the local
`ping google.com' actually pings 127.0.0.1 but `host google' returns
the actual IP addresses for google.
ping will resolve the name using the mecanism defined in
/etc/nsswitch.conf, usually:
hosts: files dns nis
try first /etc/hosts, then DNS, then NIS
But host(1) command is designed
At 08:53 PM 9/1/2008, Tom Marchand wrote:
I am trying to resolve the 192.168.2.3 address.
::1 localhost.local localhost
127.0.0.1 localhost.local localhost
72.15.233.132 host.local host
72.15.233.132 host.local.
192.168.2.3 test
Derek Ragona [EMAIL PROTECTED] wrote:
What error are you getting from ping?
I think the OP said he did not have a problem with ping.
--
Sahil Tandon [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
Tom Marchand said the following on 9/1/08 7:52 PM:
Hi,
I've got an issue where hosts defined in my /etc/hosts are not being
resolved. I've looked at resolv.conf, host.conf and nsswitch.conf and
everything looks ok. It's my understanding that with the below
configurations, /etc/hosts should
At 06:52 PM 9/1/2008, Tom Marchand wrote:
Hi,
I've got an issue where hosts defined in my /etc/hosts are not being
resolved. I've looked at resolv.conf, host.conf and nsswitch.conf and
everything looks ok. It's my understanding that with the below
configurations, /etc/hosts should be used
I am trying to resolve the 192.168.2.3 address.
::1 localhost.local localhost
127.0.0.1 localhost.local localhost
72.15.233.132 host.local host
72.15.233.132 host.local.
192.168.2.3 test
On Sep 1, 2008, at 8:10 PM, Glenn Sieb
Everything is set correctly in rc.conf. What I have noticed is that
ping can resolve hosts from /etc/hosts. I should mention that this
machine has been running for 1.5 years and it wasn't until today that
I've needed to add machines to /etc/hosts.
On Sep 1, 2008, at 8:22 PM, Derek
Tom Marchand [EMAIL PROTECTED] wrote:
Everything is set correctly in rc.conf. What I have noticed is that
ping can resolve hosts from /etc/hosts.
If ping works then everything is fine in /etc/hosts. You haven't told us
what program you're using to resolve the
Josh Paetzel [EMAIL PROTECTED] wrote:
I have a stock 6.0-RELEASE box that doesn't seem to be
reading /etc/hosts
In /etc/hosts I have:
192.168.1.101 example example.example.org
/etc/nsswitch.conf is stock:
group: compat
group_compat: nis
hosts: files dns
networks: files
passwd:
shells: files
$ host example
Host example not found: 3(NXDOMAIN)
host command always use DNS. try ping, telnet, whatever use IP
connections
$ host example.example.org
Host example not found 3(NXDOMAIN)
What am I doing wrong here that is keeping /etc/hosts from being read?
--
Thanks,
On Thursday 13 April 2006 11:11, Wojciech Puchar wrote:
shells: files
$ host example
Host example not found: 3(NXDOMAIN)
host command always use DNS. try ping, telnet, whatever use IP
connections
$ host example.example.org
Host example not found 3(NXDOMAIN)
What am I doing
Josh Paetzel writes:
Ok...That solved my hostname resolution issues. Now the next
issue is why it takes ssh 60 seconds to give me a password
prompt. I thought that was always caused by not having name
resolution working. Any thoughts on this issue?
You may have solved one
On Thu, Apr 13, 2006 at 12:52:11PM -0400, Robert Huff wrote:
You may have solved one name resolution problem; have you
solved them all?
The N second delay problem is usually caused by something
trying to do a reverse name look-up. You either need to disable
this, or make sure
On Tue, Nov 25, 2003 at 03:06:46PM -0700, RYAN vAN GINNEKEN wrote:
after makeing changes to /ect/hosts do you have to reload the file
somehow or do the effects take immediately
Changes take place immediately.
--
Jonathan Chen [EMAIL PROTECTED]
21 matches
Mail list logo
