When I went to MXtoolbox website to check my email server against all the blacklist I found that my SMTP diagnostics told me the below. Reverse DNS FAILED! This is a problem. What exactly do I need to do to fix this issue? I realize this may be the cause of our exchange server not sending to certain domains correctly. I went through yahoo small business to create all my MX record and A record. Sending out seems fine to most domain and receiving from all domain work too. Is their something I have to do on my end? Can I just create the reverse DNS on an external DNS server rather than editing my internal DNS? Any help would be apprieciated.
a reverse dns record should be in the same place where all your other dns records are...there are many emails systems that will not accept email if it fails a reverse dns check...you might want to ensure there is an spf record in place, too... -- Susan Conkey [MVP] "mlindsey" wrote in message news:CC187642-2E68-43F6-86FA-D2E15AE771A7@microsoft.com... > When I went to MXtoolbox website to check my email server against all the > blacklist I found that my SMTP diagnostics told me the below. > Reverse DNS FAILED! This is a problem. > > What exactly do I need to do to fix this issue? I realize this may be the > cause of our exchange server not sending to certain domains correctly. I > went > through yahoo small business to create all my MX record and A record. > Sending > out seems fine to most domain and receiving from all domain work too. Is > their something I have to do on my end? Can I just create the reverse DNS > on > an external DNS server rather than editing my internal DNS? Any help would > be > apprieciated.
So What should I do? You are saying these option should be in the yahoo page where I made the MX and A record?
mlindsey wrote: > When I went to MXtoolbox website to check my email server against all > the blacklist I found that my SMTP diagnostics told me the below. > Reverse DNS FAILED! This is a problem. > > What exactly do I need to do to fix this issue? I realize this may be > the cause of our exchange server not sending to certain domains > correctly. I went through yahoo small business to create all my MX > record and A record. Sending out seems fine to most domain and > receiving from all domain work too. Is their something I have to do > on my end? Can I just create the reverse DNS on an external DNS > server rather than editing my internal DNS? Any help would be > apprieciated. Call your ISP for this. You yourself cannot create a reverse lookup for your public; whomever owns the IP address/netblock creates this for you. It has nothing to do with your domain. If they'll create something that matches your MX record then that's great - but it isn't necessary. All they need to have is create *something* in there. You can do a quick lookup yourself in a command prompt - ping -a xxx.xxx.xxx.xxx
I will give them a call. I cannot ping the external IP since I am inside network. Thanks "Lanwench [MVP - Exchange]" wrote: > mlindsey wrote: > > When I went to MXtoolbox website to check my email server against all > > the blacklist I found that my SMTP diagnostics told me the below. > > Reverse DNS FAILED! This is a problem. > > > > What exactly do I need to do to fix this issue? I realize this may be > > the cause of our exchange server not sending to certain domains > > correctly. I went through yahoo small business to create all my MX > > record and A record. Sending out seems fine to most domain and > > receiving from all domain work too. Is their something I have to do > > on my end? Can I just create the reverse DNS on an external DNS > > server rather than editing my internal DNS? Any help would be > > apprieciated. > > Call your ISP for this. You yourself cannot create a reverse lookup for your > public; whomever owns the IP address/netblock creates this for you. It has > nothing to do with your domain. If they'll create something that matches > your MX record then that's great - but it isn't necessary. All they need to > have is create *something* in there. > > You can do a quick lookup yourself in a command prompt - > > ping -a xxx.xxx.xxx.xxx > > > > >
mlindsey wrote: > I will give them a call. I cannot ping the external IP since I am > inside network. You should be able to ping it and find out whether there's a reverse lookup, even if you can't get a reply, note. > > Thanks > > "Lanwench [MVP - Exchange]" wrote: > >> mlindsey wrote: >>> When I went to MXtoolbox website to check my email server against >>> all the blacklist I found that my SMTP diagnostics told me the >>> below. Reverse DNS FAILED! This is a problem. >>> >>> What exactly do I need to do to fix this issue? I realize this may >>> be the cause of our exchange server not sending to certain domains >>> correctly. I went through yahoo small business to create all my MX >>> record and A record. Sending out seems fine to most domain and >>> receiving from all domain work too. Is their something I have to do >>> on my end? Can I just create the reverse DNS on an external DNS >>> server rather than editing my internal DNS? Any help would be >>> apprieciated. >> >> Call your ISP for this. You yourself cannot create a reverse lookup >> for your public; whomever owns the IP address/netblock creates this >> for you. It has nothing to do with your domain. If they'll create >> something that matches your MX record then that's great - but it >> isn't necessary. All they need to have is create *something* in >> there. >> >> You can do a quick lookup yourself in a command prompt - >> >> ping -a xxx.xxx.xxx.xxx
You could do an NSLookup. NSLookup Set Type=PTR Enter IP "Lanwench [MVP - Exchange]" wrote in message news:eDHIlfftIHA.4260@TK2MSFTNGP05.phx.gbl... > mlindsey wrote: >> I will give them a call. I cannot ping the external IP since I am >> inside network. > > You should be able to ping it and find out whether there's a reverse > lookup, even if you can't get a reply, note. >> >> Thanks >> >> "Lanwench [MVP - Exchange]" wrote: >> >>> mlindsey wrote: >>>> When I went to MXtoolbox website to check my email server against >>>> all the blacklist I found that my SMTP diagnostics told me the >>>> below. Reverse DNS FAILED! This is a problem. >>>> >>>> What exactly do I need to do to fix this issue? I realize this may >>>> be the cause of our exchange server not sending to certain domains >>>> correctly. I went through yahoo small business to create all my MX >>>> record and A record. Sending out seems fine to most domain and >>>> receiving from all domain work too. Is their something I have to do >>>> on my end? Can I just create the reverse DNS on an external DNS >>>> server rather than editing my internal DNS? Any help would be >>>> apprieciated. >>> >>> Call your ISP for this. You yourself cannot create a reverse lookup >>> for your public; whomever owns the IP address/netblock creates this >>> for you. It has nothing to do with your domain. If they'll create >>> something that matches your MX record then that's great - but it >>> isn't necessary. All they need to have is create *something* in >>> there. >>> >>> You can do a quick lookup yourself in a command prompt - >>> >>> ping -a xxx.xxx.xxx.xxx > > >
"Susan" wrote: >a reverse dns record should be in the same place where all your other dns >records are That's not always true. The PTR records are kept in the zone file of the network owner. Other DNS resource records are kept in the domain owner's DNS. Sometimes they're the same . . . sometimes they aren't -- and for most small companies the PTR records will be in the ISP's DNS and their domain info will be in their own DNS. -- Rich Matheisen MCSE+I, Exchange MVP MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm Don't send mail to this address mailto:h.pott@getronics.com Or to these, either: mailto:h.pott@pinkroccade.com mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com
you're right, of course...I was just thinking of our setup here... -- Susan Conkey [MVP] "Rich Matheisen [MVP]" wrote in message news:7k4n2495rifhitafs1pafap94eh9ce124c@4ax.com... > "Susan" wrote: > >>a reverse dns record should be in the same place where all your other dns >>records are > > That's not always true. The PTR records are kept in the zone file of > the network owner. Other DNS resource records are kept in the domain > owner's DNS. Sometimes they're the same . . . sometimes they aren't -- > and for most small companies the PTR records will be in the ISP's DNS > and their domain info will be in their own DNS. > > > -- > Rich Matheisen > MCSE+I, Exchange MVP > MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm > Don't send mail to this address mailto:h.pott@getronics.com > Or to these, either: mailto:h.pott@pinkroccade.com > mailto:melvin.mcphucknuckle@getronics.com > mailto:melvin.mcphucknuckle@pinkroccade.com
