Tom_Hickerson
asked on
Nslookup -----> non-existent domain
We have has our DNS server in place for a long time, and everything I worked fine as far as I could tell. We had some mobile users come up, and the could not get to their smtp mail server. Somone told me to run a nslookup on the mail server and I get... (I have used msn.com for this example)
C:\Documents and Settings\XXXXXX>nslookup msn.com
*** Can't find server name for address 192.168.0.3: Non-existent domain
*** Can't find server name for address 192.168.0.3: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.3
Name: msn.com
Address: 207.68.172.246
Does this mean that something is wrong, or is this a normal responce? Like I said as far as I can tell everything else works.
C:\Documents and Settings\XXXXXX>nslookup msn.com
*** Can't find server name for address 192.168.0.3: Non-existent domain
*** Can't find server name for address 192.168.0.3: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.3
Name: msn.com
Address: 207.68.172.246
Does this mean that something is wrong, or is this a normal responce? Like I said as far as I can tell everything else works.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The computer that is the DNS server is 192.168.0.3. That is the only DNS sever in the network.
Did you try nslookup remotely?
If mobile clients are having trouble resolving the SMTP server, then it is a problem with your public domain registration.
If mobile clients are having trouble resolving the SMTP server, then it is a problem with your public domain registration.
If the server is using itself as the primary DNS server, ensure that you have and entry for the exact
FQDNS in the DNS management console.
For example, if you are server1.mycompany.local
you should add an domain and entry for mail.publicdnsname.com
FQDNS in the DNS management console.
For example, if you are server1.mycompany.local
you should add an domain and entry for mail.publicdnsname.com
ASKER
gambit
The smtp server is not my own, and I was not concerned about that as much as I was the errors I got from the nslookup.
The smtp server is not my own, and I was not concerned about that as much as I was the errors I got from the nslookup.
oh, read that wrong, I agree with toniur.
The error is not a big deal, and shouldn't cause remote users from being able to SMTP publicly.
Simply says that you server cannot resolve it's own DNS name from its IP. You would have trouble if it was the other way around.
Just means you don't have a reverse lookup entry in whatever DNS server it is querying.
If you can ping the DNS name remotely and locally, DNS is not goofing your SMTP.
The error is not a big deal, and shouldn't cause remote users from being able to SMTP publicly.
Simply says that you server cannot resolve it's own DNS name from its IP. You would have trouble if it was the other way around.
Just means you don't have a reverse lookup entry in whatever DNS server it is querying.
If you can ping the DNS name remotely and locally, DNS is not goofing your SMTP.
ASKER
Ok. I am going to try and add a reverse lookup zone. I don't know what settings I use when adding the zone.
Primary, Seconday, or Stub, and a bunch more choices after that... Can you point me in the right direction.
Primary, Seconday, or Stub, and a bunch more choices after that... Can you point me in the right direction.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks that fixed it.
If you're using 192.168.0.3 as your only name server you might have problems.
Is the dns service running on 192.168.0.3?