[mdlug] Strange Network Issue

[R Kannan]

On 10/19/2014 11:15 AM, R Kannan wrote:
> On 10/19/2014 10:34 AM, R Kannan wrote:
>> On 10/18/2014 10:19 PM, Carl T. Miller wrote:
>>> R Kannan wrote:
>>>> On 10/18/2014 08:33 PM, Adam Behnke wrote:
>>>>> What happens when your try the ip addresses?
>>>>>
>>>> They were timing out while using IPs obtained from other machines. I
>>>> believe it is not a DNS failure but a hardware issue now. But now after
>>>> replacing a network, it seems to work except resolving www.nfl.com. Is
>>>> there a local DNS buffer/cache I need to clear?
>>> If you are running nscd, you can clear the cache by
>>> running "nscd -i hosts".  If you're running bind,
>>> try "rndc flush".  Otherwise you're probably not
>>> caching dns records.
>>>
>>> c
>>>
>>>
>>> _______________________________________________
>>> mdlug mailing list
>>> mdlug at mdlug.org
>>> http://mdlug.org/mailman/listinfo/mdlug
>> I don't belive I am running either of them. grepping for these among the
>> processes did not yield anything.
>>
> Not only that particular site, several sites (www.hulu.com, etc.) are
> failing to resolve. This is frustrating.
I added the following two lines (for public DNS servers?) to
/etc/resolv.conf and now the addresses are getting resolved.

|nameserver 208.67.222.222
nameserver 208.67.220.220

And the only nameserver that was there in that file was loopback (127.0.0.1). 

That brings up the question where the name servers set (static IP not using DHCP) in the Ubuntu 
'wired connection' GUI is stored and what is the search order?

|