Windows 2003 DNS server is giving me an “Associated pointer (PTR) record cannot be created” error.

Hi GabicusC,

do youa ctually have a rlz configured? i have seen it when there is no zone there

the record still gets created in the FLZ yes?

Jay_Jay70 thanks for your reply.

no I do not have an rlz configured for this zone.  With the flz I would get the error then yes it would create the host(a) but would not create the mx at all.  I get this error when trying to do the MX record "A new record can not be created.  Name is invalid"

Gabicus

you need to configure a reverse lookup zone for your domain

I am having trouble with the rlz.  This is what i have for the flz.

Zone is:
mydomain.com
then with in mydomain.com I have
Name                    type
mail                      host(a)  ip is to the outside
www                    host(a)  ip is internal
same as parent     SOA
same as parent     NS

I tried to set up a Primay zone in the rlz with:
mydomain.com
but i get an error that the zone already exsits.  I then try with mail.mydomain.com with no luck.

What am I doing wrong with the rlz?

Thanks again for you help,

Rich

I have put a pointer into the rlz internal Network Class for the mydomain.com with the full Name being mail.mydomain.com.  I also as able to put in the MX Records and the CNAME; however my Exchange server is still not sending out to mydomain.com addresses.  All other emails are going out fine.

I am not sure if I put everything in correct.  Is there a way to check and make sure that I have everything in properly?

hmm i am not sure on the intricasies with exchange as i dont get to deal with ofiten - its all managed interstate

what happens when send your email? does it just fail?

Everything works fine when I send from my outlook.  But when I go to the Exchange sever and look at the que  I see all my emails are still sitting in the lastagealliance.com folder.  When I try a force connection it connects but nothing goes out.  All the other domains in the que have been going out with no problem.

hmm let me see if i can get some additional help

Is this you?

http://www.dnsreport.com/tools/dnsreport.ch?domain=lastagealliance.com+

you can try flushing your dns cache

ipconfig /flushdns

Thats a good call.
On the dns server, open the dns service.
in the mmc, make sure you have checked the advanced view tab so that you see the dns cache entries
Clear this cache (there is an option in the menu)

How are you creating the reverse lookup zone?

Sorry for the delay.  I have had one of those days.

Jay_Jay70 and keith_alabaster,

I flushed the DNS and I am still holding everything in my exchange que for lastagealliance.com.

The DNS Report is mine.

As for the reverse lookup zone I did not create anything but the pointer.  There was a folder already there for my IP class "0.168.192.in-addr.arpa".  In this folder is where I created the new pointer by right clicking then selecting create new pointer.

OK, thats cool. You want to point out the state of your external dns to whoever is looking after it for you though as this will not be helping your cause.

Can I ask why you want the MX record internally?
As your workstations aand the server are already on the domain, what are you expecting it to do for you?

Keith_alabaster,

Thanks for getting back to me.

I have an Exchange server on the same internal network with my workstation and web server.  I am using this Exchange server to send out on but not receive.  I am using a 3rd party company to receive all of my emails.  Everything is going out except emails going to lastagealliacne.com.  All of those are just sitting in the que and are not able to do a reverse look up because I have lastagealliance.com pointing to my internal DNS.  I have to have my Exchange server DNS pointing to the internal DNS because of the Active Directory.  I am not able to resolve mail.lastagealliance.com on the Internal DNS.   I have added a host(a) record to the flz for mail.lastagealliance.com with the proper outside IP. But it still did not work.  That is where the adding a ptr to rlz came in and is where I am at right now with trouble shooting this issue.

this line should read:

 All of those are just sitting in the que and are not able to do a reverse look up because I have lastagealliance.com in my internal DNS.

Keith_alabaster,


Yes you are right very painful.  I will try what you suggested.  For now I am off to the Mountians with my kids.  I will let you know on sunday how it goes with the server.

Thanks again for your help.

Sure. Have a good weekend, I'll be here

regards
Keith

Keith,

I finally have had a chance to get back to this. I assume I need to add the information to the LMHOSTS.SAM file.

This is what I entered then I rebooted.

64.202.165.92      mail.lastagealliance.com

is this the correct format?

Rich

No, the lmhosts.sam is actually a sample (example) copy of the lmhosts file. This is used for netbios type lookups such as those performed by a WINS server. If that were the file to be edited, you would then sabe it just as lmhosts.

What we need to do is use the file just called hosts  
Make sure you do not save it with any extension such as .sam, or .txt

The syntax you have used is perfect.

Unfortunately that did not work.  I not sure what option I have left.

on the box, if you type in nslookup mail.lastagealliance.com what do you now get?

I get:

Server:     lasa-serv1.lasa.com
Address:   192.168.0.50

Name:      mail.lastagealliance.com
Address:   64.202.165.92

I did this on a server that is named lasa-serv3 and not lasa-serv1 like what is named in the results of nslookup.

No, that is fine. The results are simply telling you that lasa-ser3 asked lasa-serv1 to get the results.

Is lasa-serv3 the email server that is having the problem?

Keith,

Yes lasa-serv3 is my Exchange server.  But I have found some other issue on this journey that I have undertaken.

I brought in a friend to help me and at this point it has become clear that I have some legacy issue that are messing up my network beyond my exchange server.  The main issue being that my internal domain lasa.com and is a domain that we do not own.  So when we did an nslookup from outside on mail.lastageallaicne.org we see that the full name coming back was mail.lastagealliance.com.lasa.com and would point to a server I do not have control over.  I am now faced with the joy of renaming my internal domain to lastageallince.com from lasa.com.  Because this is a new issue I am going to open up a new question.

I am going to split the point between you and jay_jay70.  jay_jay70 answered the first part of the question and you helped me out with the rest.  I thank you both for all your help.

Rich

Thankyou Rich, although you forgot to split the points with Keith :)

you can post a question in community support asking for it to be reopened so that you can split the points, either that or Keith may be able to as Page Editor

good look with your project

Keith,

I am so sorry I just hit the wrong link and did not hit the split points link.  Do know if there is a way I can change it so that I can split the points?

If not, I apologize because you have been a very big help to me.

Rich

Yes, I have the tools to reopen the question although I wouldn't do it here.

Thanks
keith

OK, thank you.

As I was involved in the call, it wouldn'thave been right if I had unaccepted the answer even though you suggested it. It is appreciated.

Regards
keith