On Thu, 23 Jun 2011, Giles Coochey wrote:
> Well, if you have access to the source, you can probably modify some
> constants to disable particular protocols, or there may be compile time
> options already - it would be nice to disable automatically on runtime if
> the host does not have a IPv6 pro
On Thu, June 23, 2011 12:07, John Hodrien wrote:
> On Thu, 23 Jun 2011, Giles Coochey wrote:
>
>> Yes, I'm sure it will depend on the implementation, the trailing dot was
>> somewhat an educated guess from previous ISC BIND & dig tool use. :-)
>> As for both the A and record, I think you will
On Thu, 23 Jun 2011, Giles Coochey wrote:
> Yes, I'm sure it will depend on the implementation, the trailing dot was
> somewhat an educated guess from previous ISC BIND & dig tool use. :-)
> As for both the A and record, I think you will have that until IPv4
> is fully deprecated by IPv6 and
On Thu, June 23, 2011 11:53, John Hodrien wrote:
> On Thu, 23 Jun 2011, Giles Coochey wrote:
>
>> Can you avoid the bar.baz.domain.com.domain.com by searching for
>>
>> bar.baz.domain.com.
>>
>> (note trailing dot)
>>
>> ??
>
> Hmm, good suggestion, that I'd not considered, Thanks. It does appear
On Thu, 23 Jun 2011, Giles Coochey wrote:
> Can you avoid the bar.baz.domain.com.domain.com by searching for
>
> bar.baz.domain.com.
>
> (note trailing dot)
>
> ??
Hmm, good suggestion, that I'd not considered, Thanks. It does appear to
clear that up (down to two lookups from three: an and
Can you avoid the bar.baz.domain.com.domain.com by searching for
bar.baz.domain.com.
(note trailing dot)
??
On Thu, June 23, 2011 11:06, John Hodrien wrote:
> On Wed, 22 Jun 2011, Ljubomir Ljubojevic wrote:
>
>> As Les wrote in another branch of the thread, search clause is if you
>> try name
On Wed, 22 Jun 2011, Ljubomir Ljubojevic wrote:
> As Les wrote in another branch of the thread, search clause is if you
> try name without a domain.
I think it's slightly more subtle and possibly more annoying than that.
Say you have a machine called foo.mydomain.com
By default (if you don't sp
--On Wednesday, June 22, 2011 03:30:18 PM -0500 Robert Henrichs
wrote:
> root@pbx:~ $ cat /etc/resolv.conf
> search isp.com
>nameserver 8.8.4.4
>nameserver 216.146.36.36
>nameserver 8.8.8.8
Get rid of the leading whitespace if it actually exists in that file.
It shouldn't make a diff
Ljubomir Ljubojevic wrote:
> Robert Henrichs wrote:
>> root@pbx:~ $ cat /etc/resolv.conf
>> search isp.com
>>nameserver 8.8.4.4
>>nameserver 216.146.36.36
>>nameserver 8.8.8.8
> Whats with the "search isp.com"? Try removing that and try again. Try
> first without rebooting.
>
> I am l
Robert Henrichs wrote:
>
> root@pbx:~ $ cat /etc/resolv.conf
> search isp.com
>nameserver 8.8.4.4
>nameserver 216.146.36.36
>nameserver 8.8.8.8
Whats with the "search isp.com"? Try removing that and try again. Try
first without rebooting.
I am looking what it actually does. I do not
On 6/22/2011 3:30 PM, Robert Henrichs wrote:
>
>
> what's a good link to read about how the resolv.conf file is
> constructed? esp. the "search" entry?
The 'search' should only apply if you don't supply the domain portion of
the name. Each nameserver address should be queried until one resp
> what's a good link to read about how the resolv.conf file is
> constructed? esp. the "search" entry?
>
man resolv.conf
>
> ***
> This was part of the wget response:
> www.henrichs.orgcanonical name = ehost-services119.com.
> Name: ehost-services119.com
> Address: 69.64.155.165
>
Thanks All,
Answering multiple questions:
***
I started off with Google's DNS servers- 8.8.8.8 and 8.8.4.4 with
the same results. The current set were copied off other working
wkstas on the LAN . Same type results with "ping www.yahoo.com" and
"ping www.yahoo.com". Just changed it to
robert henrichs wrote:
> I am getting what I believe to be inconsistent replies/results from
> my CentOs machine, trying to ping URLs. Pinging by URL fails the DNS
> lookup, while pinging the IP address (that should have been returned)
> works. The DNS lookup also fails NSLOOKUP, but interesti
> -Original Message-
> Behalf Of robert henrichs
> Subject: [CentOS] inconsistent DNS results - ping vs dig vs nslookup
>
> I am getting what I believe to be inconsistent replies/results from
> my CentOs machine, trying to ping URLs. Pinging by URL fails the DNS
>
I am getting what I believe to be inconsistent replies/results from
my CentOs machine, trying to ping URLs. Pinging by URL fails the DNS
lookup, while pinging the IP address (that should have been returned)
works. The DNS lookup also fails NSLOOKUP, but interestingly, dig
and wget return A re
16 matches
Mail list logo
