Re: Hacked? nslookup resolves wrong IP, name from another domain by duplicating .com.mx prefixes...
> You have a domain (public) and (private) using the same domain.name.
> Example: abc.com and abc.com both public and private.
My public domain is mydomain.com.mx
My private domain is mydomain.net
> You perform an nslookup inside of your (private) domain and all seems
> fine?
> nslookup (then get response). This response should be from your DNS
> located inside of your network.
nslookup mailserver.mydomain.com.mx dnsserver.mydomain.net
returns a non autoritative answer with the correct ip for the
mailserver.mydomain.com.mx
dnsserver.mydomain.net is set up to forward DNS queries to
dnsserver.mydomain.com.mx
> Now when you perform a nslookup on the outside public network you get what
> your now calling wrong info?
on the public network
nslookup mailserver.mydomain.com.mx dnsserver.mydomain.com.mx
returns:
Name: mailserver.mydomain.com.mx.com.mx
Address: wrong address from domain mx.com.mx
> (Q). On your registrant info, what do you have defined as your SOA
> server(s). What I am asking is do you have DNS server setup on the
> outside (public) such as ns1.abc.com and ns2.abc.com. You need to have
> this. As it will point back to what ever DNS server is to be managing
> your domain name.
SOA in my public DNS server is pdc.mydomain.com.mx.
Thanks for the response
Sammy
|