DNS problems this morning -

[lee]

Tim <ignored_mailbox at yahoo.com.au> writes:

> Allegedly, on or about 13 November 2012, Rick Stevens sent:
>> It may have to be above the nameserver specifications:
>> 
>>         domain blah
>>         search blah
>>         options attempts:1 timeout:2
>>         nameserver blah
>>         nameserver blah
>> 
>> In other words, it may only take effect from the time it's seen in
>> the file. If you put it at the end, it has no effect. Not sure about
>> that, but give it a whirl. 
>
> I was only trying out the "rotate" option, but it makes no difference
> where it is in the file, as far my tests with the dig and nslookup
> commands, go.  It may well be that *they* read the resolv.conf file in
> their own manner, only looking for nameserver lines.
>
> Short of reading through the nameserver logs, I can't think of another
> tool to test with that tells me which nameserver answered its query.
> I'll try that later on.

When you use two name servers and turn on the query logging ('rndc
querylog on') on at least one of them, you can see if the one that logs
the requests has answered one or not.

Also, dig tells you which server answered and how long it took:


,----
| [~] dig 8.8.8.8
| [...]
| ;; Query time: 1 msec
| ;; SERVER: 127.0.0.1#53(127.0.0.1)
| ;; WHEN: Wed Nov 14 12:37:47 2012
| ;; MSG SIZE  rcvd: 111
| 
| [~] dig @8.8.8.8 8.8.8.8
| [...]
| ;; Query time: 40 msec
| ;; SERVER: 8.8.8.8#53(8.8.8.8)
| ;; WHEN: Wed Nov 14 12:37:53 2012
| ;; MSG SIZE  rcvd: 111
| 
| [~] 
`----


-- 
Fedora 17