A possible alternative to capturing network traffic is running the
command which should generate the DNS lookup via strace and seeing what
it actually does. For example, from `strace ping -c 1 google.com` I can
see that I'm sending my DNS query to 127.0.1.1 (I'm running a local
instance of dnsm
Or capture the network traffic and look at it with wireshark
On Wed, Mar 26, 2014 at 6:14 PM, Paul Boniol wrote:
> You can do some diagnostics with the dig command.
>
> E.g.
> dig @server name
> dig name
>
> Paul
>
>
> On Wed, Mar 26, 2014 at 3:57 PM, Howard White wrote:
>
>> On 03/26/2014 01:
You can do some diagnostics with the dig command.
E.g.
dig @server name
dig name
Paul
On Wed, Mar 26, 2014 at 3:57 PM, Howard White wrote:
> On 03/26/2014 01:24 PM, Steven S. Critchfield wrote:
>
>> Have you checked the entries in /etc/nsswitch.conf
>>
>>
> nsswitch.conf matches another serve
On 03/26/2014 01:24 PM, Steven S. Critchfield wrote:
Have you checked the entries in /etc/nsswitch.conf
nsswitch.conf matches another server of the same release level upon
which nslookup works fine.
Howard
--
--
You received this message because you are subscribed to the Google Groups
"NL
Have you checked the entries in /etc/nsswitch.conf
- Original Message -
> One of a whole mess of CentOS servers does not resolve DNS addresses.
> I've set this up like so many others.
>
> DEVICE="eth0"
> BOOTPROTO="static" DNS1="192.168.21.1"
> GATEWAY="192.168.21.254" HOSTNAME="dev2"
>
One of a whole mess of CentOS servers does not resolve DNS addresses.
I've set this up like so many others.
DEVICE="eth0"
BOOTPROTO="static"
DNS1="192.168.21.1"
GATEWAY="192.168.21.254"
HOSTNAME="dev2"
HWADDR="00:0C:29:B9:C6:E8"
IPADDR="192.168.21.3"
IPV6INIT="yes"
MTU="1500"
NETMASK="255.255.25
