Reverse address problem

Jason ceo at inspire-web.com
Tue Jul 13 17:44:40 UTC 1999


Soledad, how long ago did you put in the request to change this information?  It
can take days before this information is globaly updated.

Soledad wrote:

> We have change our domain from medusa.es to fujitsu.es. And now, we have
> problems to resolve reverse address. I can resolve in my system but I can
> not do it in others server.
>
> > 19.140.194.in-addr.arpa
> Server:  ns.fujitsu.es
> Address:  193.148.29.100
>
> 19.140.194.in-addr.arpa nameserver = ns.fujitsu.es
> 19.140.194.in-addr.arpa nameserver = ns1.fujitsu.es
> 19.140.194.in-addr.arpa
>         origin = ns1.fujitsu.es
>         mail addr = postmaster.fujitsu.es
>         serial = 1999051301
>         refresh = 86400 (1 day)
>         retry   = 7200 (2 hours)
>         expire  = 2592000 (30 days)
>         minimum ttl = 172800 (2 days)
> 19.140.194.in-addr.arpa nameserver = ns.fujitsu.es
> 19.140.194.in-addr.arpa nameserver = ns1.fujitsu.es
> ns.fujitsu.es   internet address = 193.148.29.100
> ns1.fujitsu.es  internet address = 193.148.29.103
>
> > server artemis.ttd.net
> Default Server:  artemis.ttd.net
> Address:  194.179.1.101
>
> > 19.140.194.in-addr.arpa
> Server:  artemis.ttd.net
> Address:  194.179.1.101
>
> Non-authoritative answer:
> 19.140.194.in-addr.arpa nameserver = ns.medusa.es
> 19.140.194.in-addr.arpa nameserver = ns1.medusa.es
>
> Authoritative answers can be found from:
> 19.140.194.in-addr.arpa nameserver = ns.medusa.es
> 19.140.194.in-addr.arpa nameserver = ns1.medusa.es
> >
> > ns.medusa.es
> Server:  artemis.ttd.net
> Address:  194.179.1.101
>
> *** artemis.ttd.net can't find ns.medusa.es: Non-existent host/domain
> >
>
> ns.medusa.es and ns1.medusa.es are not a valid DNS server, at least, to this
> ip address.
>
> Can anybody tell me how to find where the problem and solution is?.
>
> Thanks in advance.
>
> Soledad Serrano Oca
> email: soledad at fujitsu.es



More information about the bind-users mailing list