Re: resolution problem

2016-05-25 Thread Matus UHLAR - fantomas
In article , Matus UHLAR - fantomas wrote: often a problem of invalid NS delegation, or bad TTL (A record for a server expires before NS record). On 19.05.16 15:31, Sam Wilson wrote: Glue A records for the nameservers

Re: resolution problem

2016-05-24 Thread Thomas Schulz
colostate.edu. 172800 IN NS dns1.colostate.edu. colostate.edu. 172800 IN NS dns3.colostate.edu. ;; Received 119 bytes from 192.41.162.30#53(l.edu-servers.net) in 78 ms www.cloudsat.cira.colostate.edu. 3600 IN CNAME

Re: resolution problem

2016-05-19 Thread Matus UHLAR - fantomas
>colostate.edu. 172800 IN NS dns1.colostate.edu. >colostate.edu. 172800 IN NS dns3.colostate.edu. >;; Received 119 bytes from 192.41.162.30#53(l.edu-servers.net) in 78 ms > >www.cloudsat.cira.colostate.edu. 3600 IN CNAME dpc.cira.colostate.edu.

Re: resolution problem

2016-05-19 Thread Sam Wilson
In article , Matus UHLAR - fantomas wrote: > On 18.05.16 14:10, Con Wieland wrote: > >I am having an issue resolving www.cloudsat.cira.colostate.edu from 2 of my > > name servers. I have 2 others with identical configs

Re: resolution problem

2016-05-19 Thread Phil Mayers
On 18/05/16 22:10, Con Wieland wrote: I am having an issue resolving www.cloudsat.cira.colostate.edu "rndc dumpdb" can be helpful in this case, IME. Dump the cache then inspect the records and parent delegations, see what bind thinks is in-cache when it's broken.

Re: resolution problem

2016-05-19 Thread Matus UHLAR - fantomas
On 18.05.16 14:10, Con Wieland wrote: I am having an issue resolving www.cloudsat.cira.colostate.edu from 2 of my name servers. I have 2 others with identical configs that resolve correctly. A normal lookup shows a server fail but a +trace looks ok. Any ideas how to better troubleshoot the

resolution problem

2016-05-18 Thread Con Wieland
I am having an issue resolving www.cloudsat.cira.colostate.edu from 2 of my name servers. I have 2 others with identical configs that resolve correctly. A normal lookup shows a server fail but a +trace looks ok. Any ideas how to better troubleshoot the issue? dig

named resolution problem

2011-10-05 Thread Roberto Bosticardo
Hi all, I have a problem with named (both bind9.3 and bind9.7) and resolution of www.myspace.fr; the problem is not present in dnscache (of djbdns suite) or asking resolution to google public dns (they run a Google implementation of dns protocol). If you ask a resolver/cache server running

Re: named resolution problem

2011-10-05 Thread Hauke Lampe
On 05.10.2011 12:58, Roberto Bosticardo wrote: If you ask a resolver/cache server running named the resolution of name www.myspace.fr it returns (SERVFAIL), if you ask the same to a dnscache server it correctly resolves to the ip address. BIND doesn't like NS records resolving to CNAMEs: The

Re: BIND 9 And Short Name resolution Problem

2011-04-01 Thread Torinthiel
On 03/31/11 20:58, Barry Finkel wrote: On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote: Hello, I get the following messages on the BIND server when I do a short name nslookup from a client: Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network unreachable resolving

Re: BIND 9 And Short Name resolution Problem

2011-04-01 Thread Mark Andrews
In message 4d956ac7.2010...@data.pl, Torinthiel writes: On 03/31/11 20:58, Barry Finkel wrote: On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote: Hello, I get the following messages on the BIND server when I do a short name= nslookup from a client: Mar 31 14:08:04 jedi

BIND 9 And Short Name resolution Problem

2011-03-31 Thread Tony MacDoodle
Hello, I get the following messages on the BIND server when I do a short name nslookup from a client: Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network unreachable resolving 'C.ROOT-SERVERS.NET//IN': 2001:500:1::803f:235#53 Mar 31 14:08:05 jedi named[1299]: [ID 873579

Re: BIND 9 And Short Name resolution Problem

2011-03-31 Thread Barry Finkel
On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote: Hello, I get the following messages on the BIND server when I do a short name nslookup from a client: Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network unreachable resolving 'C.ROOT-SERVERS.NET//IN':

Re: strange (to me) dns resolution problem

2010-06-25 Thread Matus UHLAR - fantomas
Am 23.06.2010 22:01, schrieb Hoover Chan: I have a strange problem where most things are working (i.e. I can query and get the correct answers from DNS) but a few domains which worked before have stopped working. Yet, when I go to another DNS server, they do get resolved. Any

Re: strange (to me) dns resolution problem

2010-06-24 Thread Hoover Chan
The machine in question is running bind 9.2.1. Thanks. - Hoover Chanhc...@mail.ewind.com -or- hc...@well.com Eastwind Associates P.O. Box 16646 voice: 415-731-6019 -or- 415-565-8936 San Francisco, CA

strange (to me) dns resolution problem

2010-06-23 Thread Hoover Chan
I have a strange problem where most things are working (i.e. I can query and get the correct answers from DNS) but a few domains which worked before have stopped working. Yet, when I go to another DNS server, they do get resolved. Any pointer to where I should look first? Get a newer list of

Re: strange (to me) dns resolution problem

2010-06-23 Thread Toto
Am 23.06.2010 22:01, schrieb Hoover Chan: I have a strange problem where most things are working (i.e. I can query and get the correct answers from DNS) but a few domains which worked before have stopped working. Yet, when I go to another DNS server, they do get resolved. Any pointer to where