On 4/02/11 3:07 AM, Tory M Blue tmb...@gmail.com wrote:
On Thu, Feb 3, 2011 at 5:23 PM, Barry Margolin bar...@alum.mit.edu wrote:
In article mailman.1636.1296781581.555.bind-
SNIPPED
www.yahoo.com. 300 IN CNAME fp.wg1.b.yahoo.com.
And even when they did, it didn't get involved
* Tory M. Blue:
[tblue@mx3 ~]$ dig @problemserver.net www.yahoo.com +trace
Please use dig @problemserver.net www.yahoo.com +trace +norecurse
+dnssec, to match more closely the queires that BIND would send.
--
Florian Weimerfwei...@bfk.de
BFK edv-consulting GmbH
+trace does not do what you think it does. It does not query the target name
server for each successive query. Rather, it causes the 'dig' command to
perform recursion on its own, only using the indicated server (@server) to seed
its root server list. +trace also stops at the CNAME, and does
On Fri, Feb 4, 2011 at 5:37 AM, Florian Weimer fwei...@bfk.de wrote:
* Tory M. Blue:
[tblue@mx3 ~]$ dig @problemserver.net www.yahoo.com +trace
Please use dig @problemserver.net www.yahoo.com +trace +norecurse
+dnssec, to match more closely the queires that BIND would send.
Okay thanks,
On Feb 4, 2011, at 1:11 PM, Chris Buxton wrote:
+trace does not do what you think it does. It does not query the target name
server for each successive query. Rather, it causes the 'dig' command to
perform recursion on its own, only using the indicated server (@server) to
seed its root
In article mailman.1636.1296781581.555.bind-us...@lists.isc.org,
Tory M Blue tmb...@gmail.com wrote:
Second email in a single day, crazy. But I've had issues backing up
and just need to resolve them
Again Bind bind-9.7.2-P3 behind F5 Loadbalancers.
I'm running into an issue where one of
On Thu, Feb 3, 2011 at 5:23 PM, Barry Margolin bar...@alum.mit.edu wrote:
In article mailman.1636.1296781581.555.bind-
SNIPPED
www.yahoo.com. 300 IN CNAME fp.wg1.b.yahoo.com.
And even when they did, it didn't get involved until you followed the
CNAME returned for www.yahoo.com. Your log
7 matches
Mail list logo