Very strange problem

Vitor Colaco vitor.colaco at esdata.pt
Tue Aug 8 16:52:31 UTC 2000


dnsadmin at ttd.net wrote:
> 
> >
> > they fail to work resolving local domains, remote domais, or both?
> > in case it's from remote domais, it could be some problem on you
> > communication with the rest of the World.
> 
>         Any domain. I've checked communications and it's ok. The problem
> seems to be internal. In the name server, if i use 127.0.0.1 it's ok, but
> if I use the IP adress of the server, 194.179.1.100, the answer is slow,
> or no answer, by example: localhost is minerva.ttd.net, 194.179.1.100
> 
> bash-2.03# hostname
> minerva
> bash-2.03# nslookup
> > server 127.0.0.1
> Default Server:  localhost
> Address:  127.0.0.1
> 
> >set type=any
> > ttd.net.
> Server:  localhost
> Address:  127.0.0.1
> 
> ttd.net
>         origin = SCMRRO3.nombres.ttd.es
>         mail addr = dnsredip.tsai.es
>         serial = 2000062200
>         refresh = 86400 (1D)
>         retry   = 7200 (2H)
>         expire  = 2592000 (4w2d)
>         minimum ttl = 172800 (2D)
> ttd.net nameserver = SCMRRO3.nombres.ttd.es
> ttd.net nameserver = scmrro4.nombres.ttd.es
> ttd.net nameserver = minerva.ttd.net
> ttd.net preference = 20, mail exchanger = artemis.ttd.net
> ttd.net preference = 10, mail exchanger = minerva.ttd.net
> ttd.net nameserver = SCMRRO3.nombres.ttd.es
> ttd.net nameserver = scmrro4.nombres.ttd.es
> ttd.net nameserver = minerva.ttd.net
> SCMRRO3.nombres.ttd.es  internet address = 193.152.36.5
> scmrro4.nombres.ttd.es  internet address = 193.152.36.6
> minerva.ttd.net internet address = 194.179.1.100
> artemis.ttd.net internet address = 194.179.1.101
> >
> > server 194.179.1.100
> Default Server:  minerva.ttd.net
> Address:  194.179.1.100
> 
> > ttd.net.
> Server:  minerva.ttd.net
> Address:  194.179.1.100
> 
> *** minerva.ttd.net can't find ttd.net.: No response from server
> 
>         Strange, isn't it ?
> 
>         Sometimes happens, sometimes don't.
> 
>         Any idea?

Yes. If it's not from connection, then something has changed,
intentionally or not.
Try to take a look at all the files refering to DNS that changed since
yesterday and check for possible corruption. Maybe the fact that
sometimes you ARE able to resolve has to do with local cache.

Btw, wich one is the primary server?

I really dont see a reason for Angel's advice to work but I dont see
either anything against, so defy logic, and try it :-) Maybe cheer luck
is waiting for you.

Hmmm...still I'm getting a little low of ideas here (quite a hard day at
work), is there anybody else who can drop here a line for us to focus?

-- 
Vitor Colaco		| "If life gives you lemons, make lemonade."
Analista de Suporte	| 
E.S. Data Informatica	|



More information about the bind-users mailing list