DNS Problem

[BMurphy]

Hello all,

I have a DNS problem, and unfortunately I'm not that experienced with DNS entries, therefore I'm not sure exactly what the problem is. I'm not even sure if it's a change that needs to be made on my end, or SB's end.

I get an error when doing a reverse lookup on our email server. Here is the information that is outputted when I attempt the lookup manually (from www.dnsstuff.com)

Asking ns1.serverbeach.com. for 20.34.###.##.in-addr.arpa PTR record: Reports server1.mydomain.net.

Answer:
##.###.34.20 PTR record: server1.myserver.net. [TTL 86400s] [A=None] *ERROR* A record does not point back to original IP.

Through pm'ing, knightfoo suggested I submit a PTR request to have the record changed, but when I do that there are some fields that I'm not 100% postive about what the content should be. Since it deals with DNS, I'm hesitant on submitting a request and having it turn out to be wrong ...
I'm not sure what to put in the fields FQDN, and IP address. Should I be putting server1.mydomain.net in the FQDN, or just mydomain.net. Server Beach already knows my IP address (as it's in the textbox right above where they ask for FQDN), so are they looking for the IP address of the main domain? server1.mydomain.net is a server located at SB, but mydomain.net is in a different location, on a different server.

Thank you.

[raider]

i thought they gave you a server name when you signed up...if that's your prob...

[knightfoo]

Originally posted by BMurphy
Hello all,

I have a DNS problem, and unfortunately I'm not that experienced with DNS entries, therefore I'm not sure exactly what the problem is. I'm not even sure if it's a change that needs to be made on my end, or SB's end.

I get an error when doing a reverse lookup on our email server. Here is the information that is outputted when I attempt the lookup manually (from www.dnsstuff.com)

Asking ns1.serverbeach.com. for 20.34.###.##.in-addr.arpa PTR record: Reports server1.mydomain.net.

Answer:
##.###.34.20 PTR record: server1.myserver.net. [TTL 86400s] [A=None] *ERROR* A record does not point back to original IP.

Through pm'ing, knightfoo suggested I submit a PTR request to have the record changed, but when I do that there are some fields that I'm not 100% postive about what the content should be. Since it deals with DNS, I'm hesitant on submitting a request and having it turn out to be wrong ...
I'm not sure what to put in the fields FQDN, and IP address. Should I be putting server1.mydomain.net in the FQDN, or just mydomain.net. Server Beach already knows my IP address (as it's in the textbox right above where they ask for FQDN), so are they looking for the IP address of the main domain? server1.mydomain.net is a server located at SB, but mydomain.net is in a different location, on a different server.

Thank you.

You should probably set the PTR to the FQDN of your server (server1.yourdomain.com), unless you have some other reason not to do so.

-knightfoo

[BMurphy]

raider .. I'm not sure what you mean. My problem is that I get errors when doing a reverse dns lookup on the IP of my email server.

knightfoo .. Another thing I'm confused about is the "server1". When I check the name of my computer in the network identifiction area of the server, it's server20.mydomain.net.

Just so I know, if I add the wrong value in those fields, then obviously the reverse dns lookup will not work, but could it potentially cause problems with the normal lookup (mydomain.net -> ###.###.###.###)?

[knightfoo]

Originally posted by BMurphy
raider .. I'm not sure what you mean. My problem is that I get errors when doing a reverse dns lookup on the IP of my email server.

knightfoo .. Another thing I'm confused about is the "server1". When I check the name of my computer in the network identifiction area of the server, it's server20.mydomain.net.

Just so I know, if I add the wrong value in those fields, then obviously the reverse dns lookup will not work, but could it potentially cause problems with the normal lookup (mydomain.net -> ###.###.###.###)?

Using "server1" was just an example, you need to use whatever the name of your server really is. An incorrect PTR entry will not cause your normal domain resolution to fail.

-knightfoo

[BMurphy]

knightfoo .. haha, maybe server1 was just an example, but that really is how it's setup.
Our clients use SERVER.mydomain.net for their incoming and outgoing mail server, the reverse dns lookup produces SERVER1.mydomain.net, and the server itself is setup to have a name of SERVER20.mydomain.net.